[Bug 368005] Re: Notification popups don't last enough to be correctly read
I've found there's a Messaging Menu being developed to centralize all message sources at one point: https://wiki.ubuntu.com/MessagingMenu This would be the perfect place to put the persistent log I mentioned earlier. An application that would play "catch-all" (store all messages from notify-osd that don't belong to any of the other messaging applications) would solve my "disappearing information" problem. -- Notification popups don't last enough to be correctly read https://bugs.launchpad.net/bugs/368005 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368005] Re: Notification popups don't last enough to be correctly read
Setting a longer show time will not solve this bug for me. The time might be close to expiration when I stop working with an application and want to read the notification. It also won't solve the case for notifications that would take *minutes* to mentally process, like the one I had this week: - I received a notification saying more or less that "The sound system *A-89853xx##* is not working. Switching to sound system *B-IFX99L337* instead". - When I was still trying to read the names of the failing components in order to make sense of the sentence, the notification began fading. - I tried to keep the message from disappearing. My gut reaction was placing the mouse over the notification (the standard behavior for fading popups is to stop fading). Alas, placing the mouse on Ubuntu's notifications make them *unreadable*. - Of course, when a notification disappears, it's gone. Forever. The sad thing is, that's *intentional*. By design there isn't a place in the interface where one can go to read previous notifications. I know this was a bold design decision by the Ubuntu team, and I understand the rationale behind it. The problem is, *it's not working*. Either show only notes that we won't miss when they're gone (volume-bright up/down are fine), or provide a way to recover the alerts we do care about. There must be a way to make notifications persistent so that they can be properly read. A simple log in the system tray would make wonders. -- Notification popups don't last enough to be correctly read https://bugs.launchpad.net/bugs/368005 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95853] Re: Add an option to get a confirmation dialog before deleting files in Nautilus
@kikl: You still have to locate in the trash the deleted files after you accidentally delete them. This can be really cumbersome and time- consuming if there are hundreds of files in the trash. Penalizing the user this way for a small mistake seems a bad idea, specially if the warning before deleting files is to be removed as per this bug proposal. -- Add an option to get a confirmation dialog before deleting files in Nautilus https://bugs.launchpad.net/bugs/95853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95853] Re: Add an option to get a confirmation dialog before deleting files in Nautilus
@kikl: the trash bin is not the same as an undo. Even if it provides the same functionality, it is by far much more complex to use than a single key-press (Ctrl-z). Also last time I checked the trash bin didn't have a way to restore files to the same place they were deleted (like Windows trash bin does). Compare these two workflows: - user presses Del key by mistake. Files are moved to trash. - open the trash bin. - remember which files where selected when the mistake was made, and find them in the trash bin. - select files. - move the deleted files back to the folder (supposing the user did notice the mistake and didn't close the window) vs - user presses Del key by mistake. Files are moved to trash, and a prominent but unobtrusive message notifies the operation. - user presses Undo. The files are restored. Undo function Just Works(tm). It can be safely ignored in normal workflow, but it's just one click away when you notice you've made an error. -- Add an option to get a confirmation dialog before deleting files in Nautilus https://bugs.launchpad.net/bugs/95853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95853] Re: Add an option to get a confirmation dialog before deleting files in Nautilus
As for my opinion on the bug, I strongly favor the "Undo button" on a yellow non-modal notification. For those suggesting to copy Windows, note that in Windows' Explorer there *is* a working "undo" feature when moving files to trash. -- Add an option to get a confirmation dialog before deleting files in Nautilus https://bugs.launchpad.net/bugs/95853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95853] Re: Add an option to get a confirmation dialog before deleting files in Nautilus
For those advocating a dialog confirmation, here's a relevant article from a usability professional, explaining why confirmation dialogs don't work in general as a way to protect user data: Never use a warning when you mean Undo http://www.alistapart.com/articles/neveruseawarning I think this is the central point in the linked article: "interfaces that don’t respect habituation are very bad" -- Add an option to get a confirmation dialog before deleting files in Nautilus https://bugs.launchpad.net/bugs/95853 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51043] Re: "rightclick -> paste" missing in contextmenu when pointer is above files/folders
** Also affects: hundredpapercuts Importance: Undecided Status: New -- "rightclick -> paste" missing in contextmenu when pointer is above files/folders https://bugs.launchpad.net/bugs/51043 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 96703] Kubuntu System Settings crashes on exit
Public bug reported: Latest alpha version of Kubuntu 7.04, running from LiveCD 1) Open System Settings 2) Click Monitor & Display 3) Click Administrator mode 4) Click Hardware tab->Configure 5) Click Detect monitor (mine is a Iiyama VisionMaster Pro 410) 6) Hit OK 7) Hit Apply, Continue 8) Close the System Setting window At this point, a KDE Crash Handler window appears, reporting a signal 6 (SIGABRT) in kcmshell. My machine's Ubuntu hardware database entry : 3181d9b945bad71be9e66ab9294cfc58 This is the dump in the crash window: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233220912 (LWP 11018)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb7f50410 in __kernel_vsyscall () #7 0xb7d01df0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7d03641 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb7cfb43b in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #10 0xb682c6f4 in xcb_xlib_lock () from /usr/lib/libxcb-xlib.so.0 #11 0xb69fdc8c in ?? () from /usr/lib/libX11.so.6 #12 0x0805a9e8 in ?? () #13 0x011b in ?? () #14 0xb6ac9000 in ?? () #15 0x00804d1c in ?? () #16 0xb6aa2a4c in ?? () from /usr/lib/libX11.so.6 #17 0x0805a478 in ?? () #18 0xbfcbed6c in ?? () #19 0xb69da225 in XFreeCursor () from /usr/lib/libX11.so.6 Backtrace stopped: frame did not save the PC ** Affects: kde-systemsettings (Ubuntu) Importance: Undecided Status: Unconfirmed -- Kubuntu System Settings crashes on exit https://launchpad.net/bugs/96703 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 96703] Kubuntu System Settings crashes on exit
Public bug reported: Latest alpha version of Kubuntu 7.04, running from LiveCD 1) Open System Settings 2) Click Monitor & Display 3) Click Administrator mode 4) Click Hardware tab->Configure 5) Click Detect monitor (mine is a Iiyama VisionMaster Pro 410) 6) Hit OK 7) Hit Apply, Continue 8) Close the System Setting window At this point, a KDE Crash Handler window appears, reporting a signal 6 (SIGABRT) in kcmshell. My machine's Ubuntu hardware database entry : 3181d9b945bad71be9e66ab9294cfc58 This is the dump in the crash window: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233220912 (LWP 11018)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb7f50410 in __kernel_vsyscall () #7 0xb7d01df0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7d03641 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb7cfb43b in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #10 0xb682c6f4 in xcb_xlib_lock () from /usr/lib/libxcb-xlib.so.0 #11 0xb69fdc8c in ?? () from /usr/lib/libX11.so.6 #12 0x0805a9e8 in ?? () #13 0x011b in ?? () #14 0xb6ac9000 in ?? () #15 0x00804d1c in ?? () #16 0xb6aa2a4c in ?? () from /usr/lib/libX11.so.6 #17 0x0805a478 in ?? () #18 0xbfcbed6c in ?? () #19 0xb69da225 in XFreeCursor () from /usr/lib/libX11.so.6 Backtrace stopped: frame did not save the PC ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Kubuntu System Settings crashes on exit https://launchpad.net/bugs/96703 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
