[Bug 328903] Re: Opening file-roller causes a warning in ~/.xsession-errors
** Bug watch added: GNOME Bug Tracker #585160 http://bugzilla.gnome.org/show_bug.cgi?id=585160 ** Changed in: fileroller Importance: Undecided => Unknown ** Changed in: fileroller Status: New => Unknown ** Changed in: fileroller Remote watch: None => GNOME Bug Tracker #585160 -- Opening file-roller causes a warning in ~/.xsession-errors https://bugs.launchpad.net/bugs/328903 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 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Output of gnome-settings-daemon --no-daemon --debug attached. ** Attachment added: "debug.log" http://launchpadlibrarian.net/27713499/debug.log ** Attachment removed: "debug.log" http://launchpadlibrarian.net/27713499/debug.log -- GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed https://bugs.launchpad.net/bugs/384439 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
** Attachment added: "gsd-debug.log" http://launchpadlibrarian.net/27713572/gsd-debug.log -- GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed https://bugs.launchpad.net/bugs/384439 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Removing that file doesn't change a thing here. Attaching a strace of g-s-d until the messages appear (no crash here, so no bt). gnome-settings-daemon: Installed: 2.27.1-0ubuntu1 Candidate: 2.27.1-0ubuntu1 ** Attachment added: "strace-gsd.log" http://launchpadlibrarian.net/27712548/strace-gsd.log -- GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed https://bugs.launchpad.net/bugs/384439 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Finally got a stacktrace (some debugging symbols seem to be missing, don't know which ones). ** Attachment added: "btfull-gsd.log" http://launchpadlibrarian.net/27727670/btfull-gsd.log -- GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed https://bugs.launchpad.net/bugs/384439 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Franciscovega's bug seems unrelated and happens earlier than the error
message in this bug. Also there is no segmentation fault. Xrandr plugin
just causes above mentioned errors.
Looking at the strace output right before the messages...
[pid 4818] 01:06:07.208872 access("/home/test/.config/monitors.xml.desired",
F_OK) = -1 ENOENT (No such file or directory)
[pid 4818] 01:06:07.208943 access("/home/test/.config/monitors.xml", F_OK) =
-1 ENOENT (No such file or directory)
[pid 4818] 01:06:07.209003 access("/home/test/.config/monitors.xml.desired",
F_OK) = -1 ENOENT (No such file or directory)
[pid 4818] 01:06:07.209073 write(2, "\n(gnome-settings-daemon:4818): G"..., 99
(gnome-settings-daemon:4818): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
) = 99
...this bug might be connected:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/314406
(also deals with those ~/.config/monitors.xml files).
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
https://bugs.launchpad.net/bugs/384439
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 640807] Re: Forces low refresh rate on CRT monitor
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/640807/+attachment/1595316/+files/Dependencies.txt -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 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 640807] [NEW] Forces low refresh rate on CRT monitor
Public bug reported: Binary package hint: gnome-settings-daemon Starting with version 2.31.91-0ubuntu2, my CRT monitor starts with a refresh rate of 60 Hz (overriding the 75 Hz set in xorg.conf). Using nvidia-settings to manually set it back to 75 Hz works, but after restarting gnome-settings-daemon it's back to 60 Hz. Running g-s-d with --debug shows following when starting the xrandr plugin: ** (gnome-settings-daemon:15901): DEBUG: Activating xrandr plugin ** (gnome-settings-daemon:15901): DEBUG: Starting xrandr manager === clone setup Configuration === Output: Unknown attached to default status: on width: 1280 height: 1024 rate: 53 position: 0 0 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-settings-daemon 2.31.92-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4 Uname: Linux 2.6.35-21-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Sep 16 22:47:21 2010 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick regression-potential ubuntu-une -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 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 640807] Re: Forces low refresh rate on CRT monitor
** Description changed: Binary package hint: gnome-settings-daemon - Starting with version 2.31.91-0ubuntu2, my CRT monitor starts with a + Starting with version 2.31.91-0ubuntu1, my CRT monitor starts with a refresh rate of 60 Hz (overriding the 75 Hz set in xorg.conf). Using nvidia-settings to manually set it back to 75 Hz works, but after restarting gnome-settings-daemon it's back to 60 Hz. Running g-s-d with --debug shows following when starting the xrandr plugin: ** (gnome-settings-daemon:15901): DEBUG: Activating xrandr plugin ** (gnome-settings-daemon:15901): DEBUG: Starting xrandr manager === clone setup Configuration === Output: Unknown attached to default status: on width: 1280 height: 1024 rate: 53 position: 0 0 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-settings-daemon 2.31.92-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4 Uname: Linux 2.6.35-21-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Sep 16 22:47:21 2010 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 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 640807] Re: Forces low refresh rate on CRT monitor
Ok, so this seems to have been triggered by the change in defaults in version 2.31.91-0ubuntu3 (turn on ext. monitors). Setting 'apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup' to false for the user gdm made this bug go away in the current version. That key has been introduced with version 2.31.91-0ubuntu1: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/gnome- settings-daemon/maverick/revision/109/plugins/xrandr/gsd-xrandr- manager.c#plugins/xrandr/gsd-xrandr-manager.c >From the ways to get the value for 'config' in the method 'apply_default_boot_configuration', only 'config = make_laptop_setup (screen);' seems to work (= as soon as enabling turn_on_external_monitors_at_startup, I see the 60 Hz). 'make_clone_setup' and 'make_other_setup' will call 'gnome_rr_mode_get_freq' at some point, which will return bogus because my monitor's EDID is invalid. $ xrandr -q xrandr: Failed to get size of gamma for output default Screen 0: minimum 320 x 175, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 50.0*51.0 53.0 --- Due to all the patches I'm not sure if that's an upstream bug. This should affect all users that have a monitor without EDID (got to be an old one) or invalid EDID (have seen a couple of models on the video driver section of the freedesktop bug tracker). -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 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 642839] Re: Evolution adds 'Sent from Ubuntu' signature by default
A signature is bound to an account, so why not add its definition to the account setup process and prepopulate it with "Sent from Ubuntu", similar like the hostname is prepopulated during the Ubuntu installation? -- Evolution adds 'Sent from Ubuntu' signature by default https://bugs.launchpad.net/bugs/642839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 640807] Re: Forces low refresh rate on CRT monitor
I forgot, you also need to disable this option for the user ('sudo -u
gdm' will only deal with the gdm login screen):
gconftool-2 --type bool -s
"/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup"
false
I guess the easiest way to find out if you are affected by this bug is,
to install the x11-xserver-utils package and run 'xrandr -q' - normally
this should list a proper mode - it doesn't in my case. You can also run
'sudo get-edid' from the read-edid package - if it fails, you'll likely
hit this bug.
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
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 640807] Re: Forces low refresh rate on CRT monitor
Nothing new in the log. I too think that g-s-d isn't the problem but rather triggering the behavior. Thing is, without a xorg.conf I only can chose between low/safe resolutions. With Nvidia's BLOB it's enough to add horizontal and vertical refresh rates, with Nouveau I also need to provide a modeline. Xrandr/X (or however 'gnome_rr_mode_get_freq' from gnome-desktop gets the info) seems to only rely on the monitor's EDID. ** Attachment added: "gsd-debug-randr.log" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/640807/+attachment/1650112/+files/gsd-debug-randr.log -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 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 640807] Re: Forces low refresh rate on CRT monitor
Feel free to rename the bug title as it doesn't seem to fit anymore. :-) -- Forces low refresh rate on CRT monitor https://bugs.launchpad.net/bugs/640807 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 297793] Re: Inconsistent spelling of "Filesystem" (vs. "File system")
Sure, because "Datei System" would be an orthographic mistake
("Deppenleerzeichen"). ;-)
--
Inconsistent spelling of "Filesystem" (vs. "File system")
https://bugs.launchpad.net/bugs/297793
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 420841] Re: karmic nautilus fails to run as root
** Changed in: brasero (Ubuntu) Status: New => Confirmed -- karmic nautilus fails to run as root https://bugs.launchpad.net/bugs/420841 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
This only seems to happen if the source files are on an NTFS parition and you copy more than one file (see updated description). ** Description changed: I just copied a couple of GiB around and noticed that the progress bar on the Nautilus launcher item wasn't working. It looks like the progress bar gets painted in the other direction, but that's just a guess (see - screenshot). I don't know which other applications trigger the progress - bar, so I can just report this for Nautilus. + screenshot). + + This happens when copying more than one file from a NTFS source, e.g. + NTFS -> EXT4 or NTFS -> NTFS. It does not happen with an EXT4 source and + it doesn't happen if it's only one file. TEST CASE: - 1. Open Nautilus and copy a larger file to another location so the progress bar pops up. + 1. Open Nautilus and copy more than one large files from an NTFS partition to another location so the progress bar pops up. RESULT: The progress bar doesn't follow the progress shown in Nautilus' file operation dialog. Using Unity r1486. -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
It also works with FAT32 partitions. I just copied two CD images from a flash drive onto a second Oneiric system and it showed the same behavior. ** Description changed: I just copied a couple of GiB around and noticed that the progress bar on the Nautilus launcher item wasn't working. It looks like the progress bar gets painted in the other direction, but that's just a guess (see screenshot). - This happens when copying more than one file from a NTFS source, e.g. - NTFS -> EXT4 or NTFS -> NTFS. It does not happen with an EXT4 source and - it doesn't happen if it's only one file. + This happens when copying more than one file from a NTFS or FAT32 + source, e.g. NTFS -> EXT4 or FAT32 -> NTFS. It does not happen with an + EXT4 source and it doesn't happen if it's only one file. TEST CASE: 1. Open Nautilus and copy more than one large files from an NTFS partition to another location so the progress bar pops up. RESULT: The progress bar doesn't follow the progress shown in Nautilus' file operation dialog. Using Unity r1486. -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
Oh dear, I'm sorry, but it does NOT seem to be dependent on the filesystem... I now also created an EXT4 partition on the flash drive and on both Oneiric systems the issue occurs. The only time when the progress bar seems to work, is when I copy files from the root partition to the root partition (confirmed on both systems). ** Description changed: I just copied a couple of GiB around and noticed that the progress bar on the Nautilus launcher item wasn't working. It looks like the progress bar gets painted in the other direction, but that's just a guess (see screenshot). - This happens when copying more than one file from a NTFS or FAT32 - source, e.g. NTFS -> EXT4 or FAT32 -> NTFS. It does not happen with an - EXT4 source and it doesn't happen if it's only one file. + The progress bar seems to work fine when staying on the root partition. TEST CASE: - 1. Open Nautilus and copy more than one large files from an NTFS partition to another location so the progress bar pops up. + 1. Open Nautilus and copy more than one large file from one partition to another so the launcher item progress bar pops up. RESULT: The progress bar doesn't follow the progress shown in Nautilus' file operation dialog. Using Unity r1486. -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
Unfortunately it's no fully fixed, as I now cannot see any progress bar at all (in the bad case, the good case works like before). However that fixes at least the bad visual experience. -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
This is not yet fixed. While the graphical glitch is gone (I admit, the more important part here), there are still some cases where the progress bar doesn't show any progress at all whereas the Nautilus file copy dialog works just fine. ** Changed in: nautilus (Ubuntu) Status: Fix Released => New -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
After some more testing: the progress bar seems to fail whenever the copy process total file size is >= 2147483648 bytes. ** Description changed: - I just copied a couple of GiB around and noticed that the progress bar - on the Nautilus launcher item wasn't working. It looks like the progress - bar gets painted in the other direction, but that's just a guess (see - screenshot). - - The progress bar seems to work fine when staying on the root partition. + The progress bar seems to fail showing progress whenever the total file + size limit of the copy process is larger or equal than 2147483648 bytes + (= 2 GiB). TEST CASE: - 1. Open Nautilus and copy more than one large file from one partition to another so the launcher item progress bar pops up. + 1. Create a bad dummy file: + dd if=/dev/zero of=dummy.fail bs=1073741824 count=2 + 2. Create a working dummy file: + cp dummy.bad dummy.good + truncate -s 2147483647 dummy.good + 3. Open Nautilus and copy each one separately to a different place. Filesystems and partitions shouldn't matter. RESULT: - The progress bar doesn't follow the progress shown in Nautilus' file operation dialog. - - Using Unity r1486. + * dummy.good: The progress bar follows the progress shown in Nautilus' file dialog. + * dummy.bad: The progress bar doesn't follow the progress shown in Nautilus' file operation dialog. -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 845188] [NEW] Unity launcher progress bar not working for file sizes >= 2GiB
Public bug reported: The progress bar seems to fail showing progress whenever the total file size limit of the copy process is larger or equal than 2147483648 bytes (= 2 GiB). TEST CASE: 1. Create a bad dummy file: dd if=/dev/zero of=dummy.fail bs=1073741824 count=2 2. Create a working dummy file (one byte less): cp dummy.bad dummy.good truncate -s 2147483647 dummy.good 3. Open Nautilus and copy each one separately to a different place. Filesystems and partitions shouldn't matter. RESULT: * dummy.good: The progress bar follows the progress shown in Nautilus' file dialog. * dummy.bad: The progress bar doesn't follow the progress shown in Nautilus' file operation dialog. Using Nautilus 1:3.1.90-0ubuntu2 on up-to-date Oneiric. ** Affects: nautilus (Ubuntu) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Confirmed -- 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/845188 Title: Unity launcher progress bar not working for file sizes >= 2GiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/845188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 841609] Re: Progress bar overlay not working
Setting status back to fixed on request. ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/841609 Title: Progress bar overlay not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/841609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507263] Re: Light 1px border around desktop
I'm still seeing the BT messages but the audio output works reliably (I didn't remove any BT related packages). espeak: Installed: 1.43-0ubuntu1 Candidate: 1.43-0ubuntu1 Version table: *** 1.43-0ubuntu1 0 500 http://archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status -- Light 1px border around desktop https://bugs.launchpad.net/bugs/507263 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 507263] Re: Light 1px border around desktop
Err, sorry about #16. :-) -- Light 1px border around desktop https://bugs.launchpad.net/bugs/507263 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526437] Re: Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
Yes, it's still an issue on my two testing systems (also confirmed with a current daily live CD). I don't have any custom gnome-terminal keybindings and the value of '/apps/gnome- terminal/keybindings/save_contents' is 'disabled'. -- Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed https://bugs.launchpad.net/bugs/526437 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 136702] Re: nautilus 'replace file' dialog box could give more information
Over eight months after "Great progress is being made on this" - any news on this? -- nautilus 'replace file' dialog box could give more information https://bugs.launchpad.net/bugs/136702 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 518368] Re: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
Although I don't see a segmentation fault, I do get mentioned warning twice every gnome-appearance-properties start. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed https://bugs.launchpad.net/bugs/518368 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
[Bug 518368] Re: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
gdk_display_sync is called four times until the dialog pops up, first and last call causing the warnings. Attaching backtraces and full backtraces of all calls. ** Attachment added: "gdb's 'bt' output for all four calls" http://launchpadlibrarian.net/41228816/gdb_bt_g-c-c.log -- gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed https://bugs.launchpad.net/bugs/518368 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
[Bug 518368] Re: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
** Attachment added: "gdb's 'bt full' output for all four calls" http://launchpadlibrarian.net/41228824/gdb_bt_full_g-c-c.log -- gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed https://bugs.launchpad.net/bugs/518368 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
[Bug 546583] [NEW] Drags the wrong window
Public bug reported: Binary package hint: metacity If I try to drag a window that overlays a previously maximized window, the maximized window will be picked instead. This happens with nvidia-current (not with Nouveau), 'Appearance Preferences > Visual Effects' set to 'None', and only if the other window was maximized using a double click on its title bar (using the maximize button won't trigger the bug). Steps to reproduce (doesn't matter which programs you use): 1.) Open Nautilus (make sure it's not maximized) 2.) Double click on the title bar to maximize it (don't use the window button) 3.) Start gnome-terminal 4.) Try to drag the terminal around => You should be dragging Nautilus instead. Metacity was my best guess, sorry if that's wrong. ProblemType: Bug Architecture: i386 Date: Thu Mar 25 02:40:22 2010 DistroRelease: Ubuntu 10.04 NonfreeKernelModules: nvidia Package: metacity 1:2.28.1-0ubuntu5 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: metacity Uname: Linux 2.6.32-17-generic i686 ** Affects: metacity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 lucid -- Drags the wrong window https://bugs.launchpad.net/bugs/546583 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 546583] Re: Drags the wrong window
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/41900759/Dependencies.txt -- Drags the wrong window https://bugs.launchpad.net/bugs/546583 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 546583] Re: Drags the wrong window
Seems this bug is already known (via https://bugzilla.redhat.com/show_bug.cgi?id=533066): * https://bugzilla.gnome.org/show_bug.cgi?id=608296 - includes the commit that might be responsible (tested and fixes this bug) * https://bugzilla.gnome.org/show_bug.cgi?id=608144 - dupe of above * https://bugzilla.gnome.org/show_bug.cgi?id=600227 - cannot reproduce, but likely connected * https://bugzilla.gnome.org/show_bug.cgi?id=608139 - cannot reproduce, but likely connected Linking to bug 608296 as this looks most promising. ** Bug watch added: Red Hat Bugzilla #533066 https://bugzilla.redhat.com/show_bug.cgi?id=533066 ** Bug watch added: GNOME Bug Tracker #608296 https://bugzilla.gnome.org/show_bug.cgi?id=608296 ** Bug watch added: GNOME Bug Tracker #608144 https://bugzilla.gnome.org/show_bug.cgi?id=608144 ** Bug watch added: GNOME Bug Tracker #600227 https://bugzilla.gnome.org/show_bug.cgi?id=600227 ** Bug watch added: GNOME Bug Tracker #608139 https://bugzilla.gnome.org/show_bug.cgi?id=608139 ** Also affects: metacity via https://bugzilla.gnome.org/show_bug.cgi?id=608296 Importance: Unknown Status: Unknown -- Drags the wrong window https://bugs.launchpad.net/bugs/546583 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 546583] Re: Drags the wrong window
Updated the description: it does happen with Nouveau - I made a mistake during testing. If this is a Metacity bug it will affect all video drivers anyways. ** Description changed: Binary package hint: metacity If I try to drag a window that overlays a previously maximized window, the maximized window will be picked instead. - This happens with nvidia-current (not with Nouveau), 'Appearance - Preferences > Visual Effects' set to 'None', and only if the other - window was maximized using a double click on its title bar (using the - maximize button won't trigger the bug). + This happens with nvidia-current and -nouveau, 'Appearance Preferences > + Visual Effects' set to 'None', and only if the other window was + maximized using a double click on its title bar (using the maximize + button won't trigger the bug). Steps to reproduce (doesn't matter which programs you use): 1.) Open Nautilus (make sure it's not maximized) 2.) Double click on the title bar to maximize it (don't use the window button) 3.) Start gnome-terminal 4.) Try to drag the terminal around => You should be dragging Nautilus instead. Metacity was my best guess, sorry if that's wrong. ProblemType: Bug Architecture: i386 Date: Thu Mar 25 02:40:22 2010 DistroRelease: Ubuntu 10.04 NonfreeKernelModules: nvidia Package: metacity 1:2.28.1-0ubuntu5 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: metacity Uname: Linux 2.6.32-17-generic i686 -- Drags the wrong window https://bugs.launchpad.net/bugs/546583 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Seems fixed for me (no messages while not having any monitor configuration files in ~/.config). Are you sure it's coming from the xrandr-plugin (g-s-d --debug might help)? -- GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed https://bugs.launchpad.net/bugs/384439 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 525220] Re: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `\u0002'
I'm seeing this too. Starting gnome-settings-daemon with '--no-daemon --debug' I get: ... ** (gnome-settings-daemon:10629): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libmedia-keys.so ** (gnome-settings-daemon:10629): DEBUG: Registering GsdMediaKeysPlugin ** (gnome-settings-daemon:10629): DEBUG: Creating object of type GsdMediaKeysPlugin ** (gnome-settings-daemon:10629): DEBUG: GsdMediaKeysPlugin initializing ** (gnome-settings-daemon:10629): DEBUG: Activating media_keys plugin (gnome-settings-daemon:10629): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `\u0002' ** (gnome-settings-daemon:10629): DEBUG: GnomeSettingsManager: emitting plugin-activated media-keys ** (gnome-settings-daemon:10629): DEBUG: Plugin media-keys: active ... ** Attachment added: "valgrind_g-s-d.log" http://launchpadlibrarian.net/39601990/valgrind_g-s-d.log -- IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `\u0002' https://bugs.launchpad.net/bugs/525220 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 526363] [NEW] GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c'
Public bug reported: Binary package hint: gnome-power-manager Seeing this warning in ~/.xsession-errors and when manually starting gnome-power-manager. ProblemType: Bug Architecture: i386 Date: Tue Feb 23 11:50:15 2010 DevkitPower: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 10.04 Package: gnome-power-manager 2.29.2-0ubuntu7 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.32-14-generic i686 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c' https://bugs.launchpad.net/bugs/526363 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 526363] Re: GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c'
** Attachment added: "g-p-m-verbose.log" http://launchpadlibrarian.net/39602471/g-p-m-verbose.log ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39602472/Dependencies.txt ** Attachment added: "GConfNonDefault.txt" http://launchpadlibrarian.net/39602473/GConfNonDefault.txt ** Attachment added: "gnome-power-bugreport.txt" http://launchpadlibrarian.net/39602474/gnome-power-bugreport.txt -- GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c' https://bugs.launchpad.net/bugs/526363 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 526363] Re: GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c'
** Attachment added: "valgrind_g-p-m.log" http://launchpadlibrarian.net/39602495/valgrind_g-p-m.log -- GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c' https://bugs.launchpad.net/bugs/526363 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 526437] [NEW] Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
Public bug reported: Binary package hint: gnome-terminal I'm getting this message upon starting gnome-terminal (starting additional terminals doesn't cause it). ProblemType: Bug Architecture: i386 Date: Tue Feb 23 14:06:26 2010 DistroRelease: Ubuntu 10.04 Package: gnome-terminal 2.29.6-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: gnome-terminal Uname: Linux 2.6.32-14-generic i686 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed https://bugs.launchpad.net/bugs/526437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526437] Re: Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39609413/Dependencies.txt -- Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed https://bugs.launchpad.net/bugs/526437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526437] Re: Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
** Attachment added: "gdb_bt_gnome-terminal.log" http://launchpadlibrarian.net/39609428/gdb_bt_gnome-terminal.log -- Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed https://bugs.launchpad.net/bugs/526437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526437] Re: Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
** Attachment added: "gdb_btfull_gnome-terminal.log" http://launchpadlibrarian.net/39609438/gdb_btfull_gnome-terminal.log -- Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed https://bugs.launchpad.net/bugs/526437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491937] Re: "system" pulldown empty
** Changed in: gnome-menus (Ubuntu) Status: New => Confirmed -- "system" pulldown empty https://bugs.launchpad.net/bugs/491937 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507263] [NEW] Light 1px border around desktop
Public bug reported: Binary package hint: nautilus When creating or renaming objects on the desktop, a light, 1px wide border appears around the desktop (panels and maximized windows do overlap). The border only disappears when killing the process 'nautilus'. Screenshot: http://img.xrmb2.net/images/400173.png See also: http://ubuntuforums.org/showthread.php?t=1379469 ProblemType: Bug Architecture: i386 Date: Thu Jan 14 00:33:58 2010 DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.29.1-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Light 1px border around desktop https://bugs.launchpad.net/bugs/507263 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507263] Re: Light 1px border around desktop
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/37865668/Dependencies.txt ** Attachment added: "usr_lib_nautilus.txt" http://launchpadlibrarian.net/37865669/usr_lib_nautilus.txt -- Light 1px border around desktop https://bugs.launchpad.net/bugs/507263 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507263] Re: Light 1px border around desktop
** Description changed: Binary package hint: nautilus When creating or renaming objects on the desktop, a light, 1px wide border appears around the desktop (panels and maximized windows do overlap). The border only disappears when killing the process 'nautilus'. - Screenshot: http://img.xrmb2.net/images/400173.png + Screenshot: http://img.xrmb2.net/images/837162.png See also: http://ubuntuforums.org/showthread.php?t=1379469 ProblemType: Bug Architecture: i386 Date: Thu Jan 14 00:33:58 2010 DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.29.1-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 -- Light 1px border around desktop https://bugs.launchpad.net/bugs/507263 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 507263] Re: Light 1px border around desktop
Sorry, a bad habit. ** Attachment added: "837162.png" http://launchpadlibrarian.net/37931074/837162.png ** Description changed: Binary package hint: nautilus When creating or renaming objects on the desktop, a light, 1px wide border appears around the desktop (panels and maximized windows do overlap). The border only disappears when killing the process 'nautilus'. - Screenshot: http://img.xrmb2.net/images/837162.png + Screenshot: http://launchpadlibrarian.net/37931074/837162.png See also: http://ubuntuforums.org/showthread.php?t=1379469 ProblemType: Bug Architecture: i386 Date: Thu Jan 14 00:33:58 2010 DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.29.1-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 -- Light 1px border around desktop https://bugs.launchpad.net/bugs/507263 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 508379] Re: Inactive buttons Shutdown and Restart
I'm only seeing this, when X starts in low graphics (fail-safe) mode. ck-list-sessions: Session1: unix-user = '1000' realname = 'test' seat = 'Seat1' session-type = '' active = FALSE x11-display = ':1' x11-display-device = '/dev/tty9' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2010-01-17T00:53:30.119829Z' login-session-id = '' -- Inactive buttons Shutdown and Restart https://bugs.launchpad.net/bugs/508379 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 508379] Re: Inactive buttons Shutdown and Restart
Also prevents auto-mounting: "Unable to mount 2.0 GB Filesystem Not Authorized" -- Inactive buttons Shutdown and Restart https://bugs.launchpad.net/bugs/508379 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 508379] Re: Inactive buttons Shutdown and Restart
I too can't reproduce it anymore and ck-list-sessions now shows 'active = TRUE'. -- Inactive buttons Shutdown and Restart https://bugs.launchpad.net/bugs/508379 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 509532] Re: During updates the terminal changes color
To reproduce, just reinstall one of the xfonts-packages like xfonts-base or xfonts-dpi100. All currently open terminals will change their colors. This will also trigger bug #507263 ( https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/507263 ). -- During updates the terminal changes color https://bugs.launchpad.net/bugs/509532 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 297793] Re: non consistant filesystem spelling in GNOME
** Also affects: hundredpapercuts Importance: Undecided Status: New -- non consistant filesystem spelling in GNOME https://bugs.launchpad.net/bugs/297793 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
** Bug watch added: GNOME Bug Tracker #585690 http://bugzilla.gnome.org/show_bug.cgi?id=585690 ** Also affects: gstreamer via http://bugzilla.gnome.org/show_bug.cgi?id=585690 Importance: Unknown Status: Unknown -- GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed https://bugs.launchpad.net/bugs/384439 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 387912] [NEW] gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
Public bug reported: ~/.xsession-errors is filled with following error message: Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed According to this package's changelog this should already be fixed (upstream bug 580511: http://bugzilla.gnome.org/show_bug.cgi?id=580511), but it doesn't seem fixed (used the small programm provided by Martin Nordholts in the bug report to confirm the problem's still there). ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed https://bugs.launchpad.net/bugs/387912 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 387912] Re: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
With 2.17.2-0ubuntu2 this bug seems really fixed. ** Changed in: gtk+2.0 (Ubuntu) Status: New => Fix Released -- gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed https://bugs.launchpad.net/bugs/387912 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 297793] Re: Inconsistent spelling of "Filesystem" (vs. "File system")
If you decide not to call it "File System"/"Filesystem" you may want to change it in the filebrowser (or file browser ;)) plugin in Gedit too (plugins/filebrowser/gedit-file-bookmarks-store.c, end of function init_special_directories). -- Inconsistent spelling of "Filesystem" (vs. "File system") https://bugs.launchpad.net/bugs/297793 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 387573] Re: Drop-down calendar does not close unless you click on it
@17 What about another gconf-key? There already are keys like 'gmt_time' and 'format' that don't confuse users by not being present in the preferences dialog. -- Drop-down calendar does not close unless you click on it https://bugs.launchpad.net/bugs/387573 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390733] Re: Process gconfd-2 causes cpu overuse and overheat
For me it was fusion-icon, which I had in the startup applications list. Disabling it fixed the problem. Manually starting it brought it back. -- Process gconfd-2 causes cpu overuse and overheat https://bugs.launchpad.net/bugs/390733 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390733] Re: Process gconfd-2 causes cpu overuse and overheat
Sorry for spamming but I was too quick with blaming fusion-icon. In my case it is a problem between metacity and compiz like described in this bug: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/389686 -- Process gconfd-2 causes cpu overuse and overheat https://bugs.launchpad.net/bugs/390733 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 389686] Re: compiz --replace fails to kill metacity, resulting in cpu overload
I can confirm this using a Nvidia 6600 GT with Nvidia 185.18.14 drivers. *) Starting compiz via fusion-icon in the startup applications causes 100% CPU load. Killing either compiz.real or metacity reduces CPU load back to normal. *) Starting compiz manually after session start with 'compiz --replace' causes 100% CPU load. Killing either compiz.real or metacity reduces CPU load back to normal. *) After restarting metacity with 'metacity --replace' I can start compiz with 'compiz --replace' without high CPU load. In my case the high CPU load is caused by gconfd-2, which continuously writes to ~/.gconfd/saved_state Maybe a duplicate or connected: https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/390733 -- compiz --replace fails to kill metacity, resulting in cpu overload https://bugs.launchpad.net/bugs/389686 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 389686] Re: compiz --replace fails to kill metacity, resulting in cpu overload
Ok, this gconfd-2 thing seems to be the result of 'compiz --replace' starting a loop that triggers this bug: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/150721 Addition to above points: *) Starting compiz via setting 'Visual Effects' to 'Normal' in 'Appearance Preferences' (and removing all other compiz/fusion-icon autostart entries) works fine. That's why I couldn't reproduce the problem with a new user - 'Normal' is default and compiz was already running. -- compiz --replace fails to kill metacity, resulting in cpu overload https://bugs.launchpad.net/bugs/389686 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395591] [NEW] Installing GDM 2.26 doesn't update /etc/X11/default-display-manager
Public bug reported: Binary package hint: gdm Opposed to KDM and XDM, GDM doesn't update the file /etc/X11/default- display-manager (or creates it if missing), so I have to manually change (or create) it to contain: /usr/sbin/gdm Also there is no configuration dialog when installing it along with other display managers like there was with GDM 2.20. Having XDM, KDM, and GDM installed and dpkg-reconfiguring XDM: http://img.xrmb2.net/images/39.png Version: gdm 2.26.1-0ubuntu2 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- Installing GDM 2.26 doesn't update /etc/X11/default-display-manager https://bugs.launchpad.net/bugs/395591 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395861] [NEW] gdm 2.26 custom configuration file: wrong filename
Public bug reported: Binary package hint: gdm GDM installs a file /etc/gdm/custom.conf which apparently does not do what its filename suggests: configure GDM. Instead GDM seems to use the file /etc/gdm/gdm.conf-custom for configuration. gdm 2.26.1-0ubuntu2 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gdm 2.26 custom configuration file: wrong filename https://bugs.launchpad.net/bugs/395861 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395698] Re: Autologin gets disabled on upgrade
Are you sure you didn't delete the gdm.conf-custom file manually? I cannot confirm this bug: *) Purged GDM 2.26 (including all GDM related files a file search returned) *) Installed GDM 2.20.10-0ubuntu5, /etc/gdm contained the (empty) gdm.conf-custom *) Used gdmsetup to enable autologin, gdm.conf-custom contained the relevant information *) Upgraded to GDM 2.26.1-0ubuntu2 - gdm.conf-custom still was there holding the autologin information -- Autologin gets disabled on upgrade https://bugs.launchpad.net/bugs/395698 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395861] Re: gdm 2.26 custom configuration file: wrong filename
After reading the documentation (http://library.gnome.org/admin/gdm/stable/configuration.html.en) it's in fact custom.conf that should be used to config GDM. I suggest renaming the bug to something like "gdm 2.26 wrong configuration file used". -- gdm 2.26 custom configuration file: wrong filename https://bugs.launchpad.net/bugs/395861 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395861] Re: gdm 2.26 custom configuration file: wrong filename
Issue #1: Upgrading from 2.20 to 2.26 leaves you with two configuration files. Pretty confusing I'd say - especially because you have to manually configure GDM since there is no graphical tool (yet?) to do it. Issue #2: Fresh installations just install 'custom.conf', which isn't used (yet?) by GDM. Again, if you want to configure GDM you'd probably put the information into that file rather than creating a new file called 'gdm.conf-custom' (which IS used by GDM). -- gdm 2.26 custom configuration file: wrong filename https://bugs.launchpad.net/bugs/395861 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 363298] Re: Debug messages in .xsession-errors
This is no longer an issue. ** Changed in: gnome-panel (Ubuntu) Status: Confirmed => Fix Released -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363298 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 363349] Re: Debug messages in .xsession-errors
This is no longer an issue. ** Changed in: update-notifier (Ubuntu) Status: New => Fix Released -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363349 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 396489] [NEW] gdm 2.26 Unable to log out with autologin enabled
Public bug reported: Binary package hint: gdm When the autologin-user tries to log out he automatically gets logged in again. So you cannot log out user A and log in with user B (switching users works, though). GDM 2.20 always showed the login screen after logging out the autologin- user. gdm 2.26.1-0ubuntu4 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gdm 2.26 Unable to log out with autologin enabled https://bugs.launchpad.net/bugs/396489 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 397192] Re: nautilus becomes non-responsive during video-playback
Downloaded the above linked file (4.2GB). When opening the containing folder (icon view, preview enabled) and clicking on the file, nautilus is gone: 100% CPU (actually 50% of my core duo system), ~1GB RAM usage, unresponsive. I've waited half an hour before killing it. Attaching gdb output while nautilus was hanging (backtrace full, info registers, thread apply all backtrace). Doesn't look helpful to me, but here it is. ** Attachment added: "gdb-nautilus-hang.txt" http://launchpadlibrarian.net/28958237/gdb-nautilus-hang.txt -- nautilus becomes non-responsive during video-playback https://bugs.launchpad.net/bugs/397192 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 397192] Re: nautilus becomes non-responsive during video-playback
** Bug watch added: GNOME Bug Tracker #588446 http://bugzilla.gnome.org/show_bug.cgi?id=588446 ** Also affects: nautilus via http://bugzilla.gnome.org/show_bug.cgi?id=588446 Importance: Unknown Status: Unknown -- nautilus becomes non-responsive during video-playback https://bugs.launchpad.net/bugs/397192 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 363298] [NEW] Debug messages in .xsession-errors
Public bug reported: Binary package hint: gnome-panel Gnome-panel, nm-applet, and update-notifier put messages prefixed with "DEBUG" in the .xsession-errors file. As those aren't errors or warnings, I ask you to remove them for the release. There's already enough noise in this file. Example: ** (nm-applet:3253): DEBUG: applet_common_device_state_changed ** (nm-applet:3253): DEBUG: old state indicates that this was not a disconnect 0 ** (nm-applet:3253): DEBUG: applet_common_device_state_changed ** (nm-applet:3253): DEBUG: old state indicates that this was not a disconnect 0 ** (gnome-panel:3245): DEBUG: Adding applet 0. ** (gnome-panel:3245): DEBUG: Initialized Panel Applet Signaler. ** (gnome-panel:3245): DEBUG: Adding applet 1. ** (gnome-panel:3245): DEBUG: Adding applet 2. ** (gnome-panel:3245): DEBUG: Adding applet 3. ** (gnome-panel:3245): DEBUG: Adding applet 4. ** (gnome-panel:3245): DEBUG: Adding applet 5. ** (gnome-panel:3245): DEBUG: Adding applet 6. ** (gnome-panel:3245): DEBUG: Adding applet 7. ** (gnome-panel:3245): DEBUG: Adding applet 8. ** (gnome-panel:3245): DEBUG: Adding applet 9. ** (gnome-panel:3245): DEBUG: Adding applet 10. ** (gnome-panel:3245): DEBUG: Adding applet 11. ** (gnome-panel:3245): DEBUG: Adding applet 12. ** (gnome-panel:3245): DEBUG: Adding applet 13. ** (nm-applet:3253): DEBUG: applet_common_device_state_changed ** (nm-applet:3253): DEBUG: applet_common_device_state_changed ** (nm-applet:3253): DEBUG: applet_common_device_state_changed ** (nm-applet:3253): DEBUG: foo_client_state_changed_cb ** (nm-applet:3253): DEBUG: applet_common_device_state_changed ** (nm-applet:3253): DEBUG: foo_client_state_changed_cb ** (update-notifier:3252): DEBUG: /usr/lib/update-notifier/apt-check returned 0 (security: 0) ** (update-notifier:3252): DEBUG: crashreport_check gnome-panel: Installed: 1:2.26.0-0ubuntu7 Candidate: 1:2.26.0-0ubuntu7 ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363298 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 363298] Re: Debug messages in .xsession-errors
I see. Should I report this for the other two applications too? -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363298 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 363298] Re: Debug messages in .xsession-errors
Perfectly clear now. I reported them w/o touching the nominate feature. https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/363349 https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/363350 -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363298 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 363298] Re: Debug messages in .xsession-errors
*** This bug is a duplicate of bug 363349 *** https://bugs.launchpad.net/bugs/363349 ** This bug has been marked a duplicate of bug 363349 Debug messages in .xsession-errors -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363298 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 363298] Re: Debug messages in .xsession-errors
** This bug is no longer a duplicate of bug 363349 Debug messages in .xsession-errors -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363298 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 363349] Re: Debug messages in .xsession-errors
Wasn't me. Marking them as invalid and removing the duplicate status of the other bugs (which again will spam I guess - sorry about that). ** Changed in: network-manager-applet (Ubuntu) Status: New => Invalid ** Changed in: gnome-panel (Ubuntu) Status: New => Invalid -- Debug messages in .xsession-errors https://bugs.launchpad.net/bugs/363349 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328903] Re: Opening file-roller causes a warning in ~/.xsession-errors
** Changed in: file-roller (Ubuntu) Status: Incomplete => New -- Opening file-roller causes a warning in ~/.xsession-errors https://bugs.launchpad.net/bugs/328903 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 328903] Re: Opening file-roller causes a warning in ~/.xsession-errors
file-roller: Installed: 2.26.1-0ubuntu1 Candidate: 2.26.1-0ubuntu1 Still there. -- Opening file-roller causes a warning in ~/.xsession-errors https://bugs.launchpad.net/bugs/328903 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 328903] [NEW] Opening file-roller causes a warning in ~/.xsession-errors
Public bug reported: Binary package hint: file-roller Whenever I open file-roller following entries show up in ~/.xsession- errors Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x503 (Archive Ma) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- Opening file-roller causes a warning in ~/.xsession-errors https://bugs.launchpad.net/bugs/328903 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328903] Re: Opening file-roller causes a warning in ~/.xsession-errors
Doesn't seem to happen, when I double-click a compressed file but happens when opening it via "gnome-open file" or "file-roller file". -- Opening file-roller causes a warning in ~/.xsession-errors https://bugs.launchpad.net/bugs/328903 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328903] Re: Opening file-roller causes a warning in ~/.xsession-errors
Sorry for the missing info: file-roller: Installed: 2.25.90-0ubuntu1 Candidate: 2.25.90-0ubuntu1 Version table: *** 2.25.90-0ubuntu1 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status I think you meant file-roller and not gedit? A. Opening a compressed file via terminal: file-roller /url/to/compressed/file => warning in ~/.xsession-errors B. Opening a compressed file via gnome-open (terminal or started via a web browser): gnome-open /url/to/compressed/file => warning in ~/.xsession-errors C. Double-Click on a compressed file => no warning in ~/.xsession-errors -- Opening file-roller causes a warning in ~/.xsession-errors https://bugs.launchpad.net/bugs/328903 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 329028] [NEW] gnome-keybinding-properties: Cannot edit examples for custom keybindings
Public bug reported: Binary package hint: gnome-control-center In gnome-keybinding-properties I have three disabled keybindings under "Custom Shortcuts": 1. "binding" - Disabled starts gconftool-2 --toggle /desktop/gnome/applications/at/screen_magnifier_enabled 2. "binding" - Disabled starts gconftool-2 --toggle /desktop/gnome/applications/at/screen_reader_enabled 3. "binding" - Disabled starts gconftool-2 --toggle /desktop/gnome/applications/at/screen_keyboard_enabled While I can change the names of the entries, their commands cannot be changed (won't be saved). Maybe they should not be placed in "Custom Shortcuts" - without a proper name they are easy to confuse with editable examples. gnome-control-center: Installed: 1:2.25.90-0ubuntu2 Candidate: 1:2.25.90-0ubuntu2 Version table: *** 1:2.25.90-0ubuntu2 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- gnome-keybinding-properties: Cannot edit examples for custom keybindings https://bugs.launchpad.net/bugs/329028 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
[Bug 331292] Re: gdmgreeter crashed with SIGSEGV in __libc_start_main()
Here too using vesa (my nvidia GPU is half dead, nv and nvidia won't work). -- gdmgreeter crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/331292 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 331324] Re: gdmgreeter crashed with SIGSEGV in __libc_start_main()
Vesa (with Nvidia G73M). -- gdmgreeter crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/331324 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 331324] Re: gdmgreeter crashed with SIGSEGV in __libc_start_main()
Fixed. Thanks! -- gdmgreeter crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/331324 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 329028] Re: gnome-keybinding-properties: Cannot edit examples for custom keybindings
Reproducible with today's live CD. 1. Open System > Preferences > Keyboard Shortcuts. 2. Under "Custom Shortcuts" there are three disabled shortcuts (just called "binding"). 3. Change the command of one of the three entries, close "Keyboard Shortcuts", reopen. 4. The initial command will be there again. ~/.xsession-errors shows related warnings: ** (gnome-settings-daemon:5701): WARNING **: Key binding (magnifier) is invalid ** (gnome-settings-daemon:5701): WARNING **: Key binding (screenreader) is invalid ** (gnome-settings-daemon:5701): WARNING **: Key binding (onscreenkeyboard) is invalid -- gnome-keybinding-properties: Cannot edit examples for custom keybindings https://bugs.launchpad.net/bugs/329028 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 329028] Re: gnome-keybinding-properties: Cannot edit examples for custom keybindings
Seems to be two issues: 1. Every custom shortcut that's disabled will fail to parse as valid binding in gsd-keybindings-manager.c and therefor throw this warning (to reproduce add a shortcut, restart GDM, look in ~/.xsession-errors). 2. The command of a custom shortcut can't be changed - it's not limited to those three at-shortcuts (to reproduce add a shortcut, close gnome- keybinding-properties, reopen, edit the command field of the added shortcut, close gnome-keybinding-properties, reopen - initial command is there again). -- gnome-keybinding-properties: Cannot edit examples for custom keybindings https://bugs.launchpad.net/bugs/329028 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 318689] Re: gnome-system-log attempts to open bogus/inexistent logfiles
How can I get rid of gnome-system-log in gconf? Uninstalling (and purging) gnome-utils didn't fix it. I think you just need to check the existence of default_logfiles[i] in logview_prefs_fill_defaults (I did it with fopen - maybe overkill?) but as long as I have the gconf entry present it's not creating the initial logfile list and I cannot test if it works. -- gnome-system-log attempts to open bogus/inexistent logfiles https://bugs.launchpad.net/bugs/318689 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 297793] [NEW] Inconsistent naming of root partition in Nautilus
Public bug reported: Binary package hint: gvfs The names for the root partition in Nautilus' Places panel and main panel (Computer view) differ. Screenshot: http://img.xrmb2.net/images/242451.png Not sure this is gvfs related, though. gvfs: Installed: 1.0.2-0ubuntu1 Candidate: 1.0.2-0ubuntu1 Version table: *** 1.0.2-0ubuntu1 0 500 http://archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status nautilus: Installed: 1:2.24.1-0ubuntu1 Candidate: 1:2.24.1-0ubuntu1 Version table: *** 1:2.24.1-0ubuntu1 0 500 http://archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- Inconsistent naming of root partition in Nautilus https://bugs.launchpad.net/bugs/297793 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 282199] [NEW] New logout/shut down dialogs not showing after upgrade from Hardy
Public bug reported: Binary package hint: gnome-panel In Hardy I was using the compact upstream dialogs for shut down and logout: http://img297.imageshack.us/img297/1803/bildschirmfotognomepanekk5.png I enabled them by creating the gconf key upstream_session in apps/panel/global and setting it to true. After upgrading to Intrepid this key has gone and there is no schema either (so recreating it won't change a thing) but the "old" dialogs are still showing. Using a Live-CD fixes the problem so maybe it's an upgrade related bug. Right package maybe gnome-session, didn't know. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- New logout/shut down dialogs not showing after upgrade from Hardy https://bugs.launchpad.net/bugs/282199 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 282199] Re: New logout/shut down dialogs not showing after upgrade from Hardy
I finally fixed it. I had not only to remove --purge gnome-panel but also to delete everything "gnome-panel" related I could find with gnome- search-tool. I'll do an hardy install tomorrow and see if I can reproduce this problem. -- New logout/shut down dialogs not showing after upgrade from Hardy https://bugs.launchpad.net/bugs/282199 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 282199] Re: New logout/shut down dialogs not showing after upgrade from Hardy
All-clear. I could not reproduce the described situation on the same laptop via a Hardy => Intrepid upgrade. ** Changed in: gnome-panel (Ubuntu) Status: New => Invalid -- New logout/shut down dialogs not showing after upgrade from Hardy https://bugs.launchpad.net/bugs/282199 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 398826] Re: alt f2 not working when panel background color set to "solid color"
** Changed in: gnome-panel (Ubuntu) Status: New => Confirmed -- alt f2 not working when panel background color set to "solid color" https://bugs.launchpad.net/bugs/398826 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403723] Re: gdm 2.27.4 floods daemon.log
** Changed in: gdm (Ubuntu) Status: New => Confirmed -- gdm 2.27.4 floods daemon.log https://bugs.launchpad.net/bugs/403723 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384439] Re: GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
The error is caused by the patch 100_load_desired_settings.patch by
adding:
/* return NULL if the file doesn't exist */
if (!g_file_test (filename, G_FILE_TEST_EXISTS))
{
result = NULL;
return result;
}
to the function configurations_read_from_file() in libgnome-desktop
/gnome-rr-config.c, because it leaves the error passed to the function
uninitialized which later causes the error in gnome-settings-deamon's
xrandr-plugin (gsd-xrandr-manager.c, function
apply_configuration_from_filename()).
Removing that part makes the errors go away but for sure that's not a
proper fix. No patch attached since I don't know how useful patching a
patch is...
--
GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
https://bugs.launchpad.net/bugs/384439
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 409086] [NEW] Disable touchpad while typing: make time configurable via gconf-key
Public bug reported: Binary package hint: gnome-settings-daemon When the option disable-while-typing is enabled, you currently have to wait 0.5 seconds after the last key press before the touchpad gets enabled. In my opinion that's an user preference that should be configurable at least via gconf-editor. gnome-settings-daemon 2.27.5-0ubuntu2 ** Affects: gnome-settings-daemon Importance: Unknown Status: Unknown ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #590783 http://bugzilla.gnome.org/show_bug.cgi?id=590783 ** Also affects: gnome-settings-daemon via http://bugzilla.gnome.org/show_bug.cgi?id=590783 Importance: Unknown Status: Unknown -- Disable touchpad while typing: make time configurable via gconf-key https://bugs.launchpad.net/bugs/409086 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 409086] Re: Disable touchpad while typing: make time configurable via gconf-key
Noted for the next time. -- Disable touchpad while typing: make time configurable via gconf-key https://bugs.launchpad.net/bugs/409086 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
