[Bug 706764] Re: dphys-swapfile sets incorrect swap size
My machine is just a basic Ubuntu 10.04 LTS Lucid server. It does have the 'bc' calculator installed but not 'dc'. 'dc' being RPN is also quite obtuse to understand being stack based which might the code difficult to maintain. 'expr' can be a pain to use with all the quoting needed but I see that used quite a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706764 Title: dphys-swapfile sets incorrect swap size -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706764] Re: dphys-swapfile sets incorrect swap size
Hi Alex, I tried to run the fix you show for development snapshot on my machine but it says this: The program 'dc' is currently not installed. You can install it by typing: apt-get install dc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706764 Title: dphys-swapfile sets incorrect swap size -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706764] Re: dphys-swapfile sets incorrect swap size
** Tags removed: fixed-in-debian fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706764 Title: dphys-swapfile sets incorrect swap size -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164968] Re: [Upstream] [hardy] OpenOffice.org doesn't sends an User Agent
This also prevents OpenOffice from being able to access many webdav servers who filter on the user agent string to determine allowable webdav clients. I tested this against a webdav server using OOo Writer v3.1.1 and the user agent string delivered by OOo was blank and the server refused to allow access due to the blank user agent string. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/164968 Title: [Upstream] [hardy] OpenOffice.org doesn't sends an User Agent -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706764] Re: dphys-swapfile sets incorrect swap size
When I look at upstream 20061020-3:
MEMSIZE="`head -1 /proc/meminfo | awk '{ print $2 }'`"
looks like it still might be high by a factor of 1024 since MEMSIZE is in
megabytes and meminfo is in kilobytes.
That is why my patch adjusted for the difference:
MEMSIZE=$(($(cat /proc/meminfo | awk '/^MemTotal/ { print $2 }') / 1024))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706764
Title:
dphys-swapfile sets incorrect swap size
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706764] Re: dphys-swapfile sets incorrect swap size
** Patch added: "dphys-swapfile.patch" https://bugs.launchpad.net/bugs/706764/+attachment/1804396/+files/dphys-swapfile.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706764 Title: dphys-swapfile sets incorrect swap size -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706764] [NEW] dphys-swapfile sets incorrect swap size
Public bug reported: Binary package hint: dphys-swapfile In Ubuntu 10.04 LTS Lucid. Package: dphys-swapfile does not set the proper swap file size. It currently looks at /proc/kcore to determine the memory size and in my machine this file is 0 bytes. Attaching patch. ** Affects: dphys-swapfile (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706764 Title: dphys-swapfile sets incorrect swap size -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
cloud-init does a lot of things. I guess what I'm looking for is whether cloud-init could be made to emit events as it works such that other upstart jobs can listen for those events and then use them to trigger their startup as opposed to waiting for the entire cloud-init process to complete. eg: cloud-init: initctl emit hostname myjob: start on hostname -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
Scott, I just tested a recent Maverick AMI and it does indeed correctly set the hostname to the newly assigned internal domain name after a stop/start sequence. So no need to open any other bugs on that score. + uname -n ip-10-117-39-235 + hostname -s ip-10-117-39-235 + hostname -d ec2.internal + hostname -f ip-10-117-39-235.ec2.internal + hostname ip-10-117-39-235 + echo ip-10-117-39-235 ip-10-117-39-235 + cat /etc/hostname ip-10-117-39-235 + /sbin/sysctl -n kernel.hostname ip-10-117-39-235 Now the question is how early in the boot process does cloud-init run? With the changes in this bug, how can we make another boot process wait until cloud-init has completed setting up the hostname? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
Now since my cluster filesystem starts real early in the bootup (S20) I need the hostname to be set correctly even earlier. So that would probably require some upstart job to run at S10. So now I need to see how cloud-init is doing this and if it is early in the bootup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
Running the following commands appears to correctly set all the forms of hostname on my Lucid ec2 instance: echo "$(curl -s http://169.254.169.254/latest/meta-data/local-hostname)" | sed 's:\..*$::' > /etc/hostname /sbin/sysctl -w kernel.hostname="$(curl -s http://169.254.169.254/latest /meta-data/local-hostname | sed 's:\..*$::')" logout/login shell root@ip-10-XXX-181-59:~# uname -n ip-10-XXX-181-59 root@ip-10-XXX-181-59:~# hostname -s ip-10-XXX-181-59 root@ip-10-XXX-181-59:~# hostname -d ec2.internal root@ip-10-XXX-181-59:~# hostname -f ip-10-XXX-181-59.ec2.internal root@ip-10-XXX-181-59:~# hostname ip-10-XXX-181-59 root@ip-10-XXX-181-59:~# echo $HOSTNAME ip-10-XXX-181-59 root@ip-10-XXX-181-59:~# cat /etc/hostname ip-10-XXX-181-59 root@ip-10-XXX-181-59:~# /sbin/sysctl -n kernel.hostname ip-10-XXX-181-59 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
When hostname is properly working on a system all of the following commands should work as expected: #uname -n #hostname -a #hostname -s #hostname -d #hostname -f #hostname Source: http://www.debianadmin.com/change-hostname-or-server-name-of-a -linux-machine.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
As the ec2 meta-data, local-hostname, returns the long form of hostname, I would also propose that an enhancement that a new ec2 meta-data attribute be added: local-shortname that would return the short version of hostname such as is returned from 'hostname -s' on a properly configured system. This would make it easier for users to get the hostname format that they need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop
This fix is needed for Lucid as well. I have a clustered filesystem that fails because of this bug. It relies upon the hostname value always being set correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596993 Title: hostname handling needs improvement for elastic-ip and ebs start-stop -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
Opened a kernel bug about this problem: https://bugzilla.kernel.org/show_bug.cgi?id=26702 . ** Bug watch added: Linux Kernel Bug Tracker #26702 http://bugzilla.kernel.org/show_bug.cgi?id=26702 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
>>> 1. The problem was fixed when I went through the 3mb/second channel. That's probably because it was a different controller or the hardware at least differed sufficiently enought so as to not exhibit the problem. >>> 2. I had to re-install the OS completely due to data corruption caused by the READ FDMA QUEUED errors. Don't expect your system to work properly until you've re-installed. I've had no problem getting 'fsck.ext4' to repair the minimal amount of problems that were caused so far. My system remounts the filesystem read-only immediately upon detection of errors so nothing else can be written and maybe that helped reduce any corruption. Nevertheless, this is certainly a very serious problem and this bug warrants a high priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
Tried adding libata.force=noncq to 2.6.37-12-server kernel boot line and the errors are changed to READ DMA EXT. This particular machine has a Gigabtye M/B. Some details: # lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx) 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5) 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller 00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller 00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a) 00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller 00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300 Graphics 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) 03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
Cabling is fine. I just tried to run 'sudo apt-get update' and it is telling me that I need to run 'dpkg --configure -a'. When I do that it tries to reconfigure the new kernel package again. So the read errors must have prevented the configure from completing. But the read errors will not let this kernel package configure run to completion even now so I'm stuck. Cannot run apt-get till I figure out how to get the configure to finish without triggering all these errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
I just went and upgraded to kernel 2.6.37-12-server from kernel-ppa and after rebooting into it I'm still see the same READ FPDMA QUEUED errors I was before. Both drives in the machine check out fine according to the drive tests. I've noticed a little unexplained freezing up and releasing the past couple days and then today it started with these errors almost constantly. And I'm trying to remember what packages I might have updated recently that could have contributed to this issue. I'm also going to check all the cabling in the server to make sure nothing has worked loose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
And I just checked and my south bridge is an AMD SB750 with 6 SATA. I'm using AHCI mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
It also generates filesystem errors such that I have to run fsck on the next boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550559] Re: hdd problems, failed command: READ FPDMA QUEUED
I'm seeing this same error with Lucid x86_64 and kernel 2.6.32-21. My drive is a Hitachi 500GB SATA. Once this error starts I get hung task timeouts and the systems starts freezing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550559 Title: hdd problems, failed command: READ FPDMA QUEUED -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591532] Re: ata errors { DRDY ERR } { ABRT } in Lucid
I've got this same DRDY ERR occurring on one of my machines, and once it
started it continues to show this error.
I did a drive test on the drives and no errors were found. So this is
definitely something with the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591532
Title:
ata errors { DRDY ERR } { ABRT } in Lucid
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408417] Re: No option to log in remotely via XDMCP
This removal of XDMCP affects us as well. Why is the LTS release (Lucid) marked as Won't Fix? This is a critical piece of functionality that has been removed from Ubuntu without any advance notice or warning. Please fix this for the LTS release (Lucid). -- No option to log in remotely via XDMCP https://bugs.launchpad.net/bugs/408417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: PolicyKit authentication always fails
*** This bug is a duplicate of bug 221363 *** https://bugs.launchpad.net/bugs/221363 As the reporter, it seemed as if you were trying to push aside this bug. I'm glad to hear that is not the case. Thank you. I have no problem with it being marked as a duplicate of a true bug that is for exactly the same problem. But the last time it was marked duplicate it was for a different problem. The title of this latest duplicate Bug #221363 looks like it would be the same problem. Both of these bugs need raised to Highest priority in my opinion. Users hitting this bug have no idea that it is underlying policykit that is causing all the problem. -- PolicyKit authentication always fails https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: PolicyKit authentication always fails
Milan, excuse me, but closing this report is ridiculous. It is NOT at all a feature request. This is clearly a bug, a bad bug, and it needs fixed. A lot of research and symptoms are detailed in this report that will be useful for those trying to fix this issue. And the problem needs to be assigned. -- PolicyKit authentication always fails https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: PolicyKit authentication always fails
I am remote logged into the machine using vnc/ssh/nx and this behavior is extremely undesirable. Nobody would expect this type of behavior. I have remote logged into machines for years like this and never saw this type of behavior. -- PolicyKit authentication always fails https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: PolicyKit authentication always fails
$ ps PID TTY TIME CMD 12237 pts/300:00:00 bash 19027 pts/300:00:00 ps $ pkcheck --action-id org.freedesktop.systemtoolsbackends.set --allow-user-interaction --process 12237 Not authorized. $ pkcheck --action-id com.ubuntu.systemservice.setproxy --allow-user-interaction --process 12237 Not authorized. And yes, I knew about the difference between adduser and useradd. I always use 'adduser'. The default 'ubuntu' user is a member of the following groups: adm dialout cdrom floppy audio dip video plugdev fuse lpadmin netdev admin ubuntu -- PolicyKit authentication always fails https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: PolicyKit authentication always fails
I logged out the user and started a new session: I went to try accessing Users and Groups from the menu and got the same behavior as before. Only the Password button for the current user worked, nothing else. $ ps PID TTY TIME CMD 12237 pts/300:00:00 bash 12284 pts/300:00:00 ps $ pkcheck --action-id org.freedesktop.systemtoolsbackends.set --allow-user-interaction --process 12284 Error checking for authorization org.freedesktop.systemtoolsbackends.set: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: stat() failed for /proc/12284: No such file or directory $ ps PID TTY TIME CMD 12237 pts/300:00:00 bash 12484 pts/300:00:00 ps $ pkcheck --action-id org.freedesktop.systemtoolsbackends.set --allow-user-interaction --process 12484 Error checking for authorization org.freedesktop.systemtoolsbackends.set: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: stat() failed for /proc/12484: No such file or directory $ ps PID TTY TIME CMD 12237 pts/300:00:00 bash 12573 pts/300:00:00 ps $ ps PID TTY TIME CMD 12237 pts/300:00:00 bash 12994 pts/300:00:00 ps $ pkcheck --action-id com.ubuntu.systemservice.setproxy --allow-user-interaction --process 12994 Error checking for authorization com.ubuntu.systemservice.setproxy: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.CheckAuthorization() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: stat() failed for /proc/12994: No such file or directory $ ps PID TTY TIME CMD 12237 pts/300:00:00 bash 13039 pts/300:00:00 ps pkcheck is now killing the process!! The user is in the admin group. Now for root: # ps PID TTY TIME CMD 13535 pts/300:00:00 su 13543 pts/300:00:00 bash 13568 pts/300:00:00 ps # pkcheck --action-id org.freedesktop.systemtoolsbackends.set --allow-user-interaction --process 13543 # ps PID TTY TIME CMD 13535 pts/300:00:00 su 13543 pts/300:00:00 bash 13750 pts/300:00:00 ps # pkcheck --action-id com.ubuntu.systemservice.setproxy --allow-user-interaction --process 13543 # root works fine. So some observations: It looks like to me that some of the tools like 'useradd', 'adduser' need to be updated so that they put the user into the 'admin' group on those installations that rely on PolicyKit. Since the menues were not working using these tools was the only way that I could add users to the system but obviously they knew nothing about PolicyKit and they need to. Even with the users in the admin group the access still isn't working even if you restart polkitd. -- PolicyKit authentication always fails https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: PolicyKit authentication always fails
# cat /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:admin The users were not members of 'admin' group. I added them and reran the tests. Still got the exact same results. It didn't seem to make any difference. $ ps PID TTY TIME CMD 20575 pts/000:00:00 ps 31357 pts/000:00:00 bash $ $ pkcheck --action-id org.freedesktop.systemtoolsbackends.set --allow-user-interaction --process 31357 Not authorized. $ pkcheck --action-id com.ubuntu.systemservice.setproxy --allow-user-interaction --process 31357 Not authorized. -- PolicyKit authentication always fails https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 And here is Session 26: Session26: unix-user = '1002' realname = 'TEST USER' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/pts/2' remote-host-name = '' is-local = TRUE on-since = '2010-06-29T20:41:12.373274Z' login-session-id = '4294967295' idle-since-hint = '2010-06-29T20:42:01.010623Z' -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 Created a user 'test' with a password: $ sudo adduser test Adding user `test' ... Adding new group `test' (1002) ... Adding new user `test' (1002) with group `test' ... Creating home directory `/home/test' ... Copying files from `/etc/skel' ... Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully Changing the user information for test Enter the new value, or press ENTER for the default Full Name []: TEST USER Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] Y Then did: $ sudo su - test $ users-admin (users-admin:10699): Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Malformed message was sent # ** (process:32132): DEBUG: system-bus-name::1.231589 is inquiring whether system-bus-name::1.231671 is authorized for org.freedesktop.systemtoolsbackends.self.set ** (process:32132): DEBUG: user of caller is unix-user:root ** (process:32132): DEBUG: user of subject is unix-user:test ** (process:32132): DEBUG: checking whether system-bus-name::1.231671 is authorized for org.freedesktop.systemtoolsbackends.self.set ** (process:32132): DEBUG: 0x13e9c30 ** (process:32132): DEBUG: subject is in session /org/freedesktop/ConsoleKit/Session26 (local=1 active=0) ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/30-site.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/30-site.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/50-local.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/50-local.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/90-mandatory.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/90-mandatory.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/30-site.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/30-site.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/50-local.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/50-local.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/90-mandatory.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/90-mandatory.d' ** (process:32132): DEBUG: not authorized ** (process:32132): DEBUG: It gives the exact same result as the accounts w/o password. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 The user does not have a password. All users are keyed access. # ck-list-sessions Session20: unix-user = '1001' realname = 'David Reno' seat = 'Seat18' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/ssh' remote-host-name = 'XX.XX.XX.XX' is-local = FALSE on-since = '2010-06-29T17:33:27.204342Z' login-session-id = '4294967295' Session21: unix-user = '1001' realname = 'David Reno' seat = 'Seat19' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/ssh' remote-host-name = 'XX.XX.XX.XX' is-local = FALSE on-since = '2010-06-29T17:33:27.207013Z' login-session-id = '4294967295' Session23: unix-user = '1001' realname = 'David Reno' seat = 'Seat21' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/ssh' remote-host-name = 'XX.XX.XX.XX' is-local = FALSE on-since = '2010-06-29T17:33:39.108880Z' login-session-id = '4294967295' IP hidden... I have three open distinct sessions to this user. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 # ps -ef | grep polkitd root 2552 1 0 15:33 ?00:00:00 /usr/lib/policykit-1/polkitd # killall polkitd # ps -ef | grep polkitd # # sudo /usr/lib/policykit-1/polkitd & [1] 32132 # Registering null backend at priority -10 ** (process:32132): DEBUG: Added `/var/lib/polkit-1/localauthority/10-vendor.d' as a local authorization store ** (process:32132): DEBUG: Added `/etc/polkit-1/localauthority/10-vendor.d' as a local authorization store ** (process:32132): DEBUG: Added `/var/lib/polkit-1/localauthority/20-org.d' as a local authorization store ** (process:32132): DEBUG: Added `/etc/polkit-1/localauthority/20-org.d' as a local authorization store ** (process:32132): DEBUG: Added `/var/lib/polkit-1/localauthority/30-site.d' as a local authorization store ** (process:32132): DEBUG: Added `/etc/polkit-1/localauthority/30-site.d' as a local authorization store ** (process:32132): DEBUG: Added `/var/lib/polkit-1/localauthority/50-local.d' as a local authorization store ** (process:32132): DEBUG: Added `/etc/polkit-1/localauthority/50-local.d' as a local authorization store ** (process:32132): DEBUG: Added `/var/lib/polkit-1/localauthority/90-mandatory.d' as a local authorization store ** (process:32132): DEBUG: Added `/etc/polkit-1/localauthority/90-mandatory.d' as a local authorization store ** (process:32132): DEBUG: Monitoring `/var/lib/polkit-1/localauthority' for changes ** (process:32132): DEBUG: Monitoring `/etc/polkit-1/localauthority' for changes Using authority class PolkitBackendLocalAuthority # ps -ef | grep polkitd root 32132 24906 0 19:17 pts/100:00:00 /usr/lib/policykit-1/polkitd Logged in as a regular user (davidr) and accessing Users and Groups from menues and then selecting current user and clicking on the Change button for Name: # ** (process:32132): DEBUG: system-bus-name::1.231589 is inquiring whether system-bus-name::1.231663 is authorized for org.freedesktop.systemtoolsbackends.self.set ** (process:32132): DEBUG: user of caller is unix-user:root ** (process:32132): DEBUG: user of subject is unix-user:davidr ** (process:32132): DEBUG: checking whether system-bus-name::1.231663 is authorized for org.freedesktop.systemtoolsbackends.self.set ** (process:32132): WARNING **: skipping unknown tag <_description> at line 12 ** (process:32132): WARNING **: skipping unknown tag <_message> at line 13 ** (process:32132): WARNING **: skipping unknown tag <_description> at line 21 ** (process:32132): WARNING **: skipping unknown tag <_message> at line 22 ** (process:32132): WARNING **: skipping unknown tag <_description> at line 30 ** (process:32132): WARNING **: skipping unknown tag <_message> at line 31 ** (process:32132): WARNING **: skipping unknown tag <_description> at line 39 ** (process:32132): WARNING **: skipping unknown tag <_message> at line 40 ** (process:32132): WARNING **: skipping unknown tag <_description> at line 11 ** (process:32132): WARNING **: skipping unknown tag <_message> at line 12 ** (process:32132): WARNING **: skipping unknown tag <_description> at line 15 ** (process:32132): WARNING **: skipping unknown tag <_message> at line 16 ** (process:32132): DEBUG: (nil) ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/30-site.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/30-site.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/50-local.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/50-local.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/90-mandatory.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/90-mandatory.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/10-vendor.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/etc/polkit-1/localauthority/20-org.d' ** (process:32132): DEBUG: Dropping all .pkla caches for directory `/var/lib/polkit-1/localauthority/30-site.d' ** (process:32132): D
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 I do not have the time at the moment to create another fresh install of Lucid using ubuntu-server followed by ubuntu-desktop. I've been reading the wiki entry about PolicyKit. But there is nothing that says anything about accounts w/o password. And the 'users-admin' command worked so I didn't need to kill policykitd. Was there anything else? -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 I wouldn't say it's completely different. Just maybe that the permissions aspect of the bug has been solved but there are still other related errors showing. Without sudo: $ users-admin (users-admin:18974): Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Malformed message was sent And the window button behavior is as I described from the menu. Only Password button for current user is accessible. No other buttons for anything else work. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295405] Re: Fails to run lib/dbus-1.0/dbus-daemon-launch-helper: not owned by the messagebus group
I reinstalled 'dbus' and this cleared the error but I'm seeing strange behavior. Logged in as a regular user. Time and Date: all greyed out and "you are not authorized...", no prompt to enter root password. Users and Groups: can only change Password for current user, the other Change buttons do nothing and can do nothing with any other users. I posted more details in my original bug: Bug #598909 -- Fails to run lib/dbus-1.0/dbus-daemon-launch-helper: not owned by the messagebus group https://bugs.launchpad.net/bugs/295405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 I reinstalled 'dbus' and this cleared the error but I'm seeing strange behavior. Logged in as a regular user. Time and Date: all greyed out and "you are not authorized...", no prompt to enter root password. Users and Groups: can only change Password for current user, the other Change buttons do nothing and can do nothing with any other users. Just for background info: The 'root' account on this machine is linked to 'ubuntu' account sudo. And there is no password, when you 'sudo' from ubuntu account it automatically goes to 'root' account without password. So, if I get into a terminal and from one of the regular user accounts do: $ sudo time-admin Then the time and date window displays fully accessible to all functions. $ sudo users-admin (users-admin:5154): Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. After about a minute, then the Users and Groups window displays fully accessible to all functions. But clearly there is still a problem. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 Also, look back and you'll see that I've reinstalled all the requested packages. It didn't change anything. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 Scroll just a little bit. You have my strace here in comment #5 https://bugs.launchpad.net/ubuntu/+source/system-tools- backends/+bug/598909/comments/5 -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 *** https://bugs.launchpad.net/bugs/295405 $ jockey-gtk Traceback (most recent call last): File "/usr/bin/jockey-gtk", line 417, in sys.exit(u.run()) File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 428, in run self.ui_show_main() File "/usr/bin/jockey-gtk", line 101, in ui_show_main self.update_tree_model() File "/usr/bin/jockey-gtk", line 277, in update_tree_model for h_id in self.get_displayed_handlers(): File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 772, in get_displayed_handlers return self.backend().available(self.argv_options.mode) File "/usr/lib/python2.6/dist-packages/jockey/ui.py", line 98, in backend self._dbus_iface = Backend.create_dbus_client() File "/usr/lib/python2.6/dist-packages/jockey/backend.py", line 686, in create_dbus_client obj = bus.get_object(DBUS_BUS_NAME, '/DeviceDriver') File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 244, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 241, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 183, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 281, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success I've tried changing the permissions as you suggested and that did not help at all. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295405] Re: Fails to run lib/dbus-1.0/dbus-daemon-launch-helper: not owned by the messagebus group
It did not seem to matter that the launcher was group as 'messagebus'. It still generated the error even after I changed the group. In my case it was a fresh install of Ubuntu Lucid server and followed by an install of ubuntu-desktop. Those were the main packages. -- Fails to run lib/dbus-1.0/dbus-daemon-launch-helper: not owned by the messagebus group https://bugs.launchpad.net/bugs/295405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295405] Re: fails to run lib/dbus-1.0/dbus-daemon-launch-helper
Seriously, a user cannot be expected to get into a terminal and go searching their entire system trying to fix up GIDs that were incorrectly set by some package. That isn't even a possible general workaround. This bug is a SHOWSTOPPER for Ubuntu Lucid. The majority of users are not going to know how to properly setup a user or group account from the command line and get /etc/skel files copied and anything else that needs set. Most users are going to use the menues and go System | Administration | Users and Groups and hit the error which prevents them from doing anything with Users or Groups. There is an underlying bug here in some package that is incorrectly setting the wrong GID or looking at the wrong GID in /etc/group. The bug I opened, Bug #598909, right now does not appear to be a duplicate of this bug. All the other cases seem to be centered around duplicate GID's. That is not the case with Bug #598909. If you want them linked then forget about duplicate GID's entirely. There is something else going on here. -- fails to run lib/dbus-1.0/dbus-daemon-launch-helper https://bugs.launchpad.net/bugs/295405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
*** This bug is a duplicate of bug 295405 ***
https://bugs.launchpad.net/bugs/295405
This is NOT the same problem! This is not a duplicate bug. The other
cases were about duplicated GID's.
# grep messagebus /etc/passwd
messagebus:x:102:108::/var/run/dbus:/bin/false
# grep 108 /etc/group
messagebus:x:108:
There is no duplicated GID as there was in the cases in the other bugs.
# awk -F: '{print $3}' /etc/group | sort -u | wc -l
66
# awk -F: '{print $3}' /etc/group | sort | wc -l
66
As you can see there are no duplicated GID's of any kind.
I changed the group on /lib/dbus-1.0/dbus-daemon-launch-helper from avahi to
messagebus and it didn't change anything. Still getting the same error.
--
Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
https://bugs.launchpad.net/bugs/598909
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
If I change the UID for messagebus it will be the same id as haldaemon so I don't think I should do this. Really I can see nothing wrong with the ids. There are no duplicated id's. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
Ok, here is some more info: # ls -l /lib/dbus-1.0/dbus-daemon-launch-helper -rwsr-xr-- 1 root avahi 47520 2010-03-30 18:43 /lib/dbus-1.0/dbus-daemon-launch-helper # cat /etc/group | grep -e 108 -e avahi messagebus:x:108: avahi-autoipd:x:111: avahi:x:112: # cat /etc/passwd | grep -e messagebus -e 108 -e avahi messagebus:x:102:108::/var/run/dbus:/bin/false avahi-autoipd:x:103:111:Avahi autoip daemon,,,:/var/lib/avahi-autoipd:/bin/false avahi:x:104:112:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false haldaemon:x:108:115:Hardware abstraction layer,,,:/var/run/hald:/bin/false # sudo strace -s 4096 -f -o /tmp/trace -p `ps h -o %p -U messagebus` Process 409 attached - interrupt to quit Process 21785 attached Process 21786 attached Process 21786 detached Process 21785 detached Process 21851 attached Process 21852 attached Process 21852 detached Process 21851 detached # ck-list-sessions ** (ck-list-sessions:21850): WARNING **: Failed to get list of seats: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success ** Attachment added: "strace" http://launchpadlibrarian.net/50996955/trace -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
What I got out of the other bugs comment was that it needs to be checked that there is not two groups using same ids. I don't see that as the case here. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] Re: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success
The UID for user 'messagebus' is already 102. Not sure what you are asking there. # apt-cache policy liboobs-1-4 liboobs-1-4: Installed: 2.30.0-0ubuntu1 Candidate: 2.30.0-0ubuntu1 Version table: *** 2.30.0-0ubuntu1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status # apt-get install --reinstall liboobs-1-4 Reinstalling liboobs made no difference, still have error. -- Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 598909] [NEW] System|Administration|Users and Groups: The configuration could not be loaded.
Public bug reported: Binary package hint: system-tools-backends I am running lucid with system-tools-backends at 2.9.4 and am seeing errors trying to run any of: Time and Date Users and Groups example: $ users-admin (users-admin:12353): Liboobs-WARNING **: There was an unknown error communicating with the backends: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success $ gksu users-admin (users-admin:12389): Liboobs-WARNING **: There was an unknown error communicating with the backends: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success $ gksudo users-admin (users-admin:12413): Liboobs-WARNING **: There was an unknown error communicating with the backends: Failed to execute program /lib/dbus-1.0/dbus-daemon-launch-helper: Success I checked and /etc/groups did not appear to be overwritten, but the commands still do not work either from the menu or the command-line. # cat /etc/issue Ubuntu 10.04 LTS \n \l # uname -m x86_64 # apt-show-versions gnome-system-tools system-tools-backends gnome-system-tools/lucid uptodate 2.30.0-0ubuntu2 system-tools-backends/lucid uptodate 2.9.4-0ubuntu1 Don't know if any of this is related but here is messagebus group related info from /etc/group and /etc/passwd: # grep messagebus /etc/group messagebus:x:108: # grep 108 /etc/group messagebus:x:108: # grep 108 /etc/passwd messagebus:x:102:108::/var/run/dbus:/bin/false haldaemon:x:108:115:Hardware abstraction layer,,,:/var/run/hald:/bin/false # apt-cache policy system-tools-backends gnome-system-tools system-tools-backends: Installed: 2.9.4-0ubuntu1 Candidate: 2.9.4-0ubuntu1 Version table: *** 2.9.4-0ubuntu1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status gnome-system-tools: Installed: 2.30.0-0ubuntu2 Candidate: 2.30.0-0ubuntu2 Version table: *** 2.30.0-0ubuntu2 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status # apt-get install --reinstall system-tools-backends gnome-system-tools Reinstalled these packages but it made no difference at all, still have the error. ** Affects: system-tools-backends (Ubuntu) Importance: Undecided Status: New -- System|Administration|Users and Groups: The configuration could not be loaded. https://bugs.launchpad.net/bugs/598909 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 160862] Re: users-admin (System->Administration->Users and Groups) overwrites group file
Ok, if you think this is not related I'll be glad to open a new bug. I do think this is the same underlying problem though. Also: # apt-show-versions liboobs liboobs not installed (even not available) There is no such package. -- users-admin (System->Administration->Users and Groups) overwrites group file https://bugs.launchpad.net/bugs/160862 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
