[Bug 1196362] [NEW] Brightness resets to full on resume
Public bug reported: On my Dell Inspiron N5010, running Ubuntu 13.04, the screen brightness is reset to full every time I resume from sleep. I don't know if this is related, but it is also reset to full brightness when I run gnome- control-center screen. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24.1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 30 22:12:27 2013 InstallationDate: Installed on 2013-04-27 (64 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1196362 Title: Brightness resets to full on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1196362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951123] Re: nautilus not natural scrolling
Here's some information that I wasn't able to find in this discussion, so I thought I'd post it. Natural scrolling can be achieved by putting the following in ~/. : pointer = 1 2 3 5 4 7 6 8 9 10 11 12. In man xmodmap, there is a description of the program does. The codes can be found by running xev. This is a regression as every application in 11.10 seemed to work as expected when .Xmodmap was changed. However, certain programs don't seem to respect .Xmodmap in 12.04. -- 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/951123 Title: nautilus not natural scrolling To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/951123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 50198] Re: Timeout has expired error on resume from hibernate
I'm running a Dell Inspiron N5010. I encountered this problem consistently with Ubuntu 10.04 (a few times a day) and have not encountered it in Ubuntu 11.10 yet. I have been running 11.10 for more than a week without problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/50198 Title: Timeout has expired error on resume from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/50198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 50198] Re: Timeout has expired error on resume from hibernate
I'm no longer affected in Ubuntu 11.10 regular Unity (not Unity 2D). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/50198 Title: Timeout has expired error on resume from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/50198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 50198] Re: Timeout has expired error on resume from hibernate
I can see it on a Dell Inspiron N5010 using Lucid (10.04). The laptop resumes on opening the lid and then the dialog momentarily appears, the Time has expired message shows for a few seconds and then the dialog disappears. I can start entering characters once the unlock dialog reappears. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/50198 Title: Timeout has expired error on resume from hibernate -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 508452] Re: wnck-applet crashed with SIGSEGV in g_closure_invoke()
Same as Nguyen here. Except gnome-panel doesn't seem to work properly at all. I don't see any panel to start off with (I deleted the .gconf* .gnome2* directories from tty1 before logging in and it worked then. A restart after that, I don't see any panels again. Don't know whether this is related in anyway. (BTW: I had some errors with the panel/applets (don't remember) when running the LiveCD also. Let me know if any further information is required. -- wnck-applet crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/508452 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 535088] Re: Metacity bug when using background for buttons
What's the status of the patch? Is it being reviewed? Does the status of this bug need to change to something like In Progress? -- Metacity bug when using background for buttons https://bugs.launchpad.net/bugs/535088 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 533884] [NEW] Theme thumbnails often bad in Appearance Preferences
Public bug reported: Binary package hint: metacity Hi, I've noticed very often for manually installed themes, the thumbnail doesn't really work properly. I downloaded the source for the Ambiance theme and installed it. The theme works, but the thumbnail is bad. I've never noticed this for themes that are not manually installed (drag and drop tarball). Metacity: 1:2.28.0-0ubuntu2 Using Ubuntu karmic (9.10) Got theme from `light-themes` source package in Lucid. ** Affects: metacity (Ubuntu) Importance: Undecided Status: New -- Theme thumbnails often bad in Appearance Preferences https://bugs.launchpad.net/bugs/533884 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 533884] Re: Theme thumbnails often bad in Appearance Preferences
** Attachment added: Screenshot http://launchpadlibrarian.net/40428104/Screenshot-Appearance%20Preferences.png ** Description changed: Binary package hint: metacity Hi, I've noticed very often for manually installed themes, the thumbnail doesn't really work properly. I downloaded the source for the Ambiance theme and installed it. The theme works, but the thumbnail is bad. I've never noticed this for themes that are not manually installed (drag and drop tarball). + + Metacity: 1:2.28.0-0ubuntu2 + Using Ubuntu karmic (9.10) + Got theme from `light-themes` source package in Lucid. -- Theme thumbnails often bad in Appearance Preferences https://bugs.launchpad.net/bugs/533884 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 488009] Re: F-Spot crashes when opened
Just tried it a few minutes back. Still crashes for me. -- F-Spot crashes when opened https://bugs.launchpad.net/bugs/488009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 500810] Re: Ubuntu sometimes logs me out before login process is completed
This bug still affects me. -- Ubuntu sometimes logs me out before login process is completed https://bugs.launchpad.net/bugs/500810 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 500810] Re: Ubuntu sometimes logs me out before login process is completed
** Description changed: On Ubuntu 9.10 Karmic. Sometimes, when I try to login, the login box disappears and the usplash (I think) starts as usual (with the scrolling bar). Within two or three seconds, the screen goes black, I get some errors, then the login screen again. I often have to make two or three attempts to finally get a successful login. - Conditions: The default screen resolution is 1152 x 864; 75Hz. Because - of a very awkward and rare problem, my CRT monitor sometimes starts - squeaking a very high pitch. I discovered that by changing the refresh - rate (to anything else), the squeaking stops. (e.g my screen starts - squeaking when the refresh rate is 75Hz, I change it to 60Hz and it - stops, or vice-versa). So if I change the refresh rate to 60Hz (when the - screen squeaks at 75Hz), my refresh rate and the login screen refresh - rate is different. If this is the case (my refresh rate[60Hz] not equal - to login screen refresh rate[75Hz]) then I am often unable to login. The + Conditions: The default screen resolution is 1152 x 864; 75Hz. If I + change the refresh rate to 60Hz then I am often unable to login. The screen flashes black (like it is supposed to when changing the resolution), and then a black error screen is seen. After this usplash continues, except not to log me in, but to go to gdm). This is a fresh install of Ubuntu 9.10 Karmic Koala. I do not know whether I have a graphics card (I seriously doubt it, because I am unable to use Desktop Effects). I am willing to submit any other data that is required. Reproducible: Not always. Since I am able to login after a couple of - attempts. Even when the screen resolutions are not equal, I rarely am - able to login in my first attempt. + attempts. Even when the screen resolutions (of my account to gdm) are + not equal, I rarely am able to login in my first attempt. Other info: - - I have not been able to note the error messages down as yet. + - I have not been able to note the error messages down as yet. - Yes, I am sure I typed in my password correctly. If I don't, I am not allowed to get to the point where usplash starts scrolling a bar on the screen. - This happens after around the bar completes one full scroll, sometimes two. FYI, for the whole login process, Ubuntu consistently takes 14 or 15 scrolls or scrolling cycles (whatever you call it). - I have never tried it with a different screen resolution (e.g 1024*768) - - I consider this a serious bug. -- Ubuntu sometimes logs me out before login process is completed https://bugs.launchpad.net/bugs/500810 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 500810] Re: Ubuntu sometimes logs me out before login process is completed
Well, I'm surprised nobody suggested that the error message might be in tty1. Anyway, I managed to see that the error screen I got had tty1 written somewhere on it. So Ctrl+Alt+F1. Here's what it said (my computer name is home-ubuntu and this message may not be exact since I copied it on a piece of paper) home-ubuntu login [ 123.468049] [drm: i810_wait_ring] *ERROR* space: 65520 wanted 65528 [ 123.468124][drm: i810_wait_ring] *ERROR* lockup I hope this helps in debugging... Do let me know if I need to extract some other data also. -- Ubuntu sometimes logs me out before login process is completed https://bugs.launchpad.net/bugs/500810 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 54024] Re: WIN key SUPER_L should be mapped to Applications menu
Earlier, when I wanted to change my shortcuts and started by pressing Super_L (and was going to press E for open home folder), it said Super_L and didn't allow a Super_L + ... I had to change some settings (make Super a meta key I think) to get it to work. I recently did a fresh install of Karmic (without using my old /home also) and it now allows me to do Super_L + E without any other configuration. So I presume half the problem here has been fixed. -- WIN key SUPER_L should be mapped to Applications menu https://bugs.launchpad.net/bugs/54024 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 488009] Re: F-Spot crashes when opened
*** This bug is a duplicate of bug 437402 *** https://bugs.launchpad.net/bugs/437402 ** Attachment added: Output of ~$ f-spot http://launchpadlibrarian.net/36049820/f-spot%20terminal%20output ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/36049821/Dependencies.txt -- F-Spot crashes when opened https://bugs.launchpad.net/bugs/488009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488009] [NEW] F-Spot crashes when opened
*** This bug is a duplicate of bug 437402 *** https://bugs.launchpad.net/bugs/437402 Public bug reported: Binary package hint: f-spot Hi, I have a fresh install of Ubuntu Karmic. When I open f-spot from the menu or the terminal, I get the F-Spot window which stays for a few seconds and then crashes. When I open it from the terminal, I get quite a long output, which I have attached here also. ProblemType: Bug Architecture: i386 Date: Wed Nov 25 11:13:46 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: f-spot 0.6.1.4-0ubuntu1 ProcEnviron: LANGUAGE=en_GB.UTF-8 LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: f-spot Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:1574): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:1652): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (f-spot:1876): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. (f-spot:1918): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference. ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- F-Spot crashes when opened https://bugs.launchpad.net/bugs/488009 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 437402] Re: F-Spot crashes
My bug ( lp:488009 ) has been marked a duplicate of this one. Although I'm not sure if it's the same bug (I get different output in the terminal, as far as I can see) I've submitted the Apport report also, if that helps. I have a feeling it has got to do with the theme I am using. I am using New Wave. I've always had problems with this theme. GNOME-Do used to crash and automatically log me out when I used this theme earlier. -- F-Spot crashes https://bugs.launchpad.net/bugs/437402 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 437402] Re: F-Spot crashes
Alright, using the new Human in Karmic I can use F-Spot perfectly. No problem. Does the New Wave theme work differently from the rest? Maybe, if it has problems, it should not be included for Lucid, which is a LTS? -- F-Spot crashes https://bugs.launchpad.net/bugs/437402 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388508] Re: Ctrl+Tab to change tab in Nautilus
Why will it not be fixed? -- Ctrl+Tab to change tab in Nautilus https://bugs.launchpad.net/bugs/388508 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
Hi, I'm a little confused over this issue. Firstly, we never managed to find where the bug was, nor do we know whether it was fixed by someone in the first place. Shouldn't we do a little more intensive testing to see if this is still an issue? If we had actually found the faulty code and fixed it, we could be sure it has been fixed. Now that just two people have confirmed that they haven't encountered it, do we presume it has been fixed? Has anyone actively tried to print without (quote) bombing it with X events for us to be sure that this is no longer an issue? I have very little experience in software development and have zero knowledge of how Ubuntu handles such issues. So if at all I am absolutely wrong in what I am saying, don't consider what I'm am saying rude. Consider it an attempt to understand how issues are handled. (Thanks) Umang -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 467972] [NEW] metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL)
Public bug reported: Binary package hint: metacity I don't know what happened. It just crashed. I was using Chrome when it happened and I just upgraded to Karmic today. ProblemType: Crash Architecture: i386 AssertionMessage: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) Date: Sun Nov 1 11:45:57 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/metacity Package: metacity 1:2.28.0-0ubuntu1 ProcCmdline: metacity ProcEnviron: LANGUAGE=en_US.UTF-8 LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /lib/libglib-2.0.so.0 g_assertion_message_expr () from /lib/libglib-2.0.so.0 Title: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) Uname: Linux 2.6.31-14-generic i686 UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video XsessionErrors: (gnome-settings-daemon:3172): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:3192): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:3195): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-panel:3206): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window (chrome:3337): Gdk-WARNING **: XID collision, trouble ahead ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 -- metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) https://bugs.launchpad.net/bugs/467972 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 467972] Re: metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL)
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34839192/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/34839193/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/34839194/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/34839195/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/34839196/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/34839197/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/34839198/ThreadStacktrace.txt -- metacity assert failure: metacity:ERROR:core/bell.c:211:bell_flash_window_frame: assertion failed: (window-frame != NULL) https://bugs.launchpad.net/bugs/467972 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 387573] Re: Drop-down calendar does not close unless you click on it
Completely agree with Stephen. It has to have at least a X button that can be clicked to close it. I have had to close the calender for others at least a few times times already (in one year that is a lot). -- 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 387573] Re: Drop-down calendar does not close unless you click on it
The second option I believe is the ideal solution. (https://bugs.launchpad.net/hundredpapercuts/+bug/387573/comments/21) But it doesn't look like everyone here found it a great idea, which is disappointing. -- 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 28835] Re: Unmount in volume right-click menu, is tech-speak and undiscoverable
I was wondering what among the following should be done for notifications for Device unsafely removed. Please disconnect/unmount device before detaching/unplugging/removing * a new bug * mention in https://bugs.launchpad.net/hundredpapercuts/+bug/386057 (which is invalid in launchpad, as it is upstream: http://bugzilla.gnome.org/show_bug.cgi?id=587340) * or will it be fixed with this bug. Thanks Umang ** Bug watch added: GNOME Bug Tracker #587340 http://bugzilla.gnome.org/show_bug.cgi?id=587340 -- Unmount in volume right-click menu, is tech-speak and undiscoverable https://bugs.launchpad.net/bugs/28835 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 28835] Re: Unmount in volume right-click menu, is tech-speak and undiscoverable
OK. I have a few suggestions that I think could work both ways: educating the users as well as using simple words without copying Windows. I think we should rename Unmount as disconnect. This is better than eject, because: 1.) Eject has a physical meaning and if the CD gets Ejected when we click Eject then Eject is potentially very confusing for a USB stick. 2.) Eject has no opposite. We cannot say Eject as once an FS is unmounted give a Mount or Uneject (which is funny) option for users. Connect can be an option for a disconnected (i.e. mounted) removable drive (or even hard drive). I think Connect is a word that is good enough to be copied by others too! Then, reduce how much a user will get confused about notifications, etc by introducing one more simple word: unplug. When a drive is disconnected we can give a notification saying It is now safe to unplug this device. If you wish to continue using it, please connect to the drive. This is not necessary, though, Remove may be used if people find that simpler. Of course, we will also have to educate the users by giving notifications about device unsafely removed even if there was no data transfer happening at the time the device was removed. This will remind/teach people to Disconnect (i.e. unmount) a device before removing, whether the device was removed safely or unsafely. Finally, this will only be effective if notifications are used effectively: 1.) Warning notifications have to be given when mounted device is pulled out (removed/unplugged) 2.) Confirm notifications have to be given when a device is unmounted, even if there was no data transfer. (https://bugs.launchpad.net/bugs/386057) Umang -- Unmount in volume right-click menu, is tech-speak and undiscoverable https://bugs.launchpad.net/bugs/28835 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 387573] Re: Drop-down calendar does not close unless you click on it
I agree with cenoura. This is the simplest, easiest and most intuitive solution that helps all. The pin should be a simple toggle button. I don't see a simpler solution. I think the status should be made Confirmed and changed as described above (Comment #21): https://bugs.launchpad.net/hundredpapercuts/+bug/387573/comments/21 -- 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 388508] Re: Ctrl+Tab to change tab in Nautilus
If we're going to go so far as to have Ctrl+Tab and Ctrl+Shift+Tab, Firefox users may also enjoy Ctrl+Page Up and Ctrl+Page Down. I use the later instead of the former because of its intuitiveness and ease of use. Hopefully this will be implemented in Nautilus as well. Thanks, Umang -- Ctrl+Tab to change tab in Nautilus https://bugs.launchpad.net/bugs/388508 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 388286] [NEW] Button-based location bar does not update after folder deleted
Public bug reported: Binary package hint: nautilus Hi! When the location bar has buttons for a folder that has been deleted, the buttons remain there, until a different folder is opened. They also remain there even after I get Please check the spelling and try again. error. To try: Open Home Folder, Make new directory Test Open directory Test Press 'Up' Delete Test directory Click Test button on location bar Expected behaviour: Ideally: Test should be removed from the bar as soon as it is deleted Compromise: Test should be removed after error given when Test clicked on the bar Actual behaviour: Test remains on the location bar and Please check the spelling and try again. error is given every time Test is clicked. Also, even though Test has not been opened, the Test button is pressed along with the button of the current directory, even if the current directory is two levels bellow (e.g. home and Test are both pressed down if Test is clicked after going up to home (i.e. /home/) Nautilus: 1:2.24.1-0ubuntu2 Ubuntu : 8.10 (Intrepid) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Button-based location bar does not update after folder deleted https://bugs.launchpad.net/bugs/388286 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 388293] [NEW] evince crashed on double-click (to select word)
Public bug reported: Binary package hint: evince Hi, When I am reading a PDF, and I double-click the words to select them (habitually). When I do this many times, sometimes evince crashes. This happens only a few times a month (sometimes never). I have not been able to open from terminal and see if there is any error. I cannot reproduce this bug at the moment. Though it happens very very rarely, it is very irritating. (I don't remember whether all the other evince windows closed or not, I think they did) What should I do and how do I go about giving more information on this bug? Evince : 2.24.1-0ubuntu1 Ubuntu : 8.10 (Intrepid) I found duplicate issues reported in 2005/06, but those are most probably different as fixes seem to be released for them. Umang ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- evince crashed on double-click (to select word) https://bugs.launchpad.net/bugs/388293 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- 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
Do other applets like Volume Control, Drawers, etc require a new bug, or can this bug be modified to include all drop-down applets? -- 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 387550] Re: toolbar volume control: sideways?
** Also affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- toolbar volume control: sideways? https://bugs.launchpad.net/bugs/387550 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 387573] Re: Drop-down calendar does not close unless you click on it
In that case, I better not report any bugs in this project till I upgrade to Jaunty. :P -- 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 387957] Re: Improve Save As Dialog Box (focus issues)
** Tags removed: nautilus ** Description changed: - Binary package hint: nautilus - The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File - Save As (to bring up the Save dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File - Save As (to bring up the Save dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the file type dropdown), not back to the top of the screen. -- Improve Save As Dialog Box (focus issues) https://bugs.launchpad.net/bugs/387957 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 326631] Re: Open program in the same workspace that it's initiated
http://brainstorm.ubuntu.com/idea/5448/ had a moderator say that metacity would be the right package... But I vaguely remember seeing an option that allows you to change this behavior... I was dreaming maybe? ** Package changed: ubuntu = metacity (Ubuntu) -- Open program in the same workspace that it's initiated https://bugs.launchpad.net/bugs/326631 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
Hi, I'm sorry, I actually don't know too much about the configuration, etc. Also, I figured later that this bug is for Jaunty, while I am reporting the problem from Intrepid. Sorry again, Umang -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 359975] Re: evince sometimes yield error Error printing: Too many failed attempts
Been happening to me very often recently. I somehow manage to avoid it by doing a Print Preview and printing from the preview window. But that is just irritating. There is a solution here: http://brainextender.blogspot.com/2009/01 /ubuntu-intrepid-too-many-failed.html Maybe it can be fixed along similar lines? Thanks, Umang -- evince sometimes yield error Error printing: Too many failed attempts https://bugs.launchpad.net/bugs/359975 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 292536] Re: Sticky notes prefereces dialog closes on toggling check boxes
Those following will know that this bug has been fixed upstream. http://bugzilla.gnome.org/show_bug.cgi?id=567477 Callum McKenzie said: [...] The patch has been applied to master and gnome-2-26. I guess that mean committed and not released. But, hopefully now it will be fixed in Ubuntu soon. Since Jaunty is 2.26, maybe it will come down in some upgrade soon... ? ** Changed in: gnome-applets (Ubuntu) Status: Triaged = Fix Committed -- Sticky notes prefereces dialog closes on toggling check boxes https://bugs.launchpad.net/bugs/292536 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 292536] Re: Sticky notes prefereces dialog closes on toggling check boxes
They haven't fixed it upstream. Does bumping make a difference on gnome- bugs (bugzilla)? If it does, everyone else here should post a comment on http://bugzilla.gnome.org/show_bug.cgi?id=567477. It is still UNCONFIRMED! That is a really bad situation! :( I haven't upgraded, but I really wish I don't need to wait for six months more to get it fixed. I am pretty unhappy - I use sticky notes many times a day. They are so useful. -- Sticky notes prefereces dialog closes on toggling check boxes https://bugs.launchpad.net/bugs/292536 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 45544] Re: Notifications overlap the bottom panel.
Sorry, I don't know whether this is the same issue that is being discussed here, so please do let me know. When I unmount a USB drive (Pen drive, thumb drive), I occasionally get a message saying that it is safe to remove the device. Most of the time (95%) I do not get this message no matter how long I wait after unmounting. Is this the same issue or should I report this elsewhere? (Being the lone tech-savy user of this computer, it is a little important that I fix this issue so that others don't need my help to use USB sticks) -- Notifications overlap the bottom panel. https://bugs.launchpad.net/bugs/45544 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 292536] Re: Sticky notes prefereces dialog closes on toggling check boxes
Great! Thank you! When can we expect the fix to be released? -- Sticky notes prefereces dialog closes on toggling check boxes https://bugs.launchpad.net/bugs/292536 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 281153] [NEW] Song seek overshoots if mouse button is held, instead of draging position bar
Public bug reported: Binary package hint: rhythmbox Hi! This is a minor issue, but worth pointing out, I feel. When I hold the mouse button over a part of the seek bar that doesn't have the position bar, e.g: --=--- ^position bar ^I hold the mouse button here The position bar over shoots the point at which I'm holding the mouse. It should, ideally, stop at the point where I'm holding the mouse. I'm not sure if the problem is in the Rhythmbox code itself, but I am still reporting it here. Thanks Umang ProblemType: Bug Architecture: i386 Date: Fri Oct 10 13:15:54 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.5-0ubuntu8 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_IN SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux 2.6.24-19-generic i686 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Song seek overshoots if mouse button is held, instead of draging position bar https://bugs.launchpad.net/bugs/281153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 281153] Re: Song seek overshoots if mouse button is held, instead of draging position bar
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/18390216/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/18390217/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/18390218/ProcStatus.txt -- Song seek overshoots if mouse button is held, instead of draging position bar https://bugs.launchpad.net/bugs/281153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 281153] Re: Song seek overshoots if mouse button is held, instead of draging position bar
So, should this be filed as a GTK bug? (I suspected this, that's why I said that I don't know if it's in the Rhythmbox code). If so, then where should I file it? Or will they be notified upstream. Or is this issue not intended to be fixed? Thanks! -- Song seek overshoots if mouse button is held, instead of draging position bar https://bugs.launchpad.net/bugs/281153 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 193578] Re: Scrolling Firefox interrupts Rhythmbox audio
Could this be because of too little swap (or too little RAM)? Could you post the output of top and free? I'm not a professional, but that's my guess. Similar things happen for me when I have lots of tabs open along with many applications. -- Scrolling Firefox interrupts Rhythmbox audio https://bugs.launchpad.net/bugs/193578 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
