[Bug 1017196] [NEW] when I run 'sudo nautilus' I get the message Syncdaemon not running, waiting for it to start in NameOwnerChanged
Public bug reported: Nautilus doesn't run correcltly, for example the chown command won't work correclty... ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.0.0-21.35-generic-pae 3.0.32 Uname: Linux 3.0.0-21-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Jun 24 12:34:10 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1017196 Title: when I run 'sudo nautilus' I get the message Syncdaemon not running, waiting for it to start in NameOwnerChanged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1017196/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017196] Re: when I run 'sudo nautilus' I get the message Syncdaemon not running, waiting for it to start in NameOwnerChanged
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1017196 Title: when I run 'sudo nautilus' I get the message Syncdaemon not running, waiting for it to start in NameOwnerChanged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1017196/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
That's right, it makes no difference whether I have the drive loaded or not. Not that that matters. You want it to open regardless. -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451282] Re: display is fully dimmed after resume from suspend
Gabe, is it possible to find out the source code that sets the values for brightness and actual_brightness and get them to agree after boot up? It certainly would be better to try to fix it at the upstream source. My limited knowledge of /sys/ directory is that it's mostly created by kernel drivers .. is there a way to get one of the kernel coders to just look at this bug and see if it could be in the kernel code? If so, then I'm sure linus would appreciate getting a bug filed. If you decide to add a fix to /etc/rc.local (or some other script), one problem is that each different graphic card / driver seems to create the /sys/../brightness and /sys/../actual_brightness in different locations. To meet this issue, any script would have to search /sys/ first and then test and assign the appropriate values. Keep in mind that doing this on boot wastes a bit of boot time (milliseconds), but that contradicts one of the goals of ubuntu to cut current boot times in half. regards, -- display is fully dimmed after resume from suspend https://bugs.launchpad.net/bugs/451282 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451282] Re: display is fully dimmed after resume from suspend
Patrick, 1) install the fglrx driver you desire 2) open terminal and enter: $ find /sys/ -iname '*bright*' 3) post back the results and we'll help you with the rc.local script. -- display is fully dimmed after resume from suspend https://bugs.launchpad.net/bugs/451282 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
I'll give it a try. -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
** Bug watch added: GNOME Bug Tracker #617669 https://bugzilla.gnome.org/show_bug.cgi?id=617669 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=617669 Importance: Unknown Status: Unknown -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
It's this number in gnome: https://bugzilla.gnome.org/show_bug.cgi?id=617669 -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
The gnome developer has requested additional information from the affected systems: Bastien Nocera52 [gnome-settings-daemon developer] 2010-05-04 17:43:16 UTC What's the output of gvfs-mount -li on those systems? He is subscribed to this launchpad version, so please post it here. -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
paul :~$ gvfs-mount -li Drive(0): 100 GB Hard Disk Type: GProxyDrive (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sda' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] is_media_removable=0 has_media=1 is_media_check_automatic=0 can_poll_for_media=0 can_eject=0 can_start=0 can_stop=0 start_stop_type=unknown Volume(0): 45 GB Filesystem Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '9E64580A6457E395' unix-device: '/dev/sda2' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(1): 107 MB Filesystem Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '1cf7a6e6-36a7-49eb-8892-238d9522701a' unix-device: '/dev/sda5' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(2): 25 GB Encrypted Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '374ab152-07dc-4450-bfc4-aa9d173cf681' unix-device: '/dev/sda6' themed icons: [drive-harddisk-ata] [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Volume(3): 30 GB LVM2 Physical Volume Type: GProxyVolume (GProxyVolumeMonitorGdu) ids: uuid: '96e2838b-c02c-42f6-988b-5d58ce45dc19' unix-device: '/dev/mapper/sda8_crypt' themed icons: [drive-harddisk] [drive] can_mount=1 can_eject=0 should_automount=0 Drive(1): CD/DVD Drive Type: GProxyDrive (GProxyVolumeMonitorGdu) ids: unix-device: '/dev/sr0' themed icons: [drive-optical] [drive] is_media_removable=1 has_media=0 is_media_check_automatic=1 can_poll_for_media=1 can_eject=0 can_start=0 can_stop=0 start_stop_type=unknown -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
Still not working here. Now that I know it's gnome-settings-daemon, I did aptitude reinstall gnome-settings-daemon and still no success. I opened the menu system preferences keyboard shortcuts and can see the eject listed under the sound section. I tried disabling and re- enabling it, but stil only get the o-s-d eject icon and no tray opening. I tried adding a new shortcut with the command eject and assigned the fn-f10 (xf86eject) to it. The daemon worked and disabled the fn-f10 from the sound : eject section. With this, my tray opens, but the o-s-d icon is missing. So, I reassigned it back to the sound : eject section and now I get the icon but no tray operation. I killed and restarted gnome-settings-daemon in a terminal. I notice the following relevant lines: ** (gnome-settings-daemon:8026): DEBUG: Starting keyboard manager [1272886573,000,xklavier.c:xkl_engine_start_listen/]The backend does not require manual layout management - but it is provided by the application ** Message: NumLock remembering disabled because hostname is set to localhost ** (gnome-settings-daemon:8026): DEBUG: Starting a11y_keyboard manager ** (gnome-settings-daemon:8026): DEBUG: Starting media_keys manager ** (gnome-settings-daemon:8026): DEBUG: Not a valid shortcut: '' ** (gnome-settings-daemon:8026): DEBUG: Not a valid shortcut: '' ** (gnome-settings-daemon:8026): DEBUG: Unable to parse: 'XF86AudioStop' I'm not sure what the Not a valid shortcut:'' is referring to. Any other ideas? Attached is the entire terminal log of the daemon in debug mode (gsddebug.txt) ** Attachment added: gsddebug.txt http://launchpadlibrarian.net/47547160/gsddebug.txt -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 569994] Re: eject hotkey fails to eject cd on gnome lucid
I notice the changelog shows some upstream changes in how the eject action is executed. I suppose this is a regression due to that work. Specifically, on 30 March 2010, this: - Replace eject spawn with GIO code (Bastien Nocera) (#580779) and on 17 Jan 2010, this: - Make eject behave better on OpenBSD (Jasper Lievisse Adriaanse) (#598573) -- eject hotkey fails to eject cd on gnome lucid https://bugs.launchpad.net/bugs/569994 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451282] Re: display is fully dimmed after resume from suspend
Marten, you might want to try something like this in your /etc/rc.local: brt=`cat /sys/devices/virtual/backlight/mbp_backlight/brightness` abrt=`cat /sys/devices/virtual/backlight/mbp_backlight/actual_brightness` logger -t rc.local brightness was $brt , actual_brightness was $abrt if [ $brt != $abrt ] ; then echo $abrt /sys/devices/virtual/backlight/mbp_backlight/brightness afterbrt=`cat /sys/devices/virtual/backlight/mbp_backlight/brightness` logger -t rc.local changed brightness to $afterbrt and actual_brightness is $abrt else afterbrt=`cat /sys/devices/virtual/backlight/mbp_backlight/brightness` logger -t rc.local no brightness change needed, brightness is $afterbrt and actual is $abrt fi This should give you a log entry in /var/log/messages that will show some helpful information when /etc/rc.local executes. So, after booting, check the log with: $ grep bright /var/log/messages and see what happened during boot. It seems like you could have a different problem since your /sys/ entry is different than ours. Take a look in /proc/ to see if you have any more places where brightness is set or shown: find /proc/ -iname '*bright*' hth -- display is fully dimmed after resume from suspend https://bugs.launchpad.net/bugs/451282 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451282] Re: display is fully dimmed after resume from suspend
Thanks Harm. I forgot that != is for strings and strings require quotes. I guess I should have used -ne instead and it probably would have worked. My script failed to set brightness to 7 on a subsequent boot and I had the dim display upon resume again. But, after changing it, it seems to always work now. -- display is fully dimmed after resume from suspend https://bugs.launchpad.net/bugs/451282 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451282] Re: display is fully dimmed after resume from suspend
I wonder if there was a change in how acpi records / sets brightness and gnome-power-manager was not updated to realize it. I notice 2 different kernel locations on my system for brightness. One is /sys/devices/virtual/backlight/acpi_video0/brightness and has the value of 0 on boot up. This seems strange because the lcd is at maximum brightness. The other is /sys/devices/virtual/backlight/acpi_video0/actual_brightness and has the value of 7 on boot up. On my system, 7 is the maximum. I suspect on suspend | hibernate that gnome-power-manager is saving brightness rather than actual_brightness and restoring that upon resume. So, I added this little script to /etc/rc.local to set them the same. brt=`cat /sys/devices/virtual/backlight/acpi_video0/brightness` abrt=`cat /sys/devices/virtual/backlight/acpi_video0/actual_brightness` if (( $brt != $abrt )) ; then echo $abrt /sys/devices/virtual/backlight/acpi_video0/brightness fi Now, on my first suspend the bug does not occur. I'm not sure if this will be the same for everyone. To find out your own brightness, just search /sys/ with this command: paul :~$ find /sys/ -iname '*bright*' /sys/devices/virtual/backlight/acpi_video0/brightness /sys/devices/virtual/backlight/acpi_video0/actual_brightness /sys/devices/virtual/backlight/acpi_video0/max_brightness /sys/devices/pci:00/:00:1e.0/:03:01.1/leds/mmc0::/brightness /sys/devices/pci:00/:00:1e.0/:03:01.1/leds/mmc0::/max_brightness /sys/module/video/parameters/brightness_switch_enabled If your locations are different, then change /etc/rc.local to the different values for yours. regards, -- display is fully dimmed after resume from suspend https://bugs.launchpad.net/bugs/451282 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451282] Re: display is fully dimmed after resume from suspend
This is still a problem on lucid gnome power manager here on a dell inspiron with nvidia 7300 -- display is fully dimmed after resume from suspend https://bugs.launchpad.net/bugs/451282 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515471] Re: nautilus crashed with signal 5 in brasero_burn_caps_get_default()
Only difference is I was trying to write to CD. -- nautilus crashed with signal 5 in brasero_burn_caps_get_default() https://bugs.launchpad.net/bugs/515471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240933] Re: gnome stickykey does not work on openoffice
Now that this problem can be fixed by removing openoffice.org-gtk, it ought to be easier to troubleshoot. Any ideas how to proceed? ** Description changed: With stickykeys set to work, when I press Alt and I in openoffice.org calc, I get the wrong focus. It should go to the main manu and drop down the Insert. But, instead it goes to the menu File Properties. This is the wrong focus. - This is a problem in both gnome and xfce4, but works ok on kde-3. + This is a problem in both gnome and xfce4, but works ok on kde-3 or + kde-4. + + edit 25May09: I recently updated to karmic alpha and experience the same + problem on the latest openoffice.org version 3.1.0. + + However, I notice that if I uninstall the package openoffice.org-gtk + that this problem is fixed. So, the bug appears to be in that package. -- gnome stickykey does not work on openoffice https://bugs.launchpad.net/bugs/240933 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240933] Re: gnome stickykey does not work on openoffice
FWIW, I think these gnome bugs illustrate the problem with accessiblity features in gnome. It appears that decisions were made years ago to avoid fixing these problems and complying with the accessX feature set. And my current bug probably is related to the years' old issue in gnome. At least that's my guess from reading these old bug reports: http://bugzilla.gnome.org/show_bug.cgi?id=95656 http://bugzilla.gnome.org/show_bug.cgi?id=131406 Specifically take note of this comment from 10/30/2003 in 95656: XKB allows this, but it's not clear to me that this behavior is important to users. We _do_ know that the second behavior (latch-to-lock OFF) would cause problems with window navigation in GNOME, so if we do allow the user to switch between behaviors #1 and #2, we will have to deal with the difficult problem of fixing the resulting metacity 'regression'. It seems like gnome has always had the idea that it's too difficult to fix and will cause regressions. ** Bug watch added: GNOME Bug Tracker #95656 http://bugzilla.gnome.org/show_bug.cgi?id=95656 ** Bug watch added: GNOME Bug Tracker #131406 http://bugzilla.gnome.org/show_bug.cgi?id=131406 -- gnome stickykey does not work on openoffice https://bugs.launchpad.net/bugs/240933 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217551] Re: Password prompt freezes system during presence of a drop-down menu [hardy]
same bad news here on jaunty. broadcom 4328 with STA driver. It's a hard freeze that does not respond to Alt-SysRq-REISUB. have to hit power off button. -- Password prompt freezes system during presence of a drop-down menu [hardy] https://bugs.launchpad.net/bugs/217551 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240933] Re: gnome stickykey does not work on openoffice
If you try sticky keys you will never want to go back. Sticky keys are part of the X accessibility package. When enabled, it causes the Control, Alt, Win, and Shift (any modifier) keys to stay engaged until the next key is pressed. For example, if you want to hit the key combination Alt-f to open the file menu, without sticky keys, you must press the Alt and f keys at the same time. For most of us, hitting 2 keys at the same time takes 2 hands. With sticky keys, you can hit the Alt, release it and then hit the f key. It will be interpreted as though they were hit at the same time. This is an extremely helpful feature whenever you're using a cramped keyboard, as most laptops have today. Also, anyone who doesn't want to use a mouse enjoys this feature, because it's easier to use keyboard (combination) shortcuts to get around the desktop. Try it and I think you'll become a user. Unfortunately, if you use gnome, you'll get a buggy implementation (search and you will find other bugs about gnome and sticky keys). But, kde-3.5.x has it implemented perfectly (even better than M$)! -- gnome stickykey does not work on openoffice https://bugs.launchpad.net/bugs/240933 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240933] Re: gnome stickykey does not work on openoffice
Yes this still is a problem. Not only is it a problem within the gnome desktop, it's also a problem within xfce4 desktop. Both are based on gtk. Is it possible that gtk is the problem. I filed this bug on 6/18/08, but no developer has commented. Does that mean it will never get fixed? -- gnome stickykey does not work on openoffice https://bugs.launchpad.net/bugs/240933 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
