Gnome-cups-manager and rolling release

can anyone make an update of gnome-cups-manager for voodoo? it as been 6 months since the last one...some help here please

I [03/Jan/2007:07:36:20 -0100] Configured for up to 100 clients.
I [03/Jan/2007:07:36:20 -0100] Allowing up to 100 client connections per host.
I [03/Jan/2007:07:36:20 -0100] Using policy "default" as the default!
I [03/Jan/2007:07:36:20 -0100] Full reload is required.
I [03/Jan/2007:07:36:20 -0100] Loaded MIME database from '/etc/cups': 34 types, 39 filters...
I [03/Jan/2007:07:36:20 -0100] Loading NextJobId from job cache file "/var/cache/cups/job.cache"...
I [03/Jan/2007:07:36:20 -0100] Full reload complete.
I [03/Jan/2007:07:36:20 -0100] Listening to ::1:631 on fd 2...
I [03/Jan/2007:07:36:20 -0100] Listening to 127.0.0.1:631 on fd 3...
E [03/Jan/2007:07:36:20 -0100] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
here is the log of cups...please some help here...

Similar Messages

Gnome-cups-manager error

I installed gnome-cups-manager from TUR: [staging]
The install went fine. I can't find the cups-manager anywhere in
the menus. I then tried as su
# /opt/gnome/bin/gnome-cups-manager
/opt/gnome/bin/gnome-cups-manager: error while loading shared libraries: liblinc.so.1: cannot open shared object file: No such file or directory
iI don't know how to fix this
Thanks
dk

Kind of bad news now, from the looks of it, it won't work with the new gtk or the new gnome or something else that is new on my system, as it won't compile. I will look around for patches and if anyone else can figure out how to get it to work, it would be helpful.
Kritoke

Gnome-power-manager and screen brightness

gnome-power-manager appears to be screwing with my ability to adjust the screen brightness. Now there are only two brightness settings that work - the ones defined in gnome-power-manager settings. Using the keyboard shortcuts "works" in that I can increase the brightness one level but then the change gets overridden. Decreasing the brightness sets it at the minimum level then I can get it back without entering gpm settings. This definitely work before the last update and I think for a while after.
Is there anyway I can get it to listen to manual adjustments?
Edit: I think this was due to the latest hal update.
> lshal | grep bright
laptop_panel.brightness_in_hardware = false (bool)
Edit 2:
Found http://ubuntuforums.org/archive/index.php/t-290994.html
Adding "video" to MOD_BLACKLIST in /etc/rc.conf fixed this. This is just a kernel module right? Nothing else will be screwed...?
Last edited by Allan (2007-10-31 11:30:37)

I have Sony Vaio VGN-FZ38M with Nvidia 8400M GT. I used package 'nvclock' (it is in repo) to control lcd brightness, here site with more info: NVClock. Some time ago I also configured Fn keys to work with it (on Ubuntu), but on Arch I didn't manged but I didn't try hard (in general i don't need, my laptop is stationary all the time). Solution I've found somwehere in Ubuntu forums.
edit: typo in address
edit2:
here's the solution from Ubuntu: http://newyork.ubuntuforums.org/showthr … ?t=1004568
Last edited by folletto (2009-06-14 20:58:56)

Gnome-volume-manager and plugdev

I'm trying to work out some kinks in gnome-volume-manager0--namely, that I cannot unmount disks as a regular user. Everything I have found says that a user must be a member of the plugdev group for such things to work, so I looked around and found that I should be able to add myself to the plugdev groups like so:
usermod -G plugdev isez2001
But upon giving this command, I receive an error saying that the plugdev group is unknown.
Do I have to create the plugdev group myself? If so, why? It really seems like something that should be made to just work.

Alright, I'm a member of the storage group already.
Upon further investigation, I find that my USB flash drive is autmounted in /media under the group "root," and my DVD drive automounts under the group "-1".
I am unable to unmount either of these as a normal user.
Is there something I should do that will make disks mount under the storage group?

Gnome-cups-add printer displays no available drivers?

Hi all, I have a strange problem that I'm not sure how to fix.
I have cups and gnome-cups-manager installed, and all the foomatic files (foomatic-db, foomatic-filters, etc etc), but when I go to add a printer, I am faced with the following dialogue:
Showing that I have foomatic installed...
[owen@oblong ~]$ sudo pacman -Qs foomatic
Password:
local/foomatic-db 3.1-1
Foomatic is a system for using free software printer drivers with common
spoolers on Unix
local/foomatic-db-engine 3.1-1
Foomatic is a system for using free software printer drivers with common
spoolers on Unix
local/foomatic-db-ppd 20060411-2
Foomatic is a system for using free software printer drivers with common
spoolers on Unix
local/foomatic-filters 3.1-1
Foomatic is a system for using free software printer drivers with common
spoolers on Unix
And all the necessary cups & GNOME apps:
[owen@oblong ~]$ sudo pacman -Qs cups
local/cups 1.2.7-1
The CUPS Printing System
local/gnome-cups-manager 0.31-4
A CUPS manager for the Gnome Desktop Environment.
local/libcups 1.2.7-1
The CUPS Printing System
local/libgnomecups 0.2.2-4
GNOME cups library
Any ideas?

I'm having a problem with cups' browser interface nowadays, so there's basically no (gui) way to configure printers. Choosing 'set printer options' sends me to
http://::1/admin/?op=set-printer-options&printer_name=HP_DESKJET_845C_USB_1
and firefox give me
This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.
Isn't there away to use gnome's cups interface, gnome-cups-manager?? Other distributions use it as far as I know.

[SOLVED] last update broke gnome cups support

yesterday I switched to new kernel, new gnome and new cups...system is fine exept for cups support in gnome:
gnome-cups-manager
gnome-cups-manager: error while loading shared libraries: libkrb5.so.25: cannot open shared object file: No such file or directory
what am I missing?
Last edited by pie86 (2010-04-14 18:18:20)

I guess that is an AUR package. You are required to rebuild that yourself.

Gnome-power-manager 2.26 does not suspend on idle

I got a problem with gnome-power-manager 2.26 (several Versions 2.26.0 2.26.1 2.26.2 (original PKGBUILD)). I can suspend from the applet menu. It does hibernate on critical bat level, but i does not suspend on idle, regardless what timeout values I set in screensaver and gnome-power-manager. Display sleep seems to work though. First I thought, this might be only an issue on my particular notebook, as I could not find anything on google about this, but it is the same behavior on my freshly installed desktop system.
gnome-power-manager --verbose outputs nothing about going to standby.
I built gnome-power-manager and gnome-screensaver from 2.24 and they do work porperly, except the notebook will not hibernating on crit bat level.
Hardware:
Notebook: HP Pavilion dv3550eg (centrino2 - Nvidia 9300M GS)
Desktop: GB AMD 790XT, Phenom 720, Nvidia GTX 260
Software:
Arch64
Might this be an Policy issue? Nevertheless if anyone out there has has this problem, let me know and i am goning to file a bug report.

uwinkelvos wrote:I filed a bugrepoert about this: http://bugs.archlinux.org/task/15038
anyone willing and able to have a look at the sources is welcome... i just do not have the skills and tools to get to the right conclusion.
is a well know upstream problem. you should have been fill/comment on bugzilla bugtracker because is not archlinux fault.
http://bugzilla.gnome.org/buglist.cgi?q … r-manager+
http://blogs.gnome.org/hughsie/2009/05/ … tableness/

Udev and gnome-power-manager

Hi,
Recently I upgrade the udev from 141-5-i686 to 145-1-i686 in my MSI wind. Then the following problem begins:
When the system boots this characters can be seen in the screen just before udev is finished: ^@^@
I can add more characters during the whole boot process if I press Fn+F5 (the brightness hotkey).
When gnome is running, in few minutes the screen change the brightness very fast, like blinking. This problem only happens if the gnome-power-manager is enabled.
Downgrading udev fix the problem.
Does anyone know if this is something related with this particular version of udev, or can I do something to fix it?
I don't know if the following messages will help, because them can be seen with the current and with the old udev version. But they are the only ones that I think are related with hotkeys amb modules loading. So I post them just in case.
messages.log:
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd06/26/2008:svnMICRO-STARINTERNATIONALCO.,LTD
:pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:' is
not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d000027A6sv00001462sd00000110bc03sc80i00' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias
name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0F03:PNP0F13:' is not a valid module or alias name
Aug 29 14:57:03 peremsi load-modules.sh: 'usb:v0C45p62C0d0100dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
Aug 29 14:57:08 peremsi ntfs-3g[2611]: Version 2009.4.4 integrated FUSE 27
(so many times) This message is because the kernel do not map some hotkeys. Gnome do it.
atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
atkbd.c: Use 'setkeycodes e078 <keycode>' to make it known.

recently, I updated system, and now I have same problem like you had. I was not sure, what could cause this brightness fast changing. I thought about hal, dbus, udev. Never tried to downgrade udev. Now, I have udev 146. I am not sure what version I had before system upgrading.
Now, I have kernel 2.6.31, and I am not sure if udev 141 will work with this kernel...
I have MSI WIND, also...
Last edited by kunalagon (2010-01-08 11:15:54)

Xfce4 and gnome-network-manager [solved]

I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
Last edited by anarxi (2009-01-14 00:22:42)

quoted from a previous thread
I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
en_US.UTF8 UTF-8
en_US ISO-8859-1
After you've enabled the necessary locales, you have to run locale-gen as root to update them:
# sudo locale-gen
Generating locales...
en_US.UTF-8... done
en_US.ISO-8859-1... done
Generation complete.

Release Management and Dsc - How to queue a build when a release is in progress?

I have VSO and Release Management 2013.4 working and deploying to Azure vm's via DSC
The build profile is set to trigger on commit to the Git repo and the release template is set to be triggered on successful build from TFS
However if a developer commits in quick succession the resultant builds cause releases to overlap in RM? - this causes some of the releases to fail with a DSC error ("the consistency check or pull cmdlet is in progress....")
Is there a way to force RM to prevent concurrent releases? (based on the same release template and build profile)

Thats correct - in this instance its VSO as source control and using the hosted release management to attempt to deploy to azure vms
And yes build takes about 5 minutes but the release template can take up to 15 minutes to run - this means that a second build can cause the same release template to run again (its set to trigger on build)
Error log from RM
xception Message: New deployment is not allowed as an another deployment is in progress. Retry the deployment after sometime. (type OperationFailedException)
Exception Stack Trace: at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.ReadDeploymentResponse(DeploymentResponse response)
at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.DownloadBuilds(DeploymentMachineSpecification deploymentMachineSpecification, AzureStorageSpecification azureStorageSpecification)
at Microsoft.TeamFoundation.Release.EnvironmentProvider.Azure.Implementation.AzureDeploymentProvider.RunScript(String scriptPath, String configurationPath, MachineSpecification machine, StorageSpecification storage, Dictionary`2 configurationVariables)
at Microsoft.TeamFoundation.Release.Tasks.DeployDsc.Execute(DscComponentParametersV2 dscComponentParameters, AzureStorage azureStorage, String[] dnsNameAndUpdatedWinRmPort, String userName, String password, String dscScriptPath, String dscConfigurationPath, Boolean skipCACheck)
at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.DscExecute(DscComponentParametersV2 dscComponentParameters, AzureStorage azureStorage, String[] dnsNameAndUpdatedWinRmPort, String userName, String password, String dscScriptPath, String dscConfigurationPath, Boolean skipCACheck)
at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.DscDeploy(AzureStorage azureStorage, DscComponentParametersV2 dscComponentParameters, String userName, String password, String dscScriptPath, String dscConfigurationPath, String skipCACheck)
at Microsoft.TeamFoundation.Release.Automation.Tasks.DeployDscTask.Execute(IAutomationContext context)
at Microsoft.TeamFoundation.Release.DistributedTask.TaskProcessor.TaskExecutor.Execute(TaskExecutionContext context)

Gnome settings do not take, and gnome-settings-manager breaks things.

I just updated my Arch install. I hadn't done a full system upgrade since December (I think). The install went fine as far as I can tell. It broke my xorg.conf again, but it always does that, no biggie.
My biggest fight seems to be with the gnome-settings-manager. I am now getting no icons in the menus, the mouse runs extremely slow and the only way to get it to run at a normal tracking speed is to use the KDE 'systemsettings' to change it (bizarre). Also, any desktop background that I assign is essentially covered over on startup with a background color and I cannot (using any settings program in the menus) actually put something there. I'm sure there's just some confusion over what is in control of the desktop and which config file is being used, but I cannot find any other mention of this issue in the forums, and forcefully re-installing gnome has yielded no help. I also moved all my '.gnome' dirs under home to some other location, and this made no difference.
Some info:
# pacman -Q gnome-applets gnome-desktop gnome-settings-daemon gnome-session
gnome-applets 2.24.3.1-1
gnome-desktop 2.24.3-1
gnome-settings-daemon 2.24.1-1
gnome-session 2.24.3-1
When I run gnome-mouse-properties from a command line, I see this:
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Then, when I try to change the mouse acceleration:
(gnome-mouse-properties:7165): capplet-common-WARNING **: Unable to find a default value for key for /desktop/gnome/peripherals/mouse/motion_acceleration.
I'll assume it is an integer, but that may break things.
Please be sure that the associated schema is installed
(gnome-mouse-properties:7165): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
(gnome-mouse-properties:7165): GConf-CRITICAL **: gconf_value_get_float: assertion `value->type == GCONF_VALUE_FLOAT' failed
Any ideas?

Just to reinforce what byte said: I had similar problems and moving .gconf worked. If it doesn't, you can also try moving .gnome2. And then if you are versed in the edition of gnome settings files, you can search and repair the faulty ones. If not (like me)... start from scratch, delete the moved dir.
It would be great if the gnome devs simplified the format of settings files (make it more like rc.conf!) and made it so they don't break so often. Maybe a system a la windows where previous versions of the registry get saved. Then upon breakage one could just bring up the last working version. Of course the best thing would be for the settings to not get corrupted in the first place.

SOLVE strange problem with suspend and resume with gnome-power-manager

I have pm-utils and gnome installed.
Suspending and hibernation works well from the command line ($ pm-hibernate and $ pm-suspend). Resuming works without any problems.
Suspending from gnome "Shutdown dialog" works perfectly as well.
However, if suspending is initiated by gnome-power-manager something strange happens: After pressing the power button resuming switches to hibernation and my laptop turns off. Resuming from disk works fine again.
Now, suspending works fine again if I change and save any config file in /etc/pm/.
Here comes the strange thing: It doesn't really matter what I change as long as I save it.
However, as soon as I reboot resuming fails again the way I described above.
Anyone have a clue what's going on?
I get no error messages and I've tried all sorts of boot entries.
Last edited by mehldutt (2007-12-26 19:42:31)

After some try and error my guess is that "HAL" is responsible for this problem:
I deinstalled ACPID and 'pm-utils' and switched to 'uswsusp'.
I made the appropriate changes to the appropriate hal-scrips
usr/lib/hal/scripts/hal-system-power-suspend:
#!/bin/sh
/sbin/s2ram --force
usr/lib/hal/scripts/hal-system-power-hibernate:
#!/bin/sh
/sbin/s2disk
After these changes I still have the same problem: immidiatly after resuming form suspend (via power-button) my laptop hibernates (s2disk).
However, if I delete all entries in "usr/lib/hal/scripts/hal-system-power-hibernate" resuming from suspend works fine again, but hibernate doesn't of course. So, some script must be calling "usr/lib/hal/scripts/hal-system-power-hibernate" emmediatly after resuming from suspend.
A couple of weeks ago everything worked fine. My guess is that one of the recent hal-updates is causing this.
How can I figure what script is calling "usr/lib/hal/scripts/hal-system-power-hibernate" after resuming from suspend?

Gnome-Power-Manager don't save history and statistics

I notice that g-p-m doesn't save history and statistics during a session:
when I reboot the pc I loose every information and the graphs start by 0.
I checked every configuration on gconf-editor, but nothing helped me.
There is the section /apps/gnome-power-manager/info/ but there isn't a schema for any configuration, I don't know what test I could make.
And I don't find the folder ~/.gnome2/gnome-power-manager on my Arch installations.
I found this bug with Ubuntu:
https://bugs.launchpad.net/ubuntu/+sour … bug/302570
So I run lshal | grep battery to have information about my asus eeepc battery.
This is the result:
[root@e3pc luca]# lshal | grep battery
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
battery.charge_level.current = 20871 (0x5187) (int)
battery.charge_level.design = 51034 (0xc75a) (int)
battery.charge_level.last_full = 50638 (0xc5ce) (int)
battery.charge_level.percentage = 41 (0x29) (int)
battery.charge_level.rate = 16993 (0x4261) (int)
battery.is_rechargeable = true (bool)
battery.model = '901' (string)
battery.present = true (bool)
battery.rechargeable.is_charging = true (bool)
battery.rechargeable.is_discharging = false (bool)
battery.remaining_time = 6306 (0x18a2) (int)
battery.reporting.current = 2691 (0xa83) (int)
battery.reporting.design = 6580 (0x19b4) (int)
battery.reporting.last_full = 6529 (0x1981) (int)
battery.reporting.rate = 2191 (0x88f) (int)
battery.reporting.technology = 'Li-ion' (string)
battery.reporting.unit = 'mAh' (string)
battery.serial = '' (string)
battery.technology = 'lithium-ion' (string)
battery.type = 'primary' (string)
battery.vendor = 'ASUS' (string)
battery.voltage.current = 7756 (0x1e4c) (int)
battery.voltage.design = 8400 (0x20d0) (int)
battery.voltage.unit = 'mV' (string)
info.capabilities = {'battery'} (string list)
info.category = 'battery' (string)
info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0' (string)
Eeepc hasn't the serial. Ok...
But on my hp 6735s there is the serial of the battery while I run "lshal | grep battery".
And it has the same problem.
The version of g-p-m is 2.26.2-1 on both of them.
I had many difficulties to find documentation about this gnome daemon!!
Somebody found a solution?
Thank you all!

up

Replacement for package manager and packagekit (Gnome)

Hello everyone,
following up to https://bbs.archlinux.org/viewtopic.php?id=191276 (removal of packagekit to be able to upgrade pacman to 4.2), and given the fact that packagekit had been flagged deprecated for quite some time,
does anyone have a suggestion for a desktop replacement for gnome-packagekit?
Thanks in advance

For GTK based environment I use pamac-aur. Simple packet manager, update manager and update notifier (in fact for update notification I use aarchup with systemd timer scheduling)

Firewire and gnome-volume-manager

I have a firewire scanner, when hotplugged, nothing happens in gnome. I have 'run when scanner is plugged' checked, but I get nothing.
Does gnome-volume-manager work with firewire devices? or is it just my scanner? (Canon 2540 photo)

I don't know about scanners, but my firefire external HD is recognised perfectly by gnome-volume-manager. So it does listen for firewire devices. Maybe you'll need to add something to udev to make gnome-volume-manager know it's a scanner?
I have a scsi scanner, so I won't try hotplugging it

Gnome-cups-manager and rolling release

Similar Messages

Maybe you are looking for