[Bug 1248105] [NEW] Gnome-Control-Panel fails to install functional Canon MP280 driver
Public bug reported: I attempted to use Gnome-Control-Center to install a USB-attached Canon MP280 printer and it failed. I then proceeded to install the .deb packages using gdebi which were hidden inside the tar.gz package from http://support- nz.canon.co.nz/contents/NZ/EN/0100301402.html [incidentally the ./install.sh logic inside the tar.gz aiming to automate this process fails now that both rpm and deb are installed on Ubuntu - violating it's implicit assumptions]. I'm not sure if the MP280 driver was even needed, as I believe the same error was delivered by gnome-control-center before and after installing this package. The error from the console reads... (gnome-control-center:21465): printers-cc-panel-WARNING **: Installation of the new printer failed. However, I was disappointed to find that logging in to CUPS (localhost:631) and installing the printer that way worked first time. There's some kind of issue with gnome-control-center not being able to add the appropriate CUPS printer driver and it's impossible to tell what because of the terrible error reporting it provides (hiding the originating issue). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Tue Nov 5 10:12:52 2013 InstallationDate: Installed on 2013-10-29 (7 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1248105 Title: Gnome-Control-Panel fails to install functional Canon MP280 driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1248105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1248105] Re: Gnome-Control-Panel fails to install functional Canon MP280 driver
Thanks, Sebastien. I'm using Ubuntu Gnome and as far as I know, that's the only Printer control panel I have. Is it unsupported? What is in fact supported? For the debugging report, I may have launched an unusual session (by running 'gnome-control-center printers') from the command line, because I wanted a better error report than 'printer install has failed'. However the same error was reported to the console too, with no more details, hence my concern. -- 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/1248105 Title: Gnome-Control-Panel fails to install functional Canon MP280 driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1248105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1232419] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()
I didn't experience it again, so must have been transient, or fixed by later updates. Will report back if I see it again. I only saw it on Ubuntu Gnome. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1232419 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1232419/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 335712] Re: strange escape handling in Exec line of .desktop files
Yes, please provide information how to escape paths with spaces. There's no example I can find, and it seems impossible to satisfy the parser (I can't make my entry appear at all). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/335712 Title: strange escape handling in Exec line of .desktop files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/335712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1206987] [NEW] No right-click option for Bookmarks, keyboard shortcut and menu entry hard to find
Public bug reported: I struggled navigating the Nautilus interface to find a mechanism to add items to Places, before finally looking up online to find a keyboard shortcut. When navigating e.g. in /home/user the Bookmark this item entry is greyed out (and essentially invisible with the contrast settings of the default Ubuntu Gnome theme) apparently because the Home folder is already mapped to Places, so it can't be added as a bookmark. By extensively exploring documentation I learned the long way round there is a Bookmarks entry (which is invisible until the first item is added). Altogether this meant it was extremely hard to figure out how to use Nautilus to create shortcuts. Preferably, a right-click entry on a folder would offer an 'add as Bookmark' menu entry. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Wed Jul 31 16:47:23 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- 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/1206987 Title: No right-click option for Bookmarks, keyboard shortcut and menu entry hard to find To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1206987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1207079] [NEW] alacarte: no user journey for associating filetype with new binary script
Public bug reported: I have spent a very long time trying to use any kind of GUI tool to configure a file association in Ubuntu Gnome, with no success. I finally was forced to find old .desktop files from a previous desktop backup which I'd manually authored before. The requirement is simple - use a specific script in a known path to open PDFs However, there doesn't appear to be any usable mechanism for doing this, principally because Nautilus (now?) filters the possible applications to launch a specific file according to the Mime type, yet there is no way to specify the Mime type association for a new application aside from manually editing text files and forcing update of the desktop databases directly. Alacarte should ideally anticipate this. Given the simplicity of this requirement, and how commonly it's likely to be needed, this is a major oversight for the function of Alacarte. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alacarte 3.7.90-1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Wed Jul 31 20:57:53 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alacarte (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1207079 Title: alacarte: no user journey for associating filetype with new binary script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1207079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 151365] Re: Autosave doesn't work for Unsaved Documents
Maybe a comment will bring this bug back to life. This is very serious for my use of desktop linux - there's no excuse for program configurations which lose user-entered text by default. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/151365 Title: Autosave doesn't work for Unsaved Documents To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/151365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194783] [NEW] Gnome Control Centre Display configuration throws error
Public bug reported: I am able to launch and run the Gnome monitor/display control utility by launching the following in Lubuntu 13.04 sudo gnome-control-center display ...but whenever I try to actually trigger a change to the display layout, it throws the following error in a dialog... Failed to apply configuration: %s GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files I suspect this is because some dependency of gnome-control-center is implicit. Perhaps there is a service which I need to manually start before this will succeed. This is important as the behaviour of the Gnome monitor control is much richer than other xrandr wrappers like lxrandr or arandr, and in general having access to gnome controls (e.g. for mouse configuration) would be far preferable to the minimal Lubuntu ones. In particular I would like to retain control of which is the primary screen (in Compiz and LXDE) so that the panel stays on the correct monitor, regardless of the specific layout (currently with the correct layout for the physical placement of my monitors, the panel arrives on the wrong monitor and is invisible). This feature only seems to exist within the Gnome control panel. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24.1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Wed Jun 26 09:31:34 2013 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Description changed: I am able to launch and run the Gnome monitor/display control utility by launching the following in Lubuntu 13.04 sudo gnome-control-center display ...but whenever I try to actually trigger a change to the display layout, it throws the following error in a dialog... Failed to apply configuration: %s GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files I suspect this is because some dependency of gnome-control-center is implicit. Perhaps there is a service which I need to manually start before this will succeed. This is important as the behaviour of the Gnome monitor control is much richer than other xrandr wrappers like lxrandr or arandr, and in general having access to gnome controls (e.g. for mouse configuration) would be far preferable to the minimal Lubuntu ones. In particular I would like to retain control of which is the primary screen (in Compiz and LXDE) so that the panel stays on the correct monitor, regardless of the specific layout (currently with the correct layout for the physical placement of my monitors, the panel arrives on - the wrong monitor and is invisible. This feature only seems to exist + the wrong monitor and is invisible). This feature only seems to exist within the Gnome control panel. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24.1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Wed Jun 26 09:31:34 2013 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1 -- 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/1194783 Title: Gnome Control Centre Display configuration throws error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1194783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1174649] [NEW] File Roller cannot re-author APK archives
Public bug reported: I have an APK (an archive which contains an Android application) which I created using the standard Android Developer Tools. It opens fine and I can extract the contents, but I have real problems, and unusual errors, when trying to add or modify contents. Every attempt I make to add either a folder or a file to the archive causes the popup error... An error occurred while adding files to the archive. ...whilst file-roller reports to Standard Error... ** (file-roller:1801): WARNING **: Error making symbolic link: File exists This also happens if I delete the target file or folder from the archive before trying to upload a new one. I've been attempting to simply replace some of the files in the archive with more up-to-date ones, without having to rebuild the app from scratch with the dev tools (I don't have access to the source and tools right now). I only need to change one line in a html file, and replace four icons. The tool should be capable of managing this archive, and indeed I found a workaround, which is to use the .cache/ mounting of the archive to rsync a load of changes into the folder structure. In my case it was... sudo rsync --recursive ./res/drawable-* /home/cefn/.cache/.fr-LedBmX/res/ ...a path which I figured out by opening a file with a text editor or image viewer, which then reveals the auto-generated path to this archive's temporarily mounted directories via the Save As dialog. Then file-roller helpfully asks if I want to synchronize the changes on disk with the archive. I say yes, and the archive is updated. However, this workaround is not really usable for most people. N.B. at the time I was running file-roller with sudo as I wondered whether there was a permissions problem, but the same happens without sudo. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: file-roller 3.6.3-1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Tue Apr 30 08:37:16 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Description changed: I have an APK (an archive which contains an Android application) which I - created using the standard Android Developer Tools. + created using the standard Android Developer Tools. It opens fine and I + can extract the contents, but I have real problems, and unusual errors, + when trying to add or modify contents. Every attempt I make to add either a folder or a file to the archive causes the popup error... An error occurred while adding files to the archive. ...whilst file-roller reports to Standard Error... ** (file-roller:1801): WARNING **: Error making symbolic link: File exists This also happens if I delete the target file or folder from the archive before trying to upload a new one. I've been attempting to simply replace some of the files in the archive with more up-to-date ones, without having to rebuild the app from scratch with the dev tools (I don't have access to the source and tools right now). I only need to change one line in a html file, and replace four icons. The tool should be capable of managing this archive, and indeed I found a workaround, which is to use the .cache/ mounting of the archive to rsync a load of changes into the folder structure. In my case it was... - sudo rsync --recursive ./res/drawable-* /home/cefn/.cache/.fr-LedBmX/res/ + sudo rsync --recursive ./res/drawable-* /home/cefn/.cache/.fr-LedBmX/res/ ...a path which I figured out by opening a file with a text editor or image viewer, which then reveals the auto-generated path to this archive's temporarily mounted directories via the Save As dialog. Then file-roller helpfully asks if I want to synchronize the changes on disk with the archive. I say yes, and the archive is updated. However, this workaround is not really usable for most people. N.B. at the time I was running file-roller with sudo as I wondered whether there was a permissions problem, but the same happens without sudo. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: file-roller 3.6.3-1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Tue Apr 30 08:37:16 2013 MarkForUpload: True ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification
[Bug 1166949] [NEW] Gconf-editor cannot author metacity button_layout key
Public bug reported: I'm running Lubuntu 13.04 Beta 2 with Compiz. I've been launching gconf- editor as follows, trying to execute a change to move metacity buttons from the right to the left - (I'm using gtk-window-decorator). However, it suffers a hard crash immediately after gconf-editor is launched with the specified key (output below)... cefn@cefn-raring-dell:~$ gconf-editor apps/metacity/layout button_layout ** ERROR:gconf-tree-model.c:59:gconf_tree_model_get_tree_path_from_gconf_path: assertion failed: (key[0] == '/') Aborted (core dumped) ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gconf-editor 3.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Tue Apr 9 19:33:06 2013 ExecutablePath: /usr/bin/gconf-editor MarkForUpload: True ProcCmdline: gconf-editor apps/metacity/layout Signal: 6 SourcePackage: gconf-editor UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gconf-editor (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace raring ** Description changed: I've been launching gconf-editor as follows, trying to execute a change to move metacity buttons from the right to the left - (I'm using gtk- window-decorator within compiz). - However, it suffers a hard crash immediately after gconf-editor with the - specified key ... + However, it suffers a hard crash immediately after gconf-editor is + launched with the specified key ... cefn@cefn-raring-dell:~$ gconf-editor apps/metacity/layout button_layout ** ERROR:gconf-tree-model.c:59:gconf_tree_model_get_tree_path_from_gconf_path: assertion failed: (key[0] == '/') Aborted (core dumped) I'm running Lubuntu 13.04 Beta 2 ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gconf-editor 3.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Tue Apr 9 19:33:06 2013 ExecutablePath: /usr/bin/gconf-editor MarkForUpload: True ProcCmdline: gconf-editor apps/metacity/layout Signal: 6 SourcePackage: gconf-editor UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: - I've been launching gconf-editor as follows, trying to execute a change - to move metacity buttons from the right to the left - (I'm using gtk- - window-decorator within compiz). + I'm running Lubuntu 13.04 Beta 2 with Compiz. I've been launching gconf- + editor as follows, trying to execute a change to move metacity buttons + from the right to the left - (I'm using gtk-window-decorator). However, it suffers a hard crash immediately after gconf-editor is - launched with the specified key ... + launched with the specified key (output below)... cefn@cefn-raring-dell:~$ gconf-editor apps/metacity/layout button_layout ** ERROR:gconf-tree-model.c:59:gconf_tree_model_get_tree_path_from_gconf_path: assertion failed: (key[0] == '/') Aborted (core dumped) - - I'm running Lubuntu 13.04 Beta 2 ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gconf-editor 3.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Tue Apr 9 19:33:06 2013 ExecutablePath: /usr/bin/gconf-editor MarkForUpload: True ProcCmdline: gconf-editor apps/metacity/layout Signal: 6 SourcePackage: gconf-editor UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf-editor in Ubuntu. https://bugs.launchpad.net/bugs/1166949 Title: Gconf-editor cannot author metacity button_layout key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf-editor/+bug/1166949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1166090] [NEW] Metacity paths don't appear in gconf-editor
Public bug reported: I've been trying to find out how to put the window buttons to the left. All the guides I've seen refer to the use of a path in gconf-editor apps/metacity but that path to properties settings is non-existent. Does that mean that some kind of configuration hasn't happened, yet. Where are the properties set, now. I'm using this metacity configuration only in the context of using gtk- window-decorator in Compiz, though, rather than using metacity as a window manager, so it may be the bug/feature should be reported elsewhere. I'm running Lubuntu 13.04 Beta 2. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: metacity 1:2.34.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic i686 ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 Date: Mon Apr 8 10:07:33 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1166090 Title: Metacity paths don't appear in gconf-editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1166090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044974] [NEW] Rhythmbox hangs with stupid alert box when syncing iPod
Public bug reported: Having deleted all the songs from my iPod Touch 16GB I was trying to put another 10GB of songs back on. Wasn't optimistic, thanks to Apple's obfuscated protocols, and sure enough about a half hour later the whole thing had hung, with a blank alert box and a greyed out screen. The music I was playing went on for a bit, but even that has stopped now. Screenshot attached below, and no, I didn't want 50 copies of Texas Put your arms around me. Please don't take this as a sign of my musical tastes. It was a test run with my girlfriend's music and clearly a bug that it is somehow writing so many of the same track to the iPod, or maybe a visual glitch. Hopefully apport has attached relevant PID information now, so I'm going to force quit it and try again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Sep 2 13:13:29 2012 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423.2) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1044974 Title: Rhythmbox hangs with stupid alert box when syncing iPod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044974] Re: Rhythmbox hangs with stupid alert box when syncing iPod
** Attachment added: rhythmbox_hung.png https://bugs.launchpad.net/bugs/1044974/+attachment/3288893/+files/rhythmbox_hung.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1044974 Title: Rhythmbox hangs with stupid alert box when syncing iPod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044974] Re: Rhythmbox hangs with stupid alert box when syncing iPod
After force quit and restart, it's still hung, and can't even seem to load my music library. See screenshot. ** Attachment added: rhythmbox_reloaded_hung.png https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+attachment/3288900/+files/rhythmbox_reloaded_hung.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1044974 Title: Rhythmbox hangs with stupid alert box when syncing iPod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044974] Re: Rhythmbox hangs with stupid alert box when syncing iPod
Eventually, (after 5 minutes or so) the attached screenshot appears, indicating that the fact the iPod is still plugged in is triggering the same or a related latent bug. ** Attachment added: rhythmbox_reloaded_eventual.png https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+attachment/3288901/+files/rhythmbox_reloaded_eventual.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1044974 Title: Rhythmbox hangs with stupid alert box when syncing iPod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044974] Re: Rhythmbox hangs with stupid alert box when syncing iPod
Attempting to unmount, kill nautilus or force-unplug the iPod had no
effect, so I ran
ps aux | grep gvfs | awk '{print $2;}' | xargs -n1 sudo kill -9
...which killed the iPod mount and caused Rhythmbox's hanging on blank
alert box behaviour to resolve itself.
It's offered to reinitialise my iPod. It has no models in the list of
possible models, but I gave it a name and clicked on initialise anyway.
My library seems to be intact now it's actually loaded. I'll see what's
happened to the iPod eventually.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1044974
Title:
Rhythmbox hangs with stupid alert box when syncing iPod
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044974] Re: Rhythmbox hangs with stupid alert box when syncing iPod
When it offered to initialise my iPod the device was no longer connected, as it turns out. The iPod has songs on it, and can be browsed through Rhythmbox as long as I don't try to copy files onto it. Checking the filesystem with Baobab shows that it indeed has about 3.6 Gig of songs, and is not full, (i.e. plenty of space before the 16GB limit) cefn@cefn-precise-dell:~/.gvfs/Cefn’s iPod$ df . Filesystem 1K-blocksUsed Available Use% Mounted on gvfs-fuse-daemon 15347304 3593272 11754032 24% /home/cefn/.gvfs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1044974 Title: Rhythmbox hangs with stupid alert box when syncing iPod To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1044974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 907311] Re: Not exiting properly? An instance of Brasero is already running, exiting
This is very serious, as for most users it would mean CD burning is entirely impossible. It seems to be associated with either... * having run Brasero to burn a CD with the windowed client within the same session * allowing automount behaviour to trigger Brasero with the Nautilus-embedded client I suspect it's to do with the automount behaviour, which is presumably an 'instance' of Brasero which someone thinks is more easy to use than the client itself (by dragging and dropping files). This doesn't cut it for burning ISOs though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/907311 Title: Not exiting properly? An instance of Brasero is already running, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/907311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 920691] Re: Nautilus has no Bookmark target until CTRL+D
** This bug is no longer a duplicate of bug 874386 Can't drag/drop files onto bookmarked folders -- 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/920691 Title: Nautilus has no Bookmark target until CTRL+D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/920691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 920691] Re: Nautilus has no Bookmark target until CTRL+D
*** This bug is a duplicate of bug 874386 *** https://bugs.launchpad.net/bugs/874386 It's not a duplicate of the other bug it was linked to, so I have removed that link. This is a feature regression, is confusing and inconsistent, (perhaps this doesn't qualify it as a bug). The other 'bug' relates to not being able to use bookmarks for moving files/folders around the filesystem by dragging them onto Nautilus bookmarks (which was is a deliberate choice by Gnome). My 'bug' is that it's impossible to even ADD a bookmark by dragging, which is the feature Gnome chose to preserve in this discussion! It only applies to the FIRST bookmark. Once you have added one folder, then drag-to-link becomes possible under the Bookmarks heading. Even accepting the Gnomic logic about the ambiguity of drag-to-link versus drag-to-move, they chose to favour drag-to-link. Making it impossible to drag-to-link the FIRST bookmark isn't consistent with their logic. It's to do with the build of Ubuntu which makes Home, Desktop, Documents, Downloads not 'Bookmarks', but something different under 'Computer' - a collection of shortcuts which prevent drag-to-link, and facilitate drag-to-move. As it turns out, you can't create new items under the Computer heading at all, I think. Quite a mess. -- 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/920691 Title: Nautilus has no Bookmark target until CTRL+D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/920691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 920691] Re: Nautilus has no Bookmark target until CTRL+D
Sebastien has added back the duplicate flag I removed, even though this is incorrect. Indeed this is the direct opposite of the other bug, if you take into account the feature discussion at Gnome, which split bookmark drag functionality into two. The one they decided to preserve is broken by the bug I'm reporting, at least for the first bookmark. I'll leave it to the team to decide how to manage their bugs. If they want to flag a different bug as the same thing that's their business. I would say it's harder to manage code this way, though. -- 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/920691 Title: Nautilus has no Bookmark target until CTRL+D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/920691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 920691] [NEW] Nautilus has no Bookmark target until CTRL+D
Public bug reported: Running a stock Oneiric version of Nautilus. I find that dragging Folders into the left pane never creates a bookmark. Previously, I think I could drag folders 'in between' other folders in the left pane, seeing a black line indicating where the new bookmark would be placed. Now it's impossible to find a drag/drop target which creates a bookmark from a stock Oneiric until first running the keyboard shortcut CTRL+D to add an item. Once an item exists, a Bookmarks section appears in the Nautilus left pane, and then I can drag subsequent bookmarks under this heading. For Bookmarks to be a usable feature, there should be some kind of GUI- based technique to create them. Currently it requires deep understanding of Nautilus keyboard shortcuts to begin with. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.0.0-15.25-generic-pae 3.0.13 Uname: Linux 3.0.0-15-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Jan 23 22:20:35 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- 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/920691 Title: Nautilus has no Bookmark target until CTRL+D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/920691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 920691] Re: Nautilus has no Bookmark target until CTRL+D
-- 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/920691 Title: Nautilus has no Bookmark target until CTRL+D To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/920691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 677452] [NEW] Power applet shows as charging when unplugged
Public bug reported: Binary package hint: gnome-power-manager I have a dell inspiron 1525. It's possible there's some sequence like sleep, unplug, unsleep which creates the conditions for this bug to emerge. The behaviour, given the default Ubuntu settings, is that the battery applet just disappears completely (since it thinks it's charging, and by default it is not shown). I had to get into the power settings to change this, and then it became clear that it was confused about its charging state. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-power-manager 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Fri Nov 19 13:04:53 2010 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: Dell Inc. Inspiron 1525 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-generic root=UUID=a5d3c680-150c-4973-ba86-1a85a455337b ro quiet splash ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: gnome-power-manager dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid ubuntu-une -- Power applet shows as charging when unplugged https://bugs.launchpad.net/bugs/677452 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 677452] Re: Power applet shows as charging when unplugged
-- Power applet shows as charging when unplugged https://bugs.launchpad.net/bugs/677452 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 553301] Re: Music synced to iPod touch does not appear on device
Same problem here. Ipod Touch 2nd Gen 16GB is being identified as a 1Gb Shuffle (although the available space is reported correctly). Syncing appears to work, but nothing appears on the device at the end, so it appears to be syncing into a tree which isn't being read by the iPod Touch software, presumably because it's syncing as if it was a 1GB. Maybe there's a workaround to force it to treat the device as an iPod touch? Rhythmbox syncing is currently unusable for this reason. -- Music synced to iPod touch does not appear on device https://bugs.launchpad.net/bugs/553301 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 610036] Re: MTP plugin causes Mighty Mouse to hang
I disagree this is a low priority bug. It stops you using your point and click desktop altogether if you make the mistake of launching Rhythmbox (a default install) in its default configuration. This is pretty major if you ask me. If you're not familiar with keyboard navigation, then your choices are limited to a hard shutdown or nothing. I'm using a Kensington trackball, so it's not just Mighty Mouse. Basically the MTU plugin is killing the USB subsystem. It's also an easy fix. Deactivate the MTU plugin and let people install it/activate it if they want to deal with the issues arising, rather than sharing the fun with everyone. -- MTP plugin causes Mighty Mouse to hang https://bugs.launchpad.net/bugs/610036 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 610036] Re: MTP plugin causes Mighty Mouse to hang
I mean MTP plugin - sorry for typo. -- MTP plugin causes Mighty Mouse to hang https://bugs.launchpad.net/bugs/610036 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 596559] Re: Lost text file contents due to desktop bug - change autorecover defaults!
I'm not sure I agree. For me and countless others you could decide to have autosave ENABLED by default. I probably wasn't clear in my original bug report, but my point was that you have two modes. Sensible mode - keep my data Stupid mode - lose my data I'm questioning the logic by which 'Stupid mode' has been chosen as the default. Can anyone account for that? -- Lost text file contents due to desktop bug - change autorecover defaults! https://bugs.launchpad.net/bugs/596559 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 596559] Re: Lost text file contents due to desktop bug - change autorecover defaults!
This relates to the following bug too, which doesn't seem to have been accepted as something needing attention... https://bugs.launchpad.net/gedit/+bug/151365 ...and which just bit me - since activating 'autosave' I thought the editor would save automatically, but a previously unsaved file is the exception. This user report concurs... https://answers.launchpad.net/ubuntu/+question/14837 I can't really get away from the simple headline, - Text Editor Fails to Save Edited Text. If it was a human being with this responsibility, we'd expect their resignation on the desk Monday morning, so why do we put up with it in software. Steps to replicate - use gedit for a bit as a text editor - do not save, or save and do not realise you have to click 'autosave' in the preferences - encounter a problem (battery flat, non-resume from sleep, crash) - lose your hard-edited text -- Lost text file contents due to desktop bug - change autorecover defaults! https://bugs.launchpad.net/bugs/596559 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 596559] [NEW] Lost text file contents due to desktop bug - change autorecover defaults!
Public bug reported: Binary package hint: gedit Just recently updated to Lucid Lynx with a clean install. While authoring a text file full of project notes, my laptop went into some kind of sleep state (blank screen) and I was unable to return to the desktop without a hard shutdown in between. After rebooting I was shocked to discover that Gedit had abandoned all the text I was working on, and hadn't saved it anywhere! Quite a lot of important thoughts on a project plan and a temporary notes file are now lost, presumably due to a design decision to save those precious storage bytes on my harddrive. However, I feel more precious about my data than my bytes. I had trusted to gedit as an aide-memoire and it will be very hard for me to recover all of the notes from my head, since I'm not a computer. I don't know how recently the file was manually saved or which changes are now missing. My laptop on the other hand IS a computer. I would expect software to have smart defaults, so the computer reliably and periodically carries out a common-sense action, such as creating an auto-recovery file in case of a crash. Computers help to overcome human frailties. For example I forget to turn off 'please lose my data mode' in gedit after each reinstall or desktop migration. I'm now waiting for this to bite me on my work laptop (Karmic) if I don't forget to change the config when I go in on Monday. Could I suggest that the default is to leave 'lose your data mode' off, leaving it an option for people who have less than 10k free space on their hard-drive, photographic memories, or a tic which makes them hit CTRL-S every 10 minutes, to turn the mode back on again. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- Lost text file contents due to desktop bug - change autorecover defaults! https://bugs.launchpad.net/bugs/596559 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 587812] [NEW] Linux install in Virtualbox broken by authoritarian automount behaviour
Public bug reported: Binary package hint: nautilus I have been trying to install Lucid as a Guest OS onto to an SD card using Virtualbox-OSE running on Lucid as the Host OS. I've been doing it over and over and it failed each time. I believe I've found the problem and it's the automount behaviour from Gnome/Nautilus. After the Lucid installer in Virtualbox has completed formatting and unmounting the filesystem, and before it writes the grub information and reboots, Gnome/Nautilus steps in and automounts the SD card, killing the install process in Virtualbox, which throws an error like error mounting filesystem, daemon is inhibited. This behaviour makes the final installation (which took several hours each time) unbootable, since it never gets to finish the install. Can anyone provide information of how to turn this behaviour off in the host OS using a graphical tool, or a workaround using config files. I've tried very many things but none of them seem to apply to Lucid. It proceeds to helpfully remount the card whenever I put it back in (which is I think equivalent to the reappearance of the filesystem after reformatting in the guest OS). I believe people who author helpful automated behaviours, whatever they are, should be REQUIRED to provide a straightforward way to turn them off, as they seem to create almost as many problems as they solve, and it's a fraction of the work to provide an off button. Interestingly, the only partition which I DO want automounted is never automounted on boot - my windows partition which contains my music :( However I suspect boot time mounting is a different question. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.34~kms1-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Mon May 31 09:49:50 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid ubuntu-une -- Linux install in Virtualbox broken by authoritarian automount behaviour https://bugs.launchpad.net/bugs/587812 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 587812] Re: Linux install in Virtualbox broken by authoritarian automount behaviour
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49425530/Dependencies.txt ** Attachment added: usr_lib_nautilus.txt http://launchpadlibrarian.net/49425531/usr_lib_nautilus.txt -- Linux install in Virtualbox broken by authoritarian automount behaviour https://bugs.launchpad.net/bugs/587812 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 587812] Re: Linux install in Virtualbox broken by authoritarian automount behaviour
An example of something I've tried to prevent this automount behaviour is to add a line like this to /etc/fstab... /dev/mmcblk1p1 /mnt/ ext3 noauto 0 0 which places the mount point outside of /media and flags it as noauto. Both of these were alleged in previous versions to be the magic formula for communicating DO NOT MOUNT to the automount behaviour, instead of the checkbox I'm yearning for. -- Linux install in Virtualbox broken by authoritarian automount behaviour https://bugs.launchpad.net/bugs/587812 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 587812] Re: Linux install in Virtualbox broken by authoritarian automount behaviour
Although there are a million solutions offered out there for alternate linux and ubuntu builds which do not work on Lucid, I have good news. Lucid does indeed have a CHECKBOX! Hit Alt+F2 and then type gconf-editor Navigate to /apps/nautilus/preferences/media_automount Uncheck the box. This is a perfectly good answer for me, although it might be useful for more complex setups to be able to control this on a per device basis, and I don't know how to do this. Well done to the authors of this behaviour. Once I'd traced it to nautilus I should have done a more comprehensive search of the gconf- editor for some kind of control. Stupidly I didn't include 'key names' in the gconf-editor Find I did for the word 'mount'. When I got this right the checkbox magically appeared. ** Changed in: nautilus (Ubuntu) Status: New = Invalid -- Linux install in Virtualbox broken by authoritarian automount behaviour https://bugs.launchpad.net/bugs/587812 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 331608] Re: Rhythmbox unresponsive when deleting music from ipod
I can confirm similar behaviour on my Ubuntu (Mint) installation, pushing a few hundred tunes using an iPod Touch and the ifuse packages, as described here... http://fatbuttlarry.blogspot.com/2010/01/ipod-touch-iphone-3g-ubuntu-910-in-5.html I appreciate that mine isn't a mainstream supported system, and these packages don't come from the package repository, but seems to be the only way to get a non-jailbroken iPod Touch to work with Linux at all, so I'd expect these to migrate to the core in a future Ubuntu release. The greying out and unresponsiveness is the same. Eventually Rhythmbox becomes responsive again, but the transfer is running so slow that a 5 minute MP3 takes about 30 seconds to synchronise. I don't know for sure where the slowness comes from, but I suspect it may be the same aspect, since Rhythmbox syncing to crippled Crapple iPod technology is the common factor. Happy to probe my system in whatever way you recommend. Let me know what tests I can run to reliably eliminate other speed issues (iFuse) from the investigation. It's possible somehow the USB hub is being forced down to USB 1.0 or 1.1 speeds by something else on the same hub - I have a keyboard and mouse attached to it as well. Any ideas how to eliminate this possibility by monitoring runtime information in the system. -- Rhythmbox unresponsive when deleting music from ipod https://bugs.launchpad.net/bugs/331608 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 540582] Re: Creating isos of some DVDs fails with Data could not be written
Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1848) BraseroDvdcss called brasero_job_get_action BraseroDvdcss called brasero_job_get_action BraseroDvdcss called brasero_job_get_current_track BraseroDvdcss called brasero_job_set_output_size_for_current_track BraseroDvdcss stopping BraseroDvdcss called brasero_job_get_action BraseroDvdcss called brasero_job_get_session_output_size BraseroDvdcss output set (IMAGE) image = /media/Medium/out.iso toc = none BraseroDvdcss called brasero_job_get_action BraseroDvdcss called brasero_job_set_use_average_rate BraseroDvdcss called brasero_job_set_current_action BraseroDvdcss called brasero_job_get_current_track BraseroDvdcss called brasero_job_set_current_action BraseroDvdcss called brasero_job_get_fd_out BraseroDvdcss called brasero_job_get_image_output BraseroDvdcss called brasero_job_error BraseroDvdcss finished with an error BraseroDvdcss asked to stop because of an error error = 1 message = Data could not be written (Input/output error) BraseroDvdcss stopping Session error : Data could not be written (Input/output error) (brasero_burn_record brasero-burn.c:2808) -- Creating isos of some DVDs fails with Data could not be written https://bugs.launchpad.net/bugs/540582 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 540582] Re: Creating isos of some DVDs fails with Data could not be written
I experienced the same bug, which terminates in the same way. Above is the log from my session. -- Creating isos of some DVDs fails with Data could not be written https://bugs.launchpad.net/bugs/540582 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 540582] Re: Creating isos of some DVDs fails with Data could not be written
Turns out there was corruption in the DVD I was trying to backup. A workaround for the corrupted DVD I was reading was to do the copying from the command line with a different tool. To install the tool run... sudo apt-get install gddrescue ...or install gddrescue through a graphical package manager like synaptic then use the following to copy the stream in a way which abandons the corrupted sectors, rather than allowing them to junk the copy. In the terminal unmount the drive and start the copy process like this... umount /dev/sr0 ddrescue -d -n -b 2048 /dev/sr0 /home/cefn/out.iso /home/cefn/out.log ...where /dev/sr0 should be replaced with the raw path to your DVD device, and the other two paths are the disk image file and the log file respectively. I got the raw path /dev/sr0 of my DVD device by running... mount -l ...after the DVD had first automounted. It reported the line; /dev/sr0 on /media/cdrom0 type udf (ro,nosuid,nodev,utf8,user=cefn). Note it's the first path in this line about the cdrom drive which you should use. Depending on your permissions you may need to prefix commands with the word sudo to elevate your privileges so you can access devices directly. I thought this was really weird since I could view the DVD in VLC fine, but not copy it. It seems that DVD players already know how to handle corrupted sectors, but copy programs typically do not. Copies made of corrupted disks, even if they appear to work as far as the menu, come out as junk when you try to play the part of the video which is stored with corrupted sectors, since the copy program produces a disk image with different kinds of error than the corrupted original, and so the player can't use the same tricks to skip over corrupted sectors. Given the nature of this problem it would help if the error showed 'Data could not be read' rather than 'Data could not be written' since I spent a bunch of time checking my hard disks which were fine. -- Creating isos of some DVDs fails with Data could not be written https://bugs.launchpad.net/bugs/540582 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395124] Re: logout window appears behind other windows
Not sure I agree with the bug importance assignment here. I experience the bug as well, and it took a bit of time to work out what was going on, and the consequences can be serious. If the toolbar is configured to auto-hide, it's actually impossible to see anything happening at all when you choose Quit (or hit the power button). If you are not eagle eyed enough to spot the icon appearing in the toolbar, and know that that means a window has appeared behind the others and that you can raise it by clicking on the icon then you have no choice but to hard-shutdown the machine, since it's impossible to get to any shutdown controls. This in turn creates problems elsewhere. Indeed when I first experienced the bug, this is exactly what I did, seeing no alternative. -- logout window appears behind other windows https://bugs.launchpad.net/bugs/395124 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240916] Re: can't configure display resolution (monitor, graphics card) manually in gui
As a workaround, for those who can run command line tools, there's instructions how to generate the appropriate modelines and where to stick them in xorg.conf in a comment in the duplicate bug... https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/260436/comments/18 ...which has apparently been useful to some. I'll try to restate them more clearly here. They rely on two tools - gtf and xrandr - and a text editor. xrandr should be invoked with no arguments to tell you the names of your displays. These are the names which should be used in the xorg.conf later. Here's the output shown in my command line. c...@cefn-linux-tablet:~$ xrandr Screen 0: minimum 320 x 200, current 1280 x 768, maximum 1440 x 1792 VGA disconnected (normal left inverted right x axis y axis) LVDS connected 1280x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x768_60.00 60.0*+ 1280x768 59.9 + 1024x768 85.0 75.0 70.1 60.0 1024x600_60.00 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 72.8 75.0 59.9 720x40085.0 640x40085.1 640x35085.1 TV disconnected (normal left inverted right x axis y axis) Then gtf can be invoked to create a modeline suitable for you based on what you know about your display, maybe from reading the manual. c...@cefn-linux-tablet:~$ gtf 1440 900 60 # 1440x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 106.47 MHz Modeline 1440x900_60.00 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync Finally you should create an entry in your xorg.conf which combines all these bits of information. It's advisable to save a copy of your old xorg.conf with a new name, like xorg.conf.bak. In some cases your existing xorg.conf will be blank. My modified xorg.conf looked as below. Note the declaration of a virtual resolution which was wide enough to put the displays side by side or above each other... Section Monitor Identifier Configured Monitor EndSection Section Monitor Identifier VGA Modeline 1440x900_60.00 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync EndSection Section Screen Identifier Default Screen Monitor Configured Monitor Device Configured Video Device SubSection Display Virtual 1440 1700 EndSubSection EndSection Section Device Identifier Configured Video Device EndSection Once you've made these edits, and you log out and log back in, the new modeline should be visible even in your graphical tool like grandr. If not, you can invoke the display changes using xrandr. -- can't configure display resolution (monitor, graphics card) manually in gui https://bugs.launchpad.net/bugs/240916 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 260436] Re: Unable to force screen resolution with vtswitch/splitter
Glad I could help 3vil. It's a shame that there's no mechanism for ordinary people to achieve the same thing, for whom manually editing xorg.conf is a step too far. After all it only takes three gui fields and a go button! All the other tools are already in place - gtf, gnome resolution config, etc. I often wish I had the means to author this kind of software myself but I think it's a bit beyond me. -- Unable to force screen resolution with vtswitch/splitter https://bugs.launchpad.net/bugs/260436 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 260436] Re: Unable to force screen resolution with vtswitch/splitter
Could you reopen this bug. I can reproduce it and still have a KVM which prevents the autodetection capability from working. My suggestion that this should remain open is based on Bryce's interpretation of the bug/feature request earlier in this thread... https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/260436/comments/7 I can specify the changes which are required to xorg.conf and the xrandr invocations needed (if necessary - no doubt the Gnome resolution people know this stuff too). -- Unable to force screen resolution with vtswitch/splitter https://bugs.launchpad.net/bugs/260436 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 260436] Re: Unable to force screen resolution with vtswitch/splitter
I'm referring to your request a few hours ago... can you force the resolution using the xrandr command line tool? Yes you can force it using xrandr, assuming that you have edited xorg.conf properly. I've carried out these steps and proven that you can force the correct resolution regardless of auto-detection, through a KVM which suppresses the ordinary auto-detection signals. My suggestion is to permit users to manually specify modes in the graphical tool, and have the gnome screen resolution tool make the required changes to xorg.conf just as it does today with virtual resolution. It's to add this feature to the ubuntu environment that the original request was about - not having to manually edit xorg.conf. It's for this reason I'd like to keep the bug open and provide any maintainer with more information about the request. -- Unable to force screen resolution with vtswitch/splitter https://bugs.launchpad.net/bugs/260436 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 260436] Re: Unable to force screen resolution with vtswitch/splitter
The graphical tools DO list the same options as the xrandr command. That means that if the autodetection has failed to identify a valid mode by autodetection, you are screwed unless you like to edit xorg.conf. Then these options show up in xrandr and in the graphical tool. To fix the problem I had to manually generate a line using gtf thus... c...@cefn-linux-dell:~$ gtf 1440 900 60 # 1440x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 106.47 MHz Modeline 1440x900_60.00 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync Then weigh in and edit my xorg.conf, based on the output identifiers reported by xrandr. The xorg.conf for my specific monitor follows, but it took me the best part of half a day to work out enough about this problem to solve it. My mother wouldn't stand a chance, even if she could tell perfectly well what the values of horizontal pixels, vertical pixels and refresh rate actually were, since it involves manually editing config files in mysterious and ill-documented ways! Since the bug/feature request is about the need to avoid manually editing config files, and I'm providing information about it, I don't know why you keep re-closing it? You only gave me an hour to get back to you this time before re- reporting the bug/feature request as closed. Maybe I don't understand the status reporting properly, or the nature of the bug and where it currently is in the system, so forgive me if I'm confusing matters somehow and let me know how to file this request properly. Anyway here's the example xorg.conf which could be generated by the graphical tool from those three parameters to help my mum out. Grandr already does the Virtual resolution bit automatically just the same way. What I'm suggesting is adding three fields to the gui tool (in my case 1440,900,60) and an invocation of gtf, followed by an automatic edit of xorg.conf and a message to re-log-in, just as it does with the Virtual resolution line. Section Monitor Identifier Configured Monitor EndSection Section Monitor Identifier VGA Modeline 1440x900_60.00 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync EndSection Section Screen Identifier Default Screen Monitor Configured Monitor Device Configured Video Device SubSection Display Virtual 1440 1700 EndSubSection EndSection Section Device Identifier Configured Video Device EndSection -- Unable to force screen resolution with vtswitch/splitter https://bugs.launchpad.net/bugs/260436 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
