[Bug 46172] Modem connection after configuration - Prompt to add the modem monitor to the panel.
You have been subscribed to a public bug: After configuring the modem in the Network Settings and activating the device, it was far from obvious to me as a new ubuntu user that I would have to add the modem monitor applet to the panel in order to dial out whenever necessary. If this is supposed to be intended way for users to dial-up a connection, (and given the lack of options in any of the main menu options. I imagine it is), then it should be made more obvious to the user that this is what is required by adding it to the panel for them or rather prompting them first. ** Affects: gnome-applets (Ubuntu) Importance: Medium Status: Confirmed -- Modem connection after configuration - Prompt to add the modem monitor to the panel. https://bugs.launchpad.net/bugs/46172 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 43503] Flushing data to external storage devices
You have been subscribed to a public bug: External USB Storage devices should be flushed immediately to avoid data loss. Most users would be happy to see a progress bar rather than have a chance that their data may not have been saved. After dragging files from the desktop into the folder of a USB external storage device, a move operation was executed and the files appeared to have been successfully moved. Unfortunately, the buffers had not been flushed and when the device was removed, data was lost. This issue was compacted by no obvious way of disconnecting the device from the taskbar as Windows are used to, (although I'm not suggesting that there needs to be). This may lead people to the assumption that USB storage is handled more gracefully in Ubuntu as is the case with many other things. Further information about this can be found in the following ubuntu forum: http://ubuntuforums.org/showthread.php?p=994249#post994249 ** Affects: Ubuntu Importance: Medium Assignee: Ubuntu Desktop Bugs Status: Confirmed -- Flushing data to external storage devices https://bugs.launchpad.net/bugs/43503 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 43501] Default drag operation to an external storage device.
You have been subscribed to a public bug: Particularly with a USB device, but any other form of external storage device should be the same, a drag and drop operation to the device should result in a copy and not a move by default. An existing bug with data not being flushed to usb storage devices immediately can result in loss of data if a move operation is performed. Please see the following forum reference for more details. http://ubuntuforums.org/showthread.php?p=994249#post994249 ** Affects: Ubuntu Importance: Medium Assignee: Ubuntu Desktop Bugs Status: Confirmed -- Default drag operation to an external storage device. https://bugs.launchpad.net/bugs/43501 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46169] Re: Modem monitor - inadequate status feedback
I don't have easy access to this machine any more, so further updates will not be likely. I guess this was more of a feature request than it was a bug. -- Modem monitor - inadequate status feedback https://launchpad.net/bugs/46169 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35411] Re: emblems from the sidebar are updated when clicked, should be set right at startup
This bug is not just for SMB shares, but for mounted file systems in general. I've added a similar comment upstream. -- emblems from the sidebar are updated when clicked, should be set right at startup https://launchpad.net/bugs/35411 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 11324] Re: Property contextual menu on item...
It would be good if command line parameters were editable in this properties window. -- Property contextual menu on item... https://launchpad.net/bugs/11324 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 51173] Totem crashes when the visualisation size is changed
Public bug reported: Subject: Totem crashes when the visualisation size is changed Distribution: Ubuntu 6.06 (dapper) Package: totem Severity: Normal Version: GNOME2.14.2 1.4.1 Gnome-Distributor: Ubuntu Synopsis: Totem crashes when the visualisation size is changed Bugzilla-Product: totem Bugzilla-Component: general Bugzilla-Version: 1.4.1 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Crashes when the visualisation size is changed Steps to reproduce the crash: 1. open the preferences in totem 2. change the visualisation size from normal to large 3. fill in a bug report. Expected Results: Anything but a crash How often does this happen? Additional Information: It should be noted that the visualisation effects do not work for me in totem either, and that this may be related to that. Debugging Information: Backtrace was generated from '/usr/bin/totem' (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) (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) [Thread debugging using libthread_db enabled] [New Thread -1224395072 (LWP 6227)] [New Thread -1347273808 (LWP 6237)] [New Thread -1335567440 (LWP 6236)] [New Thread -1327174736 (LWP 6235)] [New Thread -1316893776 (LWP 6234)] [New Thread -1304400976 (LWP 6233)] [New Thread -1295737936 (LWP 6232)] [New Thread -1287345232 (LWP 6231)] [New Thread -1270998096 (LWP 6230)] [New Thread -1265456208 (LWP 6228)] (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) 0xe410 in __kernel_vsyscall () #0 0xe410 in __kernel_vsyscall () #1 0xb743548b in __waitpid_nocancel () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7f028e6 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #3 #4 0xb4418d50 in ?? () #5 0xb75d4c6d in xine_config_save () from /usr/lib/libxine.so.1 #6 0x0837cb70 in ?? () #7 0x0004 in ?? () #8 0x0837cba0 in ?? () #9 0x in ?? () Thread 10 (Thread -1265456208 (LWP 6228)): #0 0xe410 in __kernel_vsyscall () No symbol table info available. #1 0xb71ee8c4 in poll () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0xb736a7e8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #3 0xb736acb8 in g_main_loop_run () from /usr/lib/libglib-2.0.s
[Bug 46169] Re: Modem monitor - inadequate status feedback
There wasn't anything that looked useful in /var/log/syslog. My parents now have the computer, and they have noticed the problem on several occasions. The workaround is to do a re-boot. Either way, some extra information in the dialog would provide some much needed feedback to the user not only that something is happening, but what is happening. -- Modem monitor - inadequate status feedback https://launchpad.net/bugs/46169 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46165] Re: Removing modem monitor applet from panel causes a crash
The percentage of CPU that may have been because I am on a relatively low-spec'd computer. I'm sure that 100% of the CPU was not being used by the applet, but there was some CPU being used which I thought was odd, and was the catalyst to me finding the bug. Thanks for confirming. -- Removing modem monitor applet from panel causes a crash https://launchpad.net/bugs/46165 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46169] Re: Modem monitor - inadequate status feedback
I installed Dapper Flight 7 and have been updating daily. I'll provide feedback on the /var/log/syslog when I get home. -- Modem monitor - inadequate status feedback https://launchpad.net/bugs/46169 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46169] Modem monitor - inadequate status feedback
Public bug reported: Binary package hint: gnome-applets Severity: low Description of situation: After going through the nightmarish experience of trying to install drivers for my hsfmodem, the time came to test it. I added the modem applet to the top panel, and after configuring the modem, activated it. The progress bar came up but thats about all I can tell you because there is no more information. As I couldn't browse the internet, I tried diagnosing the problem which may very well have included anything from an invalid password to a driver as this was an external driver from linuxant. was looking for some kind of feedback from the modem monitor. The connection to the phone line was held for some time, but the tool-tips indicated that there was no connection. Description of problem: The modem monitor needs to provide more feedback to the user about its current state. One possible place for this information is in the dialog title. Useful details could include: - Connection status - whether it has made initial connection. - Varifying credentials such as username and password. - Success on validating the username and password. - Connection speed. ** Affects: gnome-applets (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- Modem monitor - inadequate status feedback https://launchpad.net/bugs/46169 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46165] Removing modem monitor applet from panel causes a crash
Public bug reported: Binary package hint: gnome-applets Severity: medium Description of the crash: I had accidentally added several modem applets to the top panel due to a lag between when I hit add and when I received an indication that something happened. I later noticed that the CPU was running at 100%, and after noticing that the modem applets were taking up CPU, I tried to remove one. Removing each one from the panel causes a crash. Steps to reproduce: 1. Add 2 modem monitor applets to the top panel. 2. Right click on one and try to remove it. 3. Crash. ** Affects: gnome-applets (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed -- Removing modem monitor applet from panel causes a crash https://launchpad.net/bugs/46165 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
