(paid support) Pacman Update GUI

Below the project description. If you are interested in doing this programming job, please email/pm me.
If there are questions, please reply to this post.
Pacman Update GUI
Archlinux (http://www.archlinux.org/) uses the pacman package manager. A number of GUI applications to control this package manager exist (http://wiki.archlinux.org/index.php/Pac … _Frontends), but none suit our needs.
For this project you will need to design and implement two independent GTK+ applications: an Update Manager and an Update Applet. The Update Manager must be an application that guides the user through updating the system. The Update Applet must be an application which shows a systray icon. This application will check for updates once in a while and notify the user if there are updates.
Both applications must be internationalized/localized and written in C, C++ or Python. The applications should have as little dependencies as possible. The applications must include installation scripts. The applications must be installed in compiled form. Any configuration needed for these tools should be systemwide. We do not need a gui for configuration.
Update Manager
The Update Manager must be an application that guides the user through the steps of updating the system with as little effort and as little user interaction as possible. You are expected to first define the minimal amount of steps required, design the application and then implement the application (gui and internals).
There are two possibilities for this applications:
1. You develop it from scratch.
2. You modify the gnome update manager (used in eg ubuntu) to work with pacman.
We will rely on your expertise to decide which approach is best.
Update Applet
The Update Applet provides a systray icon which checks for system updates in regular intervals. The applet should have a tooltip showing the update status, and a context menu with a few options, such as "Check for updates now", "About" and "start Update Manager". You are expected to design and implement the application.

I don't get why you should allow your users to update their OS(that is their GUI, their kernel, xorg, libc and other _core_ functionality). These components are already quite "great" and shouldn't need upgrading if that is your worry. Only in the case of some new device coming out and the kernel or xorg need to support it i can see the problem. This should happen very rarely though. I mean, why should you allow your OS to be upgraded by some lowly non-tech users. I don't know of many workplaces which allow their users to upgrade their windows versions for example...
You could always upgrade the OS every X years if needed.
If the boss wants his emplyees to be able to download whichever apps/games they want then ofcourse you could allow this, but this should only be allowed if said apps/games doesn't drag in new versions of xorg, kernel versions or other core functionality or its dependencies.
Just blacklist these in pacman.conf and make the file unwritable for the users...
This way you only need external repo for apps which doesn't install without user intervention.
Here i define "core functionality" as all the code responsible for giving a "working computer" as defined by the boss and you if he's not very IT. If you are worried about security and this is why you want a constantly updating machine then just connect all the machines to a router/firewall before they are allowed onto the net. That one could be an arch machine...
Also I haven't tried xfce in a long while but you should watch against giving "windows users/mac users" anything which isn't glitzy and full-featured, because if the users doesn't think the OS have all the functionality they "need" and they don't think it looks fancy enough they have a tendency to go back to whatever OS they came from or try to "upgrade" their own os... which might spell problems for you.
You know, never underestimate the ingeniousness of an idiot.
Just my 5 cents.
Last edited by test1000 (2010-06-25 00:13:42)

Similar Messages

May Release: New partner support, Infrastructure updates, Site templates and bug fixes

Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
Partner support
Infrastructure updates
Features and enhancements
Issues fixed by this release
What's next
You can jump to the corresponding section by clicking the above links.
Partner support
Updated Help & Support partner experience
Following Adobe ID support, we have upgraded BC support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
Support experience for your Small Business owner clients can now be owned by partners (see below).
Custom Help & Support URL for your clients
As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
For more details please read the Improved support workflow and new forums announcement on our blog.
Infrastructure updates
Between our April release and the following infrastructure updates have been enabled
Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in the system through the admin interface or through FTP.
Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.
Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
Features and enhancements
Site templates
To support the increasing number of partners building, sharing or reusing templates to create new sites, we're extending our site templates support from our partner portal with a new template type and improved management support. The update is going to enable partners to mark sites as templates and choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
Business Catalyst Partner fixes
While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
Social plugins integration updates
Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will update the module template to include the corresponding module code snippet from the third party platform provider.
For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
Other changes
Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
BC-Dreamweaver integration performance improvements
Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
Issues fixed by May release
Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
Issue 3162810 - Fixed a bug in rendering engine to prevent content placed between body and head tags being incorrectly moved inside the body tag
Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
Issue 2947989 - CRM passwords are now case sensitive
Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
Business Catalyst new admin interface updates
Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
Updated the confirmation message received after copying a page to match the new workflow and button names
Fixed an issue causing the current screen or section to not be highlighted in the menu
Updated styling on the new dashboard, user management and email accounts interfaces
Updated dashboard reports filters and chart display; made the chart and the filter use the site time zone
Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
Fixed some issues preventing password recovery email from being sent
Removed the alert message displayed when the user or email account limit has been reached
Added localization for the simplified dashboard
Fixed display issues for site limits, domains and user list in the simplified dashboard
Added Custom reports for webBasics plan
Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
Added TOU checkbox in the email account setup screen
Updated Site Preview link in the dashboard to load the default domain
Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
Fixed a broken invite link issue in the Email Account invite email
Updated loading indicators in File Manager and Email Accounts screens
What's next
The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever.
We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

Recommended pacman updates conky script?

Hi,
I have been trying some of the conky pacman updates scripts on the forum/wiki.
So far they either say my system is up to date when in fact pacman -Syu shows otherwise, or they fail to give any info at all.
Can anybody recommend a conky script that is working at this moment in time?:/
Last edited by ancleessen4 (2010-03-03 15:29:45)

Sure-heavily plagiairized from either arch or ubuntu threads...a work in progress...;)
If I find it back I will honour the original author...
# Create own window instead of using desktop (required in nautilus)
own_window yes
own_window_hints undecorated,below,skip_taskbar
own_window_type override
own_window_colour brown
own_window_transparent yes
own_window_hints below
background no
maximum_width 200
# Use double buffering (reduces flicker, may not work for everyone)
double_buffer yes
# fiddle with window
use_spacer right
# Update interval in seconds
update_interval 1
# Minimum size of text area
minimum_size 350 5
# Draw shades?
draw_shades yes
draw_borders no
# Stippled borders?
# stippled_borders 8
# window.border_inner_margin 4
border_width 2
# Default colors and also border colors, grey90 == #e5e5e5
default_color white
default_shade_color black
default_outline_color white
# Text alignment, other possible values are commented
#alignment top_left
alignment top_right
#alignment bottom_left
#alignment bottom_right
# Gap between borders of screen and text
gap_x 10
gap_y 30
# Text stuff
draw_outline no # amplifies text if yes
uppercase no # set to yes if you want all text to be in uppercase
override_utf8_locale no
use_xft yes
xftfont Terminus:size=9
#xftfont Sans:size=8
xftalpha 0.8
text_buffer_size 768
# Force UTF8? note that UTF8 support required XFT
override_utf8_locale yes
color1 333333
color2 cccccc
color3 ddaa00
########## BEGIN FORMATTED DISPLAY ##########
TEXT
${font :size=15}${color red}${alignc}${execi 6000 hostname}${font}${color }
${font :size=8}${alignc}${color lightgrey}$kernel${font}${color }
${hr 1}
${color slate grey}UpTime: ${alignr}${color lightgrey}$uptime${color }
${font StyleBats:size=17}k${font Terminus:size=12} CPU ${font}${hr 2}
${color slate grey}CPU:${color } ${cpu cpu0}% ${cpu cpu1}% ${alignr}${color }$loadavg
${alignc}${cpugraph cpu0 20,90 000000 ffffff} ${cpugraph cpu1 20,90 000000 ffffff}
${color slate grey}cpu0: ${alignr}${color lightgrey}${execi 5 sensors | grep "Core 0" | cut -d "+" -f2 | cut -c1-2}C${color }
${color slate grey}cpu1: ${alignr}${color lightgrey}${execi 5 sensors | grep "Core 1" | cut -d "+" -f2 | cut -c1-2}C${color }
${color slate grey}sda: ${alignr}${color lightgrey}${execi 30 hddtemp /dev/sda | cut -c 31-33}C
${color slate grey}Processes: ${color }${alignr}$processes
${color slate grey}Running: ${color }${alignr}$running_processes
${color slate grey}Top CPU:
${color #ddaa00} ${top name 1}${alignr}${top_mem cpu 1}
${color lightgrey} ${top name 2}${alignr}${top cpu 2}
${color lightgrey} ${top name 3}${alignr}${top cpu 3}
${color lightgrey} ${top name 4}${alignr}${top cpu 4}
${color lightgrey} ${top name 5}${alignr}${top cpu 5}
${color lightgrey} ${top name 6}${alignr}${top cpu 6}
${font StyleBats:size=17}M${font Terminus:size=12} MEMORY ${font}${hr 2}
${color slate grey}RAM: ${alignr}${membar 5,100}
${color slate grey}SWAP: ${alignr}${swapbar 5,100}
${color slate grey}ROOT: ${alignr}${fs_bar 5,100 /}
${color slate grey}HOME: ${alignr}${fs_bar 5,100 /home}
${color slate grey}Top Memory:
${color #ddaa00} ${top_mem name 1}${alignr}${top_mem mem 1}
${color lightgrey} ${top_mem name 2}${alignr}${top_mem mem 2}
${color lightgrey} ${top_mem name 3}${alignr}${top_mem mem 3}
${font StyleBats:size=17}5${font Terminus:size=12} NETWORK ${font}${hr 2}
${color slate grey}Local IP: ${alignr}${color }${addr eth0}
${color slate grey}Public IP: ${alignr}${color }${execi 450 ~/.scripts/externip.sh}
${color}Up: ${color }${upspeed eth0} k/s
${alignc}${upspeedgraph eth0 20,170 000000 ffffff}
${color}Down: ${color }${downspeed eth0}k/s${color}
${alignc}${downspeedgraph eth0 20,170 000000 ffffff}
${font StyleBats:size=17}v${font Terminus:size=12} UPDATES ${font}${hr 2}
${execpi 60 /home/neil/.scripts/pacman-update}${color}
${execpi 3600 paconky /home/neil/.scripts/repos.paconky}
${execpi 3600 paconky /home/neil/.scripts/aur.paconky}
${voffset 900}
Current screen grab;
http://neilhoughton.com/wp-content/uplo … nshot3.png

Security patches without paid support contract?

I've installed S10-u2 on an old E450, and I'm trying to get to the S10 patch cluster. I do not have a paid support contract (and don't particularly intend to get one, either). Is there a way to download the security patches for S10 without a support contract?

If you register the machine with sun update connection using updatemanager
but specify you don't have support contract.
Then updatemanager and smpatch analyze/update should let you download security patches but no others.

[solved]gcc broken after pacman update - libcloog-isl.2.so

Hi,
After a pacman update my gcc broke. When compiling it gives this error:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/cc1: error while loading shared libraries: libcloog-isl.so.2: cannot open shared object file: No such file or directory
gcc -v output:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/src/gcc-4.6-20111223/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --enable-multilib --disable-libssp --disable-libstdcxx-pch --enable-checking=release --with-fpmath=sse
Thread model: posix
gcc version 4.6.2 20111223 (prerelease) (GCC)
and ls /usr/lib/*cloog* output:
/usr/lib/libcloog-isl.a /usr/lib/libcloog-isl.so /usr/lib/libcloog-isl.so.3 /usr/lib/libcloog-isl.so.3.0.0
uname -a:
Linux willem-arch 3.2.4-1-ARCH #1 SMP PREEMPT Sat Feb 4 10:53:01 CET 2012 x86_64 Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz GenuineIntel GNU/Linux
How can I fix this? I already tried installen cloog with pacman but that doesn't help.
edit:
I solved the problem. There was an issue with my pacman.conf. Multilib wasn't properly enabled after the pacman4 transition.
Last edited by pientertje (2012-02-08 09:47:25)

I'm using multilib.
@Allan
more fully than pacman -Syu? Or is my mirror not up to date?
edit:
I solved the problem. There was an issue with my pacman.conf. Multilib wasn't properly enabled after the pacman4 transition.
Last edited by pientertje (2012-02-08 09:46:40)

My Iphone4 Home button sometimes work nicely and sometimes it stop working. India Apple care says they cant give me even paid support because i bought phone from Australia. i don't know what to do. i m disappointed with the product and service support

My Iphone4 Home button sometimes work nicely and sometimes it stop working. India Apple care says they cant give me even paid support because i bought phone from Australia. i don't know what to do. i m disappointed with the product and service support

When you buy an iPhone in the U.S. it's locked to that country with the carrier you bought it for.
If you bought the device unlocked in the U.S. it's unlocked, you can use it on any carrier. Even one's outside the country.
If you want to do a repair on a device you bought in the U.S. and your using it in another country, you must send it back to the U.S. Why? That's where you bought it from.
AppleCare Protection Plans and AppleCare Limited Warranties are registered to your hardware.
Your hardware is your iPhone.
Wherever hardware that was bought then that's the country it was designed to be used in and that's where it was manufactured.
Apple is very localized - if you call U.S. tech support, you'll speak to somone in your country.
So, what does all this mean?
In order to do a repair, you need to send it back to the country you got it from.
And we're all customers like you. We understand that you're upset, but Apple isn't gonna bend the rules to one individual.
Policy is policy. Get over it.

[Solved] errors with keys after pacman update?

Hi,
I installed pacman 4.0.1-4, but now this is what happens when I try and update.
Proceed with installation? [Y/n] Y
(28/28) checking package integrity [######################] 100%
error: binutils-multilib: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: libcap-ng: signature from "Ionut Biru <[email protected]>" is unknown trust
error: cifs-utils: signature from "Tobias Powalowski <[email protected]>" is unknown trust
error: cmake: signature from "Dave Reisner <[email protected]>" is unknown trust
error: colord: signature from "Ionut Biru <[email protected]>" is unknown trust
error: lib32-glibc: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: lib32-gcc-libs: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: gcc-libs-multilib: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: gcc-multilib: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is unknown trust
error: perl: key "6D1655C14CE1C13E" is unknown
error: key "6D1655C14CE1C13E" could not be looked up remotely
error: openssl: signature from "Pierre Schmitz <[email protected]>" is unknown trust
error: git: signature from "Dan McGee <[email protected]>" is unknown trust
error: gpgme: signature from "Dave Reisner <[email protected]>" is unknown trust
error: gvfs: signature from "Dave Reisner <[email protected]>" is unknown trust
error: inetutils: key "FCF2CB179205AC90" is unknown
:: Import PGP key 9205AC90, "Eric Belanger <[email protected]>", created 2011-04-19? [Y/n] Y
error: key "Eric Belanger <[email protected]>" could not be imported
error: intltool: key "FCF2CB179205AC90" is unknown
:: Import PGP key 9205AC90, "Eric Belanger <[email protected]>", created 2011-04-19? [Y/n] ^C
Interrupt signal received
When pacman updated it suggested that I run this command,
sudo pacman-key --init
I know that usually I would say yes to a key and pacman should remember it, but what are all the errors?
Last edited by mich04 (2012-01-20 17:19:26)

# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl -C - -f %u > %o
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options (all disabled by default)
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload
#CheckSpace
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist
[multilib]
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
Here it is.

[SOLVED] Compiz crashes Gnome after pacman update

Hardware: Nvidia NVS 3100M, latest drivers 260.19.36
Software: latest pacman -Suy
On startup, right after the login, X (or Gnome?) crashes and I see the login screen again.
After I disable compiz, I am able to use Gnome desktop.
When I start compiz via fusion-icon, it crashes everything again.
Has anyone seen this?
Any clues?
==== Update =====
I solved this by re-installing the same nvidia driver I had. During install it detected that the original installation "has been altered".
Last edited by softtower (2011-02-16 22:09:49)

That's a scary thought: what if I'm the only one with this problem... :-)
Let me answer your questions guys (and thank you for replying).
First of all, I don't have anything monitor-related in my xorg.conf.d directory. Here is what I have there:
t510 ~: ll /etc/X11/xorg.conf.d/
total 20K
-rw-r--r-- 1 root root 1.1K Aug 24 06:45 10-evdev.conf
-rw-r--r-- 1 root root 377 Jun 21 2010 10-quirks.conf
-rw-r--r-- 1 root root 443 Nov 13 10:36 10-synaptics.conf
-rw-r--r-- 1 root root 267 Nov 19 03:48 10-synaptics.conf.pacnew
-rw-r--r-- 1 root root 107 Sep 2 19:39 20-nouveau.conf
Second, I do pacman updates maybe once a month. So I had 600+ MB of downloads and something like a hundred packages, including xorg itself. However, I do know that the kernel and nvidia's proprietary driver are both latest and haven't changed.
If I delete xorg.conf, arch will try to look for noveau open-source driver and will fail because I do not have it installed: it doesn't manage power well to be used on a laptop.
Looking into Xorg.log I see this:
[ 102.032] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[ 102.032] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
[ 102.032] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
[ 102.032] (EE) NVIDIA(0): you continue to encounter problems, Please try
[ 102.032] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
[ 102.582] (II) NVIDIA(0): NVIDIA GPU NVS 3100M (GT218) at PCI:1:0:0 (GPU-0)
I will try to reinstall the same nvidia driver I have to see what happens.

Alsa not working anymore after pacman update

I had problems with my sound in arch linux. But then I uninstall pulseaudio and then my sound worked.
However, two weeks ago I performed an pacman update and now the sound isn't working anymore.
I provide my configuration data. I did all the obvious stuff like unmute, aplay -L etc. and checking sound with root account.
Can someone help with this problem?
[root@st]# aplay -D sysdefault *.wav
## ==> NO SOUND
# lspci | grep "Audio"
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)
## aplay -L
aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=PCH
HDA Intel PCH, ALC269VC Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
Front speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC269VC Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=NVidia,DEV=0
HDA NVidia, HDMI 0
HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
HDA NVidia, HDMI 1
HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
HDA NVidia, HDMI 2
HDMI Audio Output
## cat /etc/asound.conf
pcm.!default {
type hw
card 0
ctl.!default {
type hw
card 0
## cat /proc/asound/modules
0 snd_hda_intel
1 snd_hda_intel
## lsmod | grep snd
snd_hda_codec_hdmi 30098 1
snd_hda_codec_realtek 39515 1
snd_hda_intel 36904 0
snd_hda_codec 149569 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 6340 1 snd_hda_codec
snd_pcm 77709 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7242 2 snd_pcm,snd_hda_intel
snd_timer 18726 1 snd_pcm
snd 59173 7 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
soundcore 5450 1 snd
## ls /dev/snd/
by-path controlC0 controlC1 hwC0D0 hwC1D0 pcmC0D0c pcmC0D0p pcmC1D3p pcmC1D7p pcmC1D
Last edited by stevebach (2013-11-26 23:12:02)

type hw
Remove your ill-advised /etc/asound.conf - it's bypassing dmix.
To make the correct soundcard the default, there's various methods - google it.

KDEMod 3.5: problems after pacman update

I did a pacman update of KDEMod 3.5, and now, several things don't work anymore:
-there's no desktop background, it's just black
-there's no icons on the desktop: as mentioned above, it's just black (so I think the component that displays wallpaper and icons doesn't work)
-when just starting KDE, there's a "report crash" window (I don't know which the thing that crashes is, it just shows the crash window and I can click it away)
-when choosing "lock session" in the start menu, nothing happens. It used to show screensaver and require password to continue, now it does nothing at all
-maybe some other things I didn't discover yet are also broken...
How can I fix all this? I'd like my system to work properly, like it used to. KDEMod 3.5 appears to have some difficulties after pacman updates these days...
Thanks.
Last edited by aardwolf (2009-08-17 16:37:21)

Hmm, I just realized that the wallpaper is a jpeg, and it could be related to the fix I did in my previous post: http://bbs.archlinux.org/viewtopic.php?id=78076
Are they going to fix those jpeg issues soon? I think this is something vital.
EDIT: FYI: this fixed it: tar -C / -zxvf /var/cache/pacman/pkg/libjpeg-6b-6-i686.pkg.tar.gz usr/lib/libjpeg.so.62 usr/lib/libjpeg.so.62.0.0
Last edited by aardwolf (2009-08-17 16:43:14)

ESS benefits and payment not displaying after support pack update

Hi All,
After the latest HR support pack update ESS benefits and payment not displaying
SAP ECC 604 EPH5
SAP_ABA 702
SAP Kernel : 720_EXT_REL
Kernel Patch number : 439
Netweaver portal version - 7.30
please help
Regards
Rahul

Hi Siddharth & Jwala,
the issue got fixed, by changing the order of Payment above the Benefits
1. i made some options to be disabled & enabled in both benefits and payment
2. Then in the portal i could see the benefits and payment
3. inside the benefits & payment i was able to see two option 1 is for benefits & other is for payment
4. we only wanted payment functionality to be displaying
5. so i tried to hide the benefits then noting was getting displayed in the portal
6. finally i changed the order of the payment just above the benefits
then then i was able to see the benefits and payment inside that i was able to see the payment where i was able to see the payslip
i am not sure what i have done but i is working but please let me know what the problem was actually
Regards
Rahul

Does nokia Lumia 630 support denim update

respected sir myself Amol I want to know that does Nokia Lumia 630 support denim update I am from India if not then when it will be available.
thank you.
best regards,
amol

Hello,
you can check here ([1]) which release is available for your device. For the Lumia 630 in India that is the Cyan release.
[2] reads "For all other Lumia Windows Phone 8 smartphones, the update will start rolling out during Q4 2014, following partner testing and approvals", so I think
it is only a matter of time when the update is deployed to the Lumia 630 in India.
[1]
http://www.microsoft.com/en/mobile/support/software-update/wp8-software-update/wp8-availability-in-asia-pacific/
[2]
http://lumiaconversations.microsoft.com/2014/09/04/lumia-denim-update/
Regards,
Henning Dieterichs
Developer-Hotline for MSDN Online Germany
Disclaimer:
Please take into consideration, that further inquiries cannot or will be answered with delay.
For further information please contact us per telephone through the MSDN-Entwickler-Hotline:
http://www.msdn-online.de/Hotline
For this post by the MSDN-Entwickler-Hotline the following terms and conditions
apply: Trademarks,
Privacy
as well as the separate
terms of use for the MSDN-Entwickler-Hotline .

Fast Pacman Update Checker for bash/zsh

I saw some fancy notifiers using Desktop Notification or the systray on this forum, but nothing suitable for my arch server.
The following snippet check for updates once a day, whenever you spawn a new shell.
#!/bin/bash
# add this to your bashrc/zshrc
function _current_epoch {
echo "$(($(date +%s) / 60 / 60 / 24))"
function _check_updates {
flock -n 9 || return # one concurrent update process at the time
local ignored_pkgs="^linux"
#local updates=`wc -l < /var/log/pacman-updates.log`
local updates=`grep -Ev $ignored_pkgs /var/log/pacman-updates.log | wc -l`
if [ $updates -gt 0 ]; then
echo -n "There are $updates updates. Upgrade? (y/n) [n] "
read line
if [ "$line" = Y ] || [ "$line" = y ]; then
yaourt -Syu --aur
pacman -Qu | sudo tee /var/log/pacman-updates.log >/dev/null
fi
fi
echo "$(_current_epoch)" > $HOME/.pacman-update
) 9> ~/.pacman-update.lck
if [[ $- == *i* ]] && # only interactive shells
[ -e /var/log/pacman-updates.log ] && # only after first update
[ ! -e /var/lib/pacman/db.lck ]; then # not if pacman is running
if [ -e .pacman-update ]; then
read last_epoch < $HOME/.pacman-update
if [[ -n "$last_epoch" ]]; then
if [ $(($(_current_epoch) - $last_epoch)) -ge 1 ]; then
_check_updates
fi
fi
unset last_epoch
else
_check_updates
fi
fi
To keep my package cache up to date I use a systemd.timer unit.
It prefetchs all new packages without installing them or touching the database
#/etc/systemd/timer-daily.timer
[Unit]
Description=Daily Timer
[Timer]
OnBootSec=10min
OnUnitActiveSec=1d
Unit=timer-daily.target
[Install]
WantedBy=basic.target
#/etc/systemd/timer-daily.target
[Unit]
Description=Daily Timer Target
StopWhenUnneeded=yes
#/etc/systemd/timer-daily.target.wants/pacman-update.service
[Unit]
Description=Update pacman's package cache
[Service]
Type=oneshot
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
Environment=CHECKUPDATE_DB=/var/lib/pacman/checkupdate
ExecStartPre=/bin/sh -c "/usr/bin/checkupdates > /var/log/pacman-updates.log"
ExecStart=/usr/bin/pacman --sync --upgrades --downloadonly --noconfirm --dbpath=/var/lib/pacman/checkupdate
Have fun.
UPDATE
Use the safer checkupdates script, so it will not touch the sync database, which prevents dangerous partial system upgrades
UPDATE 2
Do not check for updates if pacman is running. Use Type=oneshot to prevent timeout.
Last edited by Mic92 (2013-07-20 05:04:33)

Tip, look into pacaur philosophy.
Shell helpers seem strange to mix with automation. My habit at shell is to enter pacaur -Syu and say no to the updates unless/until I want what I see, or the update list gets big. In that case I plan a restaurant break to coincide with my manual update.
Autoupdates can run at a particular time like early AM before working hours, when nightowls finally sleep but before morning office rush.

Home Office Network Software Challenges - Post HP Support Assistant Update

Hi
I have an existing home office network setup on an HP Officejet 7410 with assistance from 'Dean' at the end of 2009 / early 2010.
Essentially I have a relatively new HP Compaq 6000 Pro MT Windows 7 32 bit main desktop connected by ethernet to a Netgear DG834GT router, a wirelessly connected Vista Business 32 bit laptop I use when in London and a secondary wirelessly connected family XP Pro Desktop.
All has been running smoothly until fairly recent HP Support Assistant updates for the main desktop - this has caused the HP all in one not to function and corrupted the HP Support Assistant software. I have tried uninstalling the HP 7410 software and have had to use Revo Uninstaller on a medium setting to remove some stubborn programme elements.
I am now unable to reinstall using the Full HP Software suite but have managed to get the printer part working using the basic HP driver download.
Can anyone provide assistance as to how to get back my computer and printer functionality ?
I did try contacting HP support but as it is an old printer they will not provide support (without considerable charge) despite being related to their own HP update software on my somewhat newer (but again out of warranty) Win 7 main desktop.
If I can not solve this problem by uninstalling and reinstalling the software I will be forced to consider a new printer (for which I will get support) but currently the most likely candidate is going to be a move to Epson which would be a shame after over 15 years of sticking with HP.
I look forward to hearing of any possible solutions but please let me know if you need any further info from my end.

Sorry to hear you also have a similar issue. I tried every thing I knew but unfortunately due to the lack of support I gave up ,and ended up purchasing a new printer from a competitor after 15 years of using HP printers. It was a great shame as HP had always been the leading choice for me as a small business.

[Solved] Makepkg aborting after last pacman update

Hi all,
firing makepkg yields:
$ makepkg
==> ERROR: An unknown error has occurred. Exiting...
And therefore this happens also when I try building packages of the AUR with yaourt.
The problem showed up with last pacman update.
What I am I doing wrong?
Thanks for you patience,
Davide
Last edited by flakedave (2010-06-23 22:46:39)

Yeah, version and help are fine.
$ cat /etc/makepkg.conf
# /etc/makepkg.conf
# SOURCE ACQUISITION
#-- The download utilities that makepkg should use to acquire sources
# Format: 'protocol::agent'
DLAGENTS=('ftp::/usr/bin/wget -c --passive-ftp -t 3 --waitretry=3 -O %o %u'
'http::/usr/bin/wget -c -t 3 --waitretry=3 -O %o %u'
'https::/usr/bin/wget -c -t 3 --waitretry=3 --no-check-certificate -O %o %u'
'rsync::/usr/bin/rsync -z %u %o'
'scp::/usr/bin/scp -C %u %o')
# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/curl
# ARCHITECTURE, COMPILE FLAGS
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"
#-- Exclusive: will only run on x86_64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
LDFLAGS="-Wl,--hash-style=gnu -Wl,--as-needed"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
# BUILD ENVIRONMENT
# Defaults: BUILDENV=(fakeroot !distcc color !ccache)
# A negated environment option will do the opposite of the comments below.
#-- fakeroot: Allow building packages as a non-root user
#-- distcc: Use the Distributed C/C++/ObjC compiler
#-- color: Colorize output messages
#-- ccache: Use ccache to cache compilation
BUILDENV=(fakeroot !distcc color !ccache)
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""
# GLOBAL PACKAGE OPTIONS
# These are default values for the options=() settings
# Default: OPTIONS=(strip docs libtool emptydirs zipman purge)
# A negated option will do the opposite of the comments below.
#-- strip: Strip symbols from binaries/libraries in STRIP_DIRS
#-- docs: Save doc directories specified by DOC_DIRS
#-- libtool: Leave libtool (.la) files in packages
#-- emptydirs: Leave empty directories in packages
#-- zipman: Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge: Remove files specified by PURGE_TARGETS
OPTIONS=(strip docs libtool emptydirs zipman purge)
#-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
INTEGRITY_CHECK=(md5)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Directories to be searched for the strip option (if strip is specified)
STRIP_DIRS=(bin lib sbin usr/{bin,lib,sbin,local/{bin,lib,sbin}} opt/*/{bin,lib,sbin})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
# PACKAGE OUTPUT
# Default: put built package and cached source in build directory
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <[email protected]>"
# EXTENSION DEFAULTS
# WARNING: Do NOT modify these variables unless you know what you are
# doing.
PKGEXT='.pkg.tar.xz'
SRCEXT='.src.tar.gz'
# vim: set ft=sh ts=2 sw=2 et:

(paid support) Pacman Update GUI

Similar Messages

Maybe you are looking for