[Bug 984574] Re: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()
Booted AMD x64 Desktop CD as "Try Ubuntu" on my desktop machine to see how it would handle my FireMV video card. No install done - I'm running the live CD. 8GB memory. Went to the Dash Home, typed "n", selected Network. Selected All Settings. Selected Network. Died. Repeatable. Every time. I can open any number of other Settings entries, but I can't open Network twice. It always dies on the second try. Once, even opening another Settings icon also caused it to die (after starting with Network). I have one onboard 1G NIC, two PCI 100M NICs, one USB 1G NIC (that's four "Wired" entries). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/984574 Title: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/984574/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984574] Re: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui()
** This bug is no longer a duplicate of bug 672930 Feature request for movie export menu: display zoom scale -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/984574 Title: [network]: gnome-control-center crashed with SIGSEGV in refresh_ui() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/984574/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 855967] Re: vinagre crashed with SIGSEGV in g_type_check_instance_cast()
So vinaigre crashed (Ubuntu 11.04) and sent me through the bug reporting process, collecting 50MB of reporting information and uploading it all. Here in Launchpad, I was offered two similar crashes and asked if either matched mine. Of course one did, so I chose it. As far as I can tell, Launchpad then threw away all my uploaded crash report tracing info and simply added my name to the "this affects me" count. Now that I open up this bug, I see that it is "Incomplete" requiring a "useful symbolic stack trace". For all I know, my crash had one, but Launchpad in its wisdom threw away my stack trace when it decided that my crash was similar to this one. Shouldn't Launchapd *always* upload the additional crash report info for developers to look at, rather than throwing it away, especially for bugs marked "Incomplete - need stack trace"? I have the dump sitting here at home if you want me to do something with it: 126 Oct 27 13:10 _usr_bin_vinagre.777.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/855967 Title: vinagre crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/855967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 801449] Re: gconftool-2 crashed with SIGABRT in raise()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/801449 Title: gconftool-2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/801449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 467169] Re: keyboard shortcuts UI issues; fails to set shortcut
These bugs still exist in Maverick. 10.10 Maverick: Open: System | Preferences | Keyboard Shortcuts. Verfify that "Toggle maximization state | ALT+F10" works on a window. Disable the keyboard shortcut with "Backspace". BUG: The UI shows "Disabled", but ALT+F10 still toggles maximization. At this point, the UI shows no mapping for ALT+F10, but the shortcut still maximizes windows. Disable has done nothing. Map "Toggle maximization state" to ALT+MOD4+F10 and verify that it works. Note that ALT-F10 now does nothing, as expected. Disable the keyboard shortcut with "Backspace". BUG: The UI shows "Disabled", but ALT+MOD4+F10 still toggles maximization. At this point, the UI shows no mapping for ALT+MOD4+F10, but the shortcut still maximizes windows. Disable has done nothing. Map "Toggle screen reader" to ALT+MOD4+F10. Disable the keyboard shortcut with "Backspace". Map "Toggle maximization state" to ALT+MOD4+F10. Now, ALT+MOD4+F10 does nothing, and no amount of playing around will get it to do anything. I cannot assign ALT+MOD4+F10 to anything else. It seems that any shortcut that you assign to "Toggle screen reader" gets killed and made useless for anything else. If you try to assign ALT+F11 or ALT+SHIFT+F11 to two functions, it will correctly complain and tell you in the reassignment that one will be disabled. But you can assign ALT+MOD4+F10 or ALT+MOD4+F11 to multiple functions and it won't complain at all. One of the functions might work; the others will be ignored. Map "Toggle maximization state" to ALT+F12 and verify it toggles. Disable the keyboard shortcut with "Backspace". BUG: The UI shows "Disabled", but ALT+F12 still toggles maximization. Map "Toggle shaded state" to ALT+F12. BUG: ALT+F12 still toggles maximization, even though the UI says it should toggle shaded state. Map "Toggle maximization state" to anything other than ALT+F12. Now ALT+F12 correctly toggles shaded state. This is a mess. -- keyboard shortcuts UI issues; fails to set shortcut https://bugs.launchpad.net/bugs/467169 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 515806] Re: nautilus crashed with SIGFPE in g_object_unref()
I'm using 10.10 now and haven't seen the problem yet, but I don't auto- umount my home dir any more because I need my cron jobs to keep working. -- nautilus crashed with SIGFPE in g_object_unref() https://bugs.launchpad.net/bugs/515806 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515935] Re: causes Xorg to consume CPU unless Gnome is running
This problem does not happen in Ubuntu 10.10 x86_64. -- causes Xorg to consume CPU unless Gnome is running https://bugs.launchpad.net/bugs/515935 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead
Same problem in Firefox 3.6.3 in Ubuntu 10.4. What's the best way to report the same bug in newer software? Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3 Linux linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux |~[5253] ls -l /var/lib/apt/periodic/ total 8 drwxr-xr-x 2 root root 4096 May 27 08:04 ./ drwxr-xr-x 6 root root 4096 Jun 2 05:25 ../ -rw-r--r-- 1 root root0 Jun 2 00:31 update-stamp -rw-r--r-- 1 root root0 Jun 2 01:57 update-success-stamp -- Gdk-WARNING **: XID collision, trouble ahead https://bugs.launchpad.net/bugs/401823 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 515806] Re: nautilus crashed with SIGFPE in g_object_unref()
What's a "retracer" and why and what would it remove? Should I change all my login passwords? I think this bug might be related to the bug where cron jobs cause the ecrypted $HOME to unmount. I bet I logged in just as some cron job caused $HOME to unmount, causing Nautilus to fault. -- nautilus crashed with SIGFPE in g_object_unref() https://bugs.launchpad.net/bugs/515806 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515935] Re: causes Xorg to consume CPU unless Gnome is running
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/38658319/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/38658320/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/38658321/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/38658322/XsessionErrors.txt -- causes Xorg to consume CPU unless Gnome is running https://bugs.launchpad.net/bugs/515935 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515935] [NEW] causes Xorg to consume CPU unless Gnome is running
Public bug reported: Binary package hint: gnome-system-monitor If I run gnome-system-monitor under Gnome, my Xorg process uses one or two percent of one CPU core and this seems normal. If I shut down Gnome and run gnome-system-monitor with *no* window manager (only Xorg), or with "vtwm" as my window manager, the Xorg process use goes over 15% on one of the four cores. Killing gnome- system-monitor causes the Xorg CPU use to drop back to near zero. This makes gnome-system-monitor somewhat unusable except when Gnome is running. I did not expect Xorg CPU use to become unreasonable when gnome-system-monitor is run under a non-Gnome environment. ProblemType: Bug Architecture: amd64 Date: Tue Feb 2 04:15:03 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) Package: gnome-system-monitor 2.28.0-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LC_COLLATE=C LANG=C LC_CTYPE=en_CA.utf8 ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: gnome-system-monitor Uname: Linux 2.6.31-17-generic x86_64 ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- causes Xorg to consume CPU unless Gnome is running https://bugs.launchpad.net/bugs/515935 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515806] Re: nautilus crashed with SIGFPE in g_object_unref()
** Visibility changed to: Public -- nautilus crashed with SIGFPE in g_object_unref() https://bugs.launchpad.net/bugs/515806 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 466948] Re: keyboard shortcuts disable requires logout/login
> Thank you for your bug report. The issue is an upstream one and it > would be nice if somebody having it could send the bug the to the people > writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME) Please fix the spelling of "writing". This having to report bugs twice is not friendly: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/467169/comments/3 -- keyboard shortcuts disable requires logout/login https://bugs.launchpad.net/bugs/466948 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 466948] Re: keyboard shortcuts disable requires logout/login
I already gave one example: "e.g. "Minimize window / ALT-F9". The UI says "disabled" but the shortcut still works, until logout/login." Here are others that, after I disable them and the UI shows "Disabled", are not actually disabled but continue to work: Show the panel's "Run Application" dialog box Show the panel's main menu Take a screenshot Activate the window menu Toggle maximization state Minimize window etc. See also the same problem here: https://bugs.launchpad.net/bugs/467169 I use the standard 9.10 install into a new VMware. The install did not ask me about any desktop "effects", so I don't know what they might be. -- keyboard shortcuts disable requires logout/login https://bugs.launchpad.net/bugs/466948 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 467169] Re: keyboard shortcuts UI issues; fails to set shortcut
I find this Gnome bug reporting process via Ubuntu to be discouraging, unfriendly, and in need of reworking. I've just spent a bunch of my time researching and documenting a bug, registering it with Launchpad, searching for duplicates, and reporting it. Now Ubuntu tells me: "we don't write this software; go login somewhere else and repeat the whole process somewhere else". I read other Ubuntu bugs where others are being told the same thing. This is discouraging. You should have told me to go elsewhere at the time I was first reporting the bug, so that I wouldn't duplicate all the login and search work: "Thank you for attempting to report a Gnome bug, but the piece of software you are listing isn't written by Ubuntu and so any work you do registering with Ubuntu Launchpad and searching for duplicate bugs will be wasted, because we're going to tell you the bug isn't our problem. Rather than waste your time, please go directly to the people who write the software and report the bug there." Even when telling me to go somewhere else, you use jargon words such as "upstream" that I'm sure mean nothing to most Ubuntu users. The Wiki you sent me to should say in the opening lines: "You've been sent here because your bug report needs to go directly to the people who wrote the software. Here's how to transfer a Launchpad bug report to be a Gnome bug report. Follow these steps." "If you've already gone to all the trouble of creating a Launchpad account, searching for duplicates, and submitting your Gnome bug, then we're sorry to say your time has been wasted unless you also create a Gnome Bugzilla account, again search for duplicates, again submit a bug report, and then link your Bugzilla bug to your Launchpad bug (and vice-versa). You have to do the work twice, otherwise nobody will know about the bug." The first several screens worth of text in the Wiki don't even mention Launchpad, and they don't say why I was sent there or what to do. The first sentence on the Wiki page again uses the jargon word "upstream" without explaining what it means. Instead of a prominent heading "Transfer Launchpad bug report to Gnome", I have to look several screens down under "Filing new bugs" to know what needs to be done. The points in that section aren't even ordered correctly - the bullet item "open a new bug" appears *before* the title "Before submitting a new bug". Why not just put the steps in order, rather than telling people, after the fact, what they should have done? And who is going to read all the way to the bottom line on the page, where you are told to link your Launchpad bug to your Bugzilla bug? Why not put that right into the bullet list of points on what to do? This isn't friendly. Can I (or someone else) rewrite that Wiki page into a single, numbered list of steps to follow? -- keyboard shortcuts UI issues; fails to set shortcut https://bugs.launchpad.net/bugs/467169 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 467047] Re: Keyboard Shortcuts window ignores maximize
* Is this reproducible? * If so, what specific steps should we take to recreate this bug? Yes. To recreate it, do what I said to do, above: Try to use a keyboard shortcut to "maximze" the window. Does nothing. Set your "Titlebar Action" to be "Maximize Vertically" and then double-click on the title bar of the window. Does nothing. Dragging with the mouse works. * Do you use compiz therE? I don't know what that is. I did a standard install of 9.10 into an empty VMware virtual machine. It never asked me about compiz. -- Keyboard Shortcuts window ignores maximize https://bugs.launchpad.net/bugs/467047 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 467169] Re: keyboard shortcuts UI issues; fails to set shortcut
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34799140/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/34799142/XsessionErrors.txt -- keyboard shortcuts UI issues; fails to set shortcut https://bugs.launchpad.net/bugs/467169 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 467169] [NEW] keyboard shortcuts UI issues; fails to set shortcut
Public bug reported: Binary package hint: gnome-control-center Fresh install of 9.10 karmic into VMWare running on 8.10. Keyboard Shortcuts are mangled under 9.10 karmic. (They may be mangled under previous releases, but I didn't ever try to use them. This is my first try to use Gnome instead of vtwm.) Watch this: 9.10 Karmic: Open System | Preferences | Keyboard Shortcuts. Verfify that "Move between windows immediately | ALT+Escape" is working. Disable it with "Backspace". BUG: The UI shows "Disabled", but ALT+Escape still moves between windows. At this point, the UI should show no mapping for ALT+Escape, but the shortcut still tries to move between windows. Map "Switch to workspace on the left of the current workspace" to "ALT+Escape" and verify that it works (bringing up a little desktop viewer menu that says "Desk 1"). Disable it with "Backspace". BUG: The UI shows "Disabled", but ALT+Escape still switches workspaces. At this point, the UI should again show no mapping for ALT+Escape, but the shortcut still tries to switch workspaces. Map "Move between windows immediately" to "ALT+Escape" again. Try to use it. BUG: It doesn't work - ALT+Escape still tries to switch workspaces. Disable it with "Backspace". BUG: The UI shows "Disabled", but ALT+Escape still switches workspaces. At this point, the UI should again show no mapping for ALT+Escape, but the shortcut still tries to switch workspaces. Map "Switch to workspace on the left of the current workspace" to "ALT+Escape" and verify that it works (bringing up a little desktop viewer menu that says "Desk 1"). Map "Move between windows immediately" to "ALT+Escape". The UI warns you that you are re-assigning the shortcut. Say "Reassign". The UI shows that the shortcut moves from "Switch workspace" to "Move between". Try to use it. BUG: It still doesn't work - ALT+Escape still tries to switch workspaces. Disable it with "Backspace". BUG: The UI shows "Disabled", but ALT+Escape still switches workspaces. At this point, the UI should again show no mapping for ALT+Escape, but the shortcut still tries to switch workspaces. Map "Switch to workspace on the left of the current workspace" to "ALT+1" and verify that it works (bringing up a little desktop viewer menu that says "Desk 1"). Now try ALT+Escape (which the UI shows as not being mapped). BUG: ALT+Escape now moves between windows again, even though it doesn't show anywhere in the UI, and wasn't mapping correctly a moment ago. Disable "Switch to workspace on the left of the current workspace". BUG: ALT+1 still tries to switch workspaces. At this point, the UI should show no mapping for ALT+Escape, but the shortcut still tries to move between windows. At this point, the UI should show no mapping for ALT+1, but the shortcut still tries to switch workspaces. Map "Move between windows immediately" to "ALT+1". Try to use it. BUG: It doesn't work - ALT+1 still tries to switch workspaces. ALT+Escape, which was working, even though it shouldn't, has now stopped working and doesn't do anything. This is unusable. ProblemType: Bug Architecture: i386 Date: Sat Oct 31 14:19:41 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: gnome-control-center 1:2.28.1-0ubuntu1 ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-control-center Uname: Linux 2.6.31-14-generic i686 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- keyboard shortcuts UI issues; fails to set shortcut https://bugs.launchpad.net/bugs/467169 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 467047] Re: Keyboard Shortcuts window ignores maximize
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34794124/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/34794125/XsessionErrors.txt -- Keyboard Shortcuts window ignores maximize https://bugs.launchpad.net/bugs/467047 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 467047] [NEW] Keyboard Shortcuts window ignores maximize
Public bug reported: Binary package hint: gnome-control-center Fresh install of 9.10 karmic into VMware running on host O/S 8.10. The "Keyboard Shortcuts" window lets me use my mouse to resize it by dragging on the borders, but it ignores keyboard shortcuts to "maximize", and if I set double-clicking window titles to "maximize vertically", the window ignores that, too. I don't see why this window should be treated any differently from any other window. Let these things work. ProblemType: Bug Architecture: i386 Date: Sat Oct 31 13:05:23 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: gnome-control-center 1:2.28.1-0ubuntu1 ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-control-center Uname: Linux 2.6.31-14-generic i686 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Keyboard Shortcuts window ignores maximize https://bugs.launchpad.net/bugs/467047 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 291150] Re: When you clear a keyboard shortcut with backspace, it isn't really cleared.
I have this same problem on 9.10 karmic: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/466948 -- When you clear a keyboard shortcut with backspace, it isn't really cleared. https://bugs.launchpad.net/bugs/291150 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 466948] Re: keyboard shortcuts disable requires logout/login
I just found this related item: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/291150 -- keyboard shortcuts disable requires logout/login https://bugs.launchpad.net/bugs/466948 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 466948] Re: keyboard shortcuts disable requires logout/login
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34789785/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/34789787/XsessionErrors.txt -- keyboard shortcuts disable requires logout/login https://bugs.launchpad.net/bugs/466948 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 466948] [NEW] keyboard shortcuts disable requires logout/login
Public bug reported: Binary package hint: gnome-control-center Fresh install of 9.10 karmic into a VMware virtual machine (host O/S is 8.10). All updates applied (October 31, 2009). Nowhere do I read that you have to logout/login for keyboard shortcut disables to take effect. If disables are supposed to work without a logout/login, then this is a bug in the software. If you are supposed to logout/login for a shortcut disable to be effective, then this is a bug in the documentation and the "Keyboard Shortcuts" window should say "logout/login for changes to take effect". Pick any keyboard shortcut and disable it, e.g. "Minimize window / ALT-F9". The UI says "disabled" but the shortcut still works, until logout/login. There are more problems with re-assigning keyboard shortcuts; I'll document them in a separate report. ProblemType: Bug Architecture: i386 Date: Sat Oct 31 11:37:27 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: gnome-control-center 1:2.28.1-0ubuntu1 ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-control-center Uname: Linux 2.6.31-14-generic i686 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- keyboard shortcuts disable requires logout/login https://bugs.launchpad.net/bugs/466948 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 335942] Re: nautilus crashed with SIGSEGV in start_thread()
Yes, the multiple-nautilus-failure loop is now fixed for VMware now. Jaunty Beta with: brasero 2.26.0-0ubuntu2 Thank you for the fix. -- nautilus crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/335942 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 335942] Re: nautilus crashed with SIGSEGV in start_thread()
This is still a problem in 9.04 Jaunty Beta. This failure of Nautilus to start makes it difficult to configure 9.04 to run well in a VMware virtual machine, since the VMware Tools CDROM ISO image can't be attached without causing a Nautilus crash loop that fills the task bar. You have to SIGSTOP Nautilus, mount the CDROM ISO file manually, install VMware tools, unmount the ISO, then SIGCONT Nautilus. See https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/344371 -- nautilus crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/335942 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 344371] Re: nautilus crashed with SIGSEGV in start_thread()
See also: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/337910 -- nautilus crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/344371 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 344371] Re: nautilus crashed with SIGSEGV in start_thread()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/24010811/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/24010812/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/24010813/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/24010814/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/24010815/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/24010816/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/24010817/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/24010818/ThreadStacktrace.txt ** Visibility changed to: Public -- nautilus crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/344371 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 338180] Re: clock applet help contains broken Gnome bug report link
This is a documentation content error, not a program execution error. Do you really want a program strace? The ghelp:gnome-feedback link is also broken in 8.10. -- clock applet help contains broken Gnome bug report link https://bugs.launchpad.net/bugs/338180 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 338193] Re: clock manual preferences do not match clock applet
Sure would be nice if the "Report a problem" function on the yelp Help menu made the distinction between "report a problem with yelp" and "report a problem with the documentation yelp is showing". Of course, for the Clock Manual there is a link to "About this Document" that has a Feedback button that says "to report a bug regarding the Clock Manual", but that's the very button whose link is broken: ghelp:gnome-feedback (It's also broken in Ubuntu 8.10 as well as 9.04.) How do you report a problem with the mechanism that reports problems? I note that the Feedback button is buried under several screens worth of Legal Notice. You have to really want to post a documentation bug to go looking for that button, which might explain why this has been broken for so long. -- clock manual preferences do not match clock applet https://bugs.launchpad.net/bugs/338193 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 337910] Re: nautilus repeated SIGABRT in VMware on live CD and DVD
> this looks like bug 325973 It resembles it, but in my case nautilus is actually dying over and over with a SIGABRT, where the above bug doesn't show that symptom. Backtrace attached, such as it is. It's tricky to get a backtrace of a system program that faults every two seconds and dies. I had to "killall -STOP nautilus", set up the gdb session, and then kill -CONT nautilus and attach gdb quickly to the pid. I hope the result is useful. ** Attachment added: "gdb backtrace of nautilus and SIGABRT" http://launchpadlibrarian.net/23528542/igdb2.txt -- nautilus repeated SIGABRT in VMware on live CD and DVD https://bugs.launchpad.net/bugs/337910 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 338193] Re: clock manual preferences do not match clock applet
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/23510769/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/23510770/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/23510771/ProcStatus.txt -- clock manual preferences do not match clock applet https://bugs.launchpad.net/bugs/338193 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 338193] [NEW] clock manual preferences do not match clock applet
Public bug reported: Binary package hint: yelp In the Clock Manual, the Preferences page lists preferences that are not available in the actual clock applet, e.g. the clock applet doesn't offer Unix Time or Internet Time or Use UTC, etc. Clock 2.25.92 The manual needs to be edited to match the actual clock applet. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/yelp Package: yelp 2.25.1-0ubuntu2 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: yelp Uname: Linux 2.6.28-8-generic i686 ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- clock manual preferences do not match clock applet https://bugs.launchpad.net/bugs/338193 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 338192] [NEW] yelp run from command line cannot report a problem
Public bug reported: Binary package hint: yelp Ubuntu 9.04 jaunty Alpha 5 with several hundred package updates applied. I had asked for help from the Clock applet, and I noticed the help didn't match the applet, so I chose "Report a Problem", which started up a browser report for something called "yelp". I double-checked the About menu and was told that the application was "Help 2.25.1", not "yelp". I did a process listing, and didn't see anything named "yelp" running, only "gnome-help". So I read the "yelp" man page and then started "yelp" from the command line, and it started the Gnome help application (a second copy). Is the program "gnome-help" called "yelp" in the packaging and documentation? That's confusing. I did a process listing, and I could see the yelp I had run from the command line: 4 0 5840 4796 20 0 121652 50904 poll Sl pts/0 0:03 yelp I did some searches in the new Gnome help window, then went back to the previous Clock help window, and at some point the yelp I had run crashed: I/O error : Is a directory I/O error : Is a directory [1]+ Segmentation fault (core dumped) yelp The top menu bar showed a "!" icon telling me to click on it to report a crash. I tried to do that; the report a crash application apparently itself crashed and I couldn't submit anything that way. So I started yelp from terminal again, e.g. just typed "yelp" at the bash prompt. When yelp opened, I tried "Report a Problem". and I got this mess: r...@idallen-jaunty5:~# yelp & [1] 6380 I/O error : Is a directory I/O error : Is a directory Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 264, in app.run_argv() File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 325, in run_argv return self.run_report_bug() File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 298, in run_report_bug self.collect_info() File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 425, in collect_info icthread.exc_raise() File "/usr/lib/python2.6/dist-packages/apport/REThread.py", line 37, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 66, in thread_collect_info report.anonymize() File "/usr/lib/python2.6/dist-packages/apport/report.py", line 932, in anonymize replacements[os.uname()[1]] = 'hostname' UnboundLocalError: local variable 'replacements' referenced before assignment Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/apport_python_hook.py", line 85, in apport_excepthook os.O_WRONLY|os.O_CREAT|os.O_EXCL), 'w') OSError: [Errno 17] File exists: '/var/crash/_usr_share_apport_apport-gtk.0.crash' Original exception was: Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 264, in app.run_argv() File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 325, in run_argv return self.run_report_bug() File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 298, in run_report_bug self.collect_info() File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 425, in collect_info icthread.exc_raise() File "/usr/lib/python2.6/dist-packages/apport/REThread.py", line 37, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.6/dist-packages/apport/ui.py", line 66, in thread_collect_info report.anonymize() File "/usr/lib/python2.6/dist-packages/apport/report.py", line 932, in anonymize replacements[os.uname()[1]] = 'hostname' UnboundLocalError: local variable 'replacements' referenced before assignment yelp: Installed: 2.25.1-0ubuntu2 Candidate: 2.25.1-0ubuntu2 Version table: *** 2.25.1-0ubuntu2 0 500 http://ca.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/yelp Package: yelp 2.25.1-0ubuntu2 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: yelp Uname: Linux 2.6.28-8-generic i686 ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- yelp run from command line cannot report a problem https://bugs.launchpad.net/bugs/338192 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 338192] Re: yelp run from command line cannot report a problem
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/23510677/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/23510678/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/23510679/ProcStatus.txt -- yelp run from command line cannot report a problem https://bugs.launchpad.net/bugs/338192 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 338180] Re: clock applet help contains broken Gnome bug report link
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/23509789/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/23509790/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/23509791/ProcStatus.txt -- clock applet help contains broken Gnome bug report link https://bugs.launchpad.net/bugs/338180 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 338180] [NEW] clock applet help contains broken Gnome bug report link
Public bug reported: Binary package hint: yelp In the "Clock Manual", under "About this document", is this broken link for bug reporting: ghelp:gnome-feedback Selecting the text gives "document not found". Revision History February 2004: Clock Applet Manual V2.5 (Sun Microsystems) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/yelp Package: yelp 2.25.1-0ubuntu2 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: yelp Uname: Linux 2.6.28-8-generic i686 ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- clock applet help contains broken Gnome bug report link https://bugs.launchpad.net/bugs/338180 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 337910] Re: nautilus repeated SIGABRT in VMware on live CD and DVD
Goodness, it's a pain to do all the configuration and download all the software needed to get a backtrace, isn't it? I'll try to find time to do all that later. Couldn't you build a little script that would do all the work, e.g. "ubuntu-backtrace nautilus" would do all those config steps, download the symbols, etc.? Please make bug reporting and tracing as painless as possible! I have more information on the nautilus problem: I reran my virtual machine. I chose the "Install" menu item from the CD (which is a virtual CD - the virtual CDROM is attached to the Jaunty ISO file on my host system) and everything installed fine onto the virtual disk, and at reboot and login my desktop came up without any looping/dying nautilus problem. Then I noticed that the CDROM was listed as "disconnected" - I didn't have the Ubuntu CDROM icon visible on the desktop and there was a red "X" over the CDROM in the VMware Workstation status line. So I used Workstation to enable the CDROM. Boom - nautilus started looping. I disconnected the virtual CDROM. The looping/dying stopped. I reconnected the virtual CDROM. The looping/dying started. I configured a second virtual CDROM and attached it to the ISO file, and enabled it. The looping/dying started again. I disconnected it. I attached the virtual CDROM to my real, physical CDROM, stuck in an old Ubuntu install CD, and enabled it. The CD spun up and the Ubuntu icon appeared on my desktop. No looping. So, the nautilus looping/dying problem only happens when the virtual CDROM is connected to an ISO image in the host file system. -- nautilus repeated SIGABRT in VMware on live CD and DVD https://bugs.launchpad.net/bugs/337910 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 337910] Re: nautilus repeated SIGABRT in VMware on live CD and DVD
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/23439800/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/23439801/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/23439803/ProcStatus.txt -- nautilus repeated SIGABRT in VMware on live CD and DVD https://bugs.launchpad.net/bugs/337910 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 337910] [NEW] nautilus repeated SIGABRT in VMware on live CD and DVD
Public bug reported:
Binary package hint: nautilus
I used VMware Workstation to create a 1GB/8GB virtual machine, attached
the latest (Feb 28) Jaunty DVD to the CDROM port, and booted it as
"try without installing". Both the CD and DVD versions came up with a
desktop background and a task bar showing nautilus processes starting
and dying - the task bar was filling with nautilus entries and nothing
ever appeared on the desktop.
I started a terminal and did "killall -STOP nautilus" to stop the looping
nautilus and then straced the stopped nautilus process (which resumed
as soon as the strace attached to it). Nautilus quickly died with
a SIGABRT and another nautilus started, which died, etc. I repeated
this STOP/strace sequence twice. Each nautilus died with this system
call pattern:
[...]
read(20, "l\2\1\1\4\0\0\0\360\364\0\0-\0\0\0\6\1s\0\7\0\0\0:1.1687\0\5"...,
2048) = 68
read(20, 0x8cc2968, 2048) = -1 EAGAIN (Resource temporarily
unavailable)
gettimeofday({1236189516, 845172}, NULL) = 0
writev(20, [{"l\1\0\1\20\0\0\0*\0\0\0\277\0\0\0\1\1o\0E\0\0\0/org/free"...,
208}, {"\v\0\0\0scsi.target\0"..., 16}], 2) = 224
gettimeofday({1236189516, 848212}, NULL) = 0
poll([{fd=20, events=POLLIN}], 1, 25000) = 1 ([{fd=20, revents=POLLIN}])
read(20, "l\2\1\1\4\0\0\0\361\364\0\0-\0\0\0\6\1s\0\7\0\0\0:1.1687\0\5"...,
2048) = 68
read(20, 0x8cc2968, 2048) = -1 EAGAIN (Resource temporarily
unavailable)
gettimeofday({1236189516, 848757}, NULL) = 0
writev(20, [{"l\1\0\1&\0\0\0+\0\0\0\267\0\0\0\1\1o\0;\0\0\0/org/free"..., 200},
{"!\0\0\0storage.removable.media_avail"..., 38}], 2) = 238
gettimeofday({1236189516, 849645}, NULL) = 0
poll([{fd=20, events=POLLIN}], 1, 25000) = 1 ([{fd=20, revents=POLLIN}])
read(20, "l\2\1\1\4\0\0\0\362\364\0\0-\0\0\0\6\1s\0\7\0\0\0:1.1687\0\5"...,
2048) = 68
read(20, 0x8cc2968, 2048) = -1 EAGAIN (Resource temporarily
unavailable)
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK,
-1, 0) = 0xb5be9000
mprotect(0xb5be9000, 4096, PROT_NONE) = 0
clone(child_stack=0xb63e9424,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xb63e9bd8, {entry_number:6, base_addr:0xb63e9b90,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}, child_tidptr=0xb63e9bd8) = 16428
futex(0xb795e790, FUTEX_WAKE_PRIVATE, 1) = 1
+++ killed by SIGABRT (core dumped) +++
Both the CD and the DVD do this. The previous Jaunty (Feb 5) worked
fine under VMware.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.25.91-0ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux 2.6.28-8-generic i686
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
nautilus repeated SIGABRT in VMware on live CD and DVD
https://bugs.launchpad.net/bugs/337910
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
