[Bug 454146] [NEW] Cannot expand templates with tab key
Public bug reported: Binary package hint: scribes On upgrading to Ubuntu 9.04, Scribes no longer expands templates using the tab key. In fact, the name of the template is just deleted in the editor. Reproduce: 1. Create a template 2. In the editor, type the template name 3. It will now turn bold and Scribes will say in the status bar that it detected a template 4. Press tab 5. The name of the template is erased from the editor I have attached a Python traceback of the error. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: scribes 0.3.3.3-4 PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: scribes Uname: Linux 2.6.28-15-generic x86_64 ** Affects: scribes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Cannot expand templates with tab key https://bugs.launchpad.net/bugs/454146 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 454146] Re: Cannot expand templates with tab key
** Attachment added: Python traceback http://launchpadlibrarian.net/33843267/error.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33843268/Dependencies.txt -- Cannot expand templates with tab key https://bugs.launchpad.net/bugs/454146 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 367630] Re: new kvm machines created with wrong keyboard
*** This bug is a duplicate of bug 348364 *** https://bugs.launchpad.net/bugs/348364 ** This bug has been marked a duplicate of bug 348364 Selecting same as host for keymap doesn't really select the host keymap -- new kvm machines created with wrong keyboard https://bugs.launchpad.net/bugs/367630 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 295944] Re: 'unmount' fails for user mounted file system
@Kevin. This is an ugly hack. But if you put your second line beginning with /dev/loop0 into your /etc/fstab, then you will be able to run the unmount for your /mounts dmgfile. Just remember to add noauto so it doesn't mount twice on bootup. -- 'unmount' fails for user mounted file system https://bugs.launchpad.net/bugs/295944 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152271] Re: Error when enabling visual effects in appearance preferences under Gutsy
@Martin In Intrepid Ibex, this has still not been addressed. The radio buttons are still fully active, waiting for a user to click on them, despite not being supported on my hardware. After clicking on Normal or Extra, I am greeted with a 5 second delay with a dialog saying it is searching for whether the composite extension is installed. When it doesn't find, it bombs out with the same error dialog: The Composite extension is not available. In the original bug description, you will find my description for why this is not the correct behaviour for radio buttons. -- Error when enabling visual effects in appearance preferences under Gutsy https://bugs.launchpad.net/bugs/152271 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 152271] Re: Error when enabling visual effects in appearance preferences under Gutsy
@Johnathon: Nice script, but the problem is the design of the Visual Effects tab in the gnome-appearance-properties dialog. -- Error when enabling visual effects in appearance preferences under Gutsy https://bugs.launchpad.net/bugs/152271 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 209901] Re: webcam Logitech QuickCam Messenger ID 046d:08f6 is not reconized
I'm using Intrepid Ibex and my quickcam works with Skype but not in Cheese or Camorama. So either its a bug in both programs, or its something more general. Its worth pointing out that my /dev/video0 does actually exist. -- webcam Logitech QuickCam Messenger ID 046d:08f6 is not reconized https://bugs.launchpad.net/bugs/209901 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 200357] Re: syncropated crashed with DBusException in call_blocking()
I confirm I have the same bug in Intrepid Ibex x86_64 and that the above patch fixes the issue. -- syncropated crashed with DBusException in call_blocking() https://bugs.launchpad.net/bugs/200357 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 121653] Re: [gutsy] fglrx breaks over suspend/resume
@Bernhard Gehl: Whenever you are in doubt about the cause of any bug, just blame dbus. -- [gutsy] fglrx breaks over suspend/resume https://bugs.launchpad.net/bugs/121653 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 186623] Re: Cannot set lock option in menu.lst without being overriden by update-grub
@Steve It seems you are saying you can't imagine any scenarios where someone would want to lock their default kernel. I don't think its that difficult, please try. Here is just one. You work for a company where official policy dictates you may only use Windows workstations; any unauthorised software installation is forbidden. Due to pressing business requirements, your boss gives you the go-ahead to install Ubuntu on a workstation as long as nobody finds out. The last thing you need is for a technician to accidentally discover you have a Linux workstation on there - perhaps they were delivering some hardware update. Having grub bork an unauthorised error is a good way to achieve that, there is plausible deniability. -- Cannot set lock option in menu.lst without being overriden by update-grub https://bugs.launchpad.net/bugs/186623 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186623] [NEW] Cannot set lock option in menu.lst without being overriden by update-grub
Public bug reported: Binary package hint: grub In the menu.lst, it explains in the password section about using the lock command. However, the lock command is not part of the automagic kernel default options sections. Yes, there are options for alternative and old kernels (lockalternative, lockold), but how do I lock my default kernel? If I do set the lock option manually by changing the automagic kernels list and appending the lock keyword under the title of my default kernel, it does work okay. However this is not really a solution since users are not supposed to modify the automagic kernel section. It will be overridden by update- grub the next time the kernel is upgraded and update-grub is run. What is required is a feature-enhancement of update-grub in order to add the lock option to kernels in the default options section. Apologies if there is already a way to do this. But I have been through all the docs I could find and I did not find anything suitable. This is different from bug #21412 since I am not saying the options are not user friendly. Rather, there is no option to set this feature. Version: Ubuntu 7.10, grub 0.97-29ubuntu4 ** Affects: grub (Ubuntu) Importance: Undecided Status: New -- Cannot set lock option in menu.lst without being overriden by update-grub https://bugs.launchpad.net/bugs/186623 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 186623] Re: Cannot set lock option in menu.lst without being overriden by update-grub
Thanks for confirming and also pointing out that the lock option won't be silently overridden by upgrades anymore. At this point it seems the bug title is no longer relevant. Rather it could be Cannot set lock option without messy kernel upgrade procedure. To clarify, I am making the case for a new option called lockdefault which will do for the default kernel what the other locks for other kernels. My thoughts are that if you are going through all the trouble of looking out for the lock option, and then bailing out of a grub update because you don't want to override it, you might as well just support the lock option in the automagic default options so that kernel upgrades aren't problematic. Another point is that the lock option is a grub _feature_ which people do use on their default kernel, regardless of breakage and inconveniences relating to debian's update-grub. It is debatable whether such people are misguided, but they will no doubt continue to use the lock option in this way under the impression that their system is more secure that way. I accept that people who do this are not going to have unattended upgrades. However, I did not suggest that the distro is shipped with the lock option enabled by default and thereby break the unattended upgrades. Rather, this is a feature for those who do edit the menu.lst by hand. -- Cannot set lock option in menu.lst without being overriden by update-grub https://bugs.launchpad.net/bugs/186623 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184072] update-manager notifications unreadable with dark themes
Public bug reported: Binary package hint: update-manager When using a dark theme such as Darklooks from gnome-theme-extras, the notifications that are produced by update-manager are unreadable. In particular, when using a dark theme there is a bright foreground font with a bright background color. This renders the notification illegible. In order to be legible, either the foreground font color should be set to being black or else the background color should be dark. This way the notification will be legible regardless of theme. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- update-manager notifications unreadable with dark themes https://bugs.launchpad.net/bugs/184072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184072] Re: update-manager notifications unreadable with dark themes
Sorry I just realised this is not a problem specific to update-manager. Rather, it is the gnome-notifications system that is getting the color wrong. I just received notification from Evolution which had same the problem. I will try to attach a screenshot. -- notifications are difficult to read with dark themes https://bugs.launchpad.net/bugs/184072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184072] Re: update-manager notifications unreadable with dark themes
** Attachment added: gnome notification when using darklooks theme http://launchpadlibrarian.net/11429964/notification-darklooks.png ** Summary changed: - update-manager notifications unreadable with dark themes + notifications are difficult to read with dark themes ** Description changed: - Binary package hint: update-manager + Binary package hint: notification-daemon When using a dark theme such as Darklooks from gnome-theme-extras, the - notifications that are produced by update-manager are unreadable. + notifications that are produced bynotification-daemon are unreadable. In particular, when using a dark theme there is a bright foreground font with a bright background color. This renders the notification illegible. In order to be legible, either the foreground font color should be set to being black or else the background color should be dark. This way the notification will be legible regardless of theme. -- notifications are difficult to read with dark themes https://bugs.launchpad.net/bugs/184072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184072] Re: notifications are difficult to read with dark themes
Michael: yes, this is on Gutsy but I have not tested on Hardy. ** Description changed: Binary package hint: notification-daemon When using a dark theme such as Darklooks from gnome-theme-extras, the - notifications that are produced bynotification-daemon are unreadable. + notifications that are produced by notification-daemon are unreadable. In particular, when using a dark theme there is a bright foreground font with a bright background color. This renders the notification illegible. In order to be legible, either the foreground font color should be set to being black or else the background color should be dark. This way the notification will be legible regardless of theme. -- notifications are difficult to read with dark themes https://bugs.launchpad.net/bugs/184072 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181890] Re: Deleted items always empty when home is encfs folder
Pedro: What more information do you need to change the status from INCOMPLETE? -- Deleted items always empty when home is encfs folder https://bugs.launchpad.net/bugs/181890 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182272] Re: mergeant package is missing dependencies
Or rather that mergeant should use the gnome-database-properties-3.0 binary rather than gnome-database-properties binary. -- mergeant package is missing dependencies https://bugs.launchpad.net/bugs/182272 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182272] mergeant package is missing dependencies
Public bug reported: Binary package hint: mergeant When installing mergeant, apt-get also brought in the following: libgda3-sqlite libgnomedb3-4 libgnomedb3-bin libgnomedb3-common After starting mergeant, I accepted default connection to SalesTest data source. The problem is that it is not possible to edit the data sources. Pressing the Datasource button or selecting the menuitem brings up an error dialog with the following text: Could not find the 'gnome-database-properties' program: Failed to execute child process gnome-database-properties (No such file or directory) So I tried installing libgnomedb3-bin, but that didn't work because the binary in that file is gnome-database-properties-3.0 so mergeant doesn' t pick it up. Perhaps libgnomdb3-bin should use the debian-alternatives system so it can create a symlink from gnome-database-properties to gnome- database-3.0? ** Affects: mergeant (Ubuntu) Importance: Undecided Status: New -- mergeant package is missing dependencies https://bugs.launchpad.net/bugs/182272 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181890] Re: Deleted items always empty when home is encfs folder
This is on Ubuntu 7.10 Gutsy x86_64. -- Deleted items always empty when home is encfs folder https://bugs.launchpad.net/bugs/181890 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181890] Deleted items always empty when home is encfs folder
Public bug reported: Binary package hint: gnome-applets My home folder is mounted using libpam-encfs on login. This makes use of FUSE. Some information on how to do this is here - https://help.ubuntu.com/community/FolderEncryption The problem is that now the Deleted Items folder is always empty, even though $HOME/.Trash contains files. I don't think this is a duplicate of bug #34247 since this is specifically about FUSE. ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New -- Deleted items always empty when home is encfs folder https://bugs.launchpad.net/bugs/181890 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
** Attachment added: output of /var/log/messages when doing modprobe for e1000 http://launchpadlibrarian.net/11158730/modprobe_messages -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
** Attachment added: dmesg http://launchpadlibrarian.net/11158711/dmesg -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Unable to connect to wired network
Public bug reported: Binary package hint: network-manager On my laptop, I am unable to use the ethernet port to connect to a wired network. I noticed this problem on the Gutsy LiveCD and now on Gutsy after installation. Using nm-tool, it seems like NetworkManager does see my ethernet card as eth0. It reports its driver as e1000 and everything else OK. However, nothing happens after connecting ethernet cable. I checked output of /var/log/daemon.log as well as other log files, but did not find any activity. Going into the nm-applet, the Wired Network option is greyed out. I also tried the following: - I went to nm-applet - Manual configuration - I disabled roaming mode for the Wired connection - I set Configuration to DHCP and pressed OK - Note that the checkbox next to Wired connection is now unchecked - At this point, NetworkManager logged some output, see daemon_log_1 - I then clicked the checkbox next to Wired connection to activate it - Now, NetworkManager logged some more output, see daemon_log_2 What is interesting about the daemon.log output is that it keeps referring to eth1, which is the wireless card. I tried something else, which is to uncheck the Wired connection in NetworkManager and to go to the command line. I checked /etc/network/interfaces contained the following: iface eth0 inet dhcp. I also unloaded my wireless card's driver by doing modprobe -r ipw3945. I then tried to do an ifup eth0 but from the log output it seems like DHCPD could not find an IP address. I have already eliminated problems with the cable or router, by testing on another Linux laptop where I could connect to the internet OK. It got DHCP and everything. Another theory is maybe its something to do with IRQ's. I noticed when I ran modprobe -r e1000, I got the following message in the syslog: ACPI: Unable to derive IRQ for device :00:19.0 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
** Attachment added: trying nm manual configuration - daemon.log part 2 http://launchpadlibrarian.net/11158718/daemon_log_2 -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
** Attachment added: trying to do run ifup eth0 http://launchpadlibrarian.net/11158725/ifup_eth0 -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
** Attachment added: trying nm manual configuration - daemon.log part 1 http://launchpadlibrarian.net/11158716/daemon_log_1 -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
** Attachment added: lspci http://launchpadlibrarian.net/11158707/lspci -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180440] Re: Unable to connect to wired network
*** This bug is a duplicate of bug 151887 *** https://bugs.launchpad.net/bugs/151887 ** This bug has been marked a duplicate of bug 151887 82562GT ethernet card does not work in Linux-source-2.6.22-14 -- Unable to connect to wired network https://bugs.launchpad.net/bugs/180440 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151887] Re: 82562GT ethernet card does not work in Linux-source-2.6.22-14
I was affected by this bug on HP 6820s hardware. I found out I was using version F.02 of the BIOS After installing version F.07 of the BIOS, the ethernet port works out of the box. For anyone worried about how to do a BIOS update without running Windows. I basically downloaded sp38153.exe from the driver page, which was ROMPaq for HP Notebook System BIOS - FreeDOS Bootable Media. You can run this using WINE or any other emulator. All it does is unpack a few files into a folder you specify. Once unpacked, you will find an ISO there. There are two ISO's that are unpackad. I assume that one is for 6820s and one for 6520s. For the 6820s hardware, you need the ISO in the sp38153d folder. I deduced this from the output of dmesg by running dmesg | grep 30D. Look up the value 30D7 or 30D8 in the file map.ini within the sp38153 folder. I found out that sp38153d was the right one for my hardware. I think a BIOS update is the solution here, as all the confirmations of the bug seem to be for HP hardware. So, can we go ahead and close this bug?? -- 82562GT ethernet card does not work in Linux-source-2.6.22-14 https://bugs.launchpad.net/bugs/151887 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158385] Re: addons path wrong in debian.vim
I think we should mark this as a duplicate of bug #163583. As described in the previous comment, there are new debian vim guidelines. However, a registry file was not added for the vim-outliner in Gutsy. That is why vim outliner it is broken, and not because of /usr/share/vim/vim71/debian.vim. Once you create the file vim-vimoutliner.yaml in /usr/share/vim/registry, then you can get it working for your user using vim-addons. This is described above. -- addons path wrong in debian.vim https://bugs.launchpad.net/bugs/158385 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174782] Re: bad colours playing movies in totem-gstreamer with xv output driver
Example attached featuring Eben Moglen. ** Attachment added: fsf_moglen.png http://launchpadlibrarian.net/10794304/fsf_moglen.png -- bad colours playing movies in totem-gstreamer with xv output driver https://bugs.launchpad.net/bugs/174782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174782] bad colours playing movies in totem-gstreamer with xv output driver
Public bug reported: Binary package hint: totem-gstreamer SUMMARY Playing movies in Totem under Ubuntu Gutsy does not render them in their correct colours. If anything they look blue. STEPS TO REPRODUCE Play any movie in Totem. I have tested different formats such as ogg mov avi mpg. WORKAROUND Force gstreamer not to use xv driver: gstreamer-properties Video Plugin: Change Autodetect to X Window System (no xv). It is worth pointing out that mplayer renders all videos correctly. Also VLC will play them correctly for x11 and opengl output drivers. HARDWARE * Mobile Intel PM965 chipset * ATI Mobility Radeon X1350 graphics ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: totem-gstreamer SUMMARY - Playing movies in Totem does not render them in their correct colours. If anything they look blue. + Playing movies in Totem under Ubuntu Gutsy does not render them in their correct colours. If anything they look blue. STEPS TO REPRODUCE Play any movie in Totem. I have tested different formats such as ogg mov avi mpg. WORKAROUND Force gstreamer not to use xv driver: gstreamer-properties Video Plugin: Change Autodetect to X Window System (no xv). It is worth pointing out that mplayer renders all videos correctly. Also VLC will play them correctly for x11 and opengl output drivers. HARDWARE * Mobile Intel PM965 chipset * ATI Mobility Radeon X1350 graphics -- bad colours playing movies in totem-gstreamer with xv output driver https://bugs.launchpad.net/bugs/174782 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163583] Re: no registry entry for vim-addons
I use vimoutliner also. After upgrading from Feisty to Gutsy, vimoutliner stopped working. The reason is that the addon path /usr/share/vim/addons has been removed from /usr/share/vim/debian.vim. Probably this was done in line with the new vim policy cited above so that addons would instead have to place a file in the registry under /usr/share/vim/registry. Unfortunately, vim-vimoutliner does not place such a file there. Thanks, yard. The yaml file does the trick, along with vim-addons install vim-outliner. -- no registry entry for vim-addons https://bugs.launchpad.net/bugs/163583 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132833] Jürgen's patch works
Sebastian: I am confused by your comments: Could people stop to apply such workaround? you are breaking next upgrades this way but will probably not notice for some time until the configuration change in the package and then you will wondering why the upgrades are broken Which workarounds are you talking about? The reason is there are two sets of solutions people are proposing. One is simply to set the value of BACKCOLOR, and the second one is Jürgen's fix. Isn't the gdmflexiserver the problem? Jürgen's fix @ https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/132833/comments/11 replaces every gdmflexiserver with gdmflexiserver -a. I confirm that this works. -- login background color is hardcoded https://bugs.launchpad.net/bugs/132833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132833] Re: login background color is hardcoded
Sebastian: From what I understand, you are saying people should not be modifying files under /etc/gdm because this will break upgrades. This is fair enough. But still no clarity about whether in the short term, Jürgen's fix is the right way or not. -- login background color is hardcoded https://bugs.launchpad.net/bugs/132833 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152265] Bug is not fixed yet
Sorry, Sarah. I don't think this bug should be marked as fixed. What I meant in my most recent comment is that manually configuring the usplash.conf _does_ fix the problem. However, I just reinstalled Gutsy and it didn't set the settings correctly. Every time I booted up and shut down, the splash screen did not appear and I saw junk on the console. I had to manually edit usplash.conf to get it to appear. So I don't think it is fixed since the installer is not setting the right values in usplash.conf. -- Splash screen doesn't appear under Gutsy after installation https://bugs.launchpad.net/bugs/152265 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152265] Re: Splash screen doesn't appear under Gutsy after installation
*** This bug is a duplicate of bug 150930 *** https://bugs.launchpad.net/bugs/150930 That is appropriate at this point, since usplash works after manual modification. -- Splash screen doesn't appear under Gutsy after installation https://bugs.launchpad.net/bugs/152265 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152271] Re: Error when enabling visual effects in appearance preferences under Gutsy
JoshBlacker: They are related but they are not the same. The bug 149972 is reporting that the visual effects tab is buggy: the OK button does not do anything and the only way to get rid of it is to press the X. This bug does is concerned with the fact there is a whole page devoted to desktop effects and all the radio buttons are active and waiting to be clicked, when in fact visual effects will not work. It does not concern the fact the buttons are buggy. -- Error when enabling visual effects in appearance preferences under Gutsy https://bugs.launchpad.net/bugs/152271 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133363] Re: suspend-to-ram problems with fglrx module loaded
From my past experience, I have found that ATI's installer does not integrate well with a Debian or Ubuntu system. So I will not be able to test the latest drivers until they are packaged by Ubuntu. I would also not recommend the drivers to others. -- suspend-to-ram problems with fglrx module loaded https://bugs.launchpad.net/bugs/133363 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152265] Re: Splash screen doesn't appear under Gutsy after installation
I am happy to report that after upgrading from the Gutsy RC to the final release, the splash screen now does appear. In fact, I tried entering my actual screen resolution of 1440x900 in the usplash.conf and it worked. It also worked with 1280x800 which was recommended above. What I have yet to test is whether this works out of the box with a fresh Gutsy install, rather than an existing install where the usplash.conf has to be tweaked. I will test that shortly. -- Splash screen doesn't appear under Gutsy after installation https://bugs.launchpad.net/bugs/152265 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152265] Re: Splash screen doesn't appear under Gutsy after installation
*** This bug is a duplicate of bug 150930 *** https://bugs.launchpad.net/bugs/150930 Changing the resolution in usplash.conf did not fix it for my hardware. I am going to follow up with the other bug #150930. -- Splash screen doesn't appear under Gutsy after installation https://bugs.launchpad.net/bugs/152265 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150930] Re: Black screen, and bad usplash.conf
I reported bug #152265 with similar problems. The screen is blank while booting up, however it did appear with the livecd but at the wrong resolution (it was not widescreen). Just to point out my laptop is widescreen with resolution 1440x900. Hardware is Mobile Intel PM965 chipset with ATI Mobility Radeon X1350 graphics. Roel Huybrechts suggested modifying the usplash.conf to 1024x768. So I looked in /etc/usplash.conf and found the resolution to be 1280x1024. I changed it to 1024x768 but the screen was still blank during booting up. Also the same if I changed it to 1440x900. -- Black screen, and bad usplash.conf https://bugs.launchpad.net/bugs/150930 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152265] Splash screen doesn't appear under Gutsy after installation
Public bug reported: Binary package hint: usplash The splash screen appears OK when using the livecd, but after installing Ubuntu on the hard drive the splash screen no longer appears when booting up. This is on a HP Compaq 6820s laptop with: * Mobile Intel PM965 chipset * ATI Mobility Radeon X1350 graphics ** Affects: usplash (Ubuntu) Importance: Undecided Status: New -- Splash screen doesn't appear under Gutsy after installation https://bugs.launchpad.net/bugs/152265 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152271] Error when enabling visual effects in appearance preferences under Gutsy
Public bug reported: Binary package hint: gnome-control-center In the Visual Effects tab of the GNOME Appearance preferences, selecting Normal or Extra visual effects pops up an error dialog box with the message: The Composite extension is not available. This is not a very helpful because it does not give any further instructions on what needs to be done to get visual effects working. For example, Ubuntu could automatically download and configure XGL. In addition, it is integrated into the GNOME Appearance applet so one would EXPECT it to work out of the box, like any of the other tabs in the applet. If the feature is not going to be supported on my hardware, the radio buttons should be greyed out and a suitable message displayed with the reason why I cannot access them. The graphics hardware is ATI Mobility Radeon X1350. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Error when enabling visual effects in appearance preferences under Gutsy https://bugs.launchpad.net/bugs/152271 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133363] Re: suspend-to-ram problems with fglrx module loaded
I can confirm this problem with Gutsy RC and ATI Radeon X1300. Blacklisting the fglrx driver allows suspend/resume to work. kernel: 2.6.22-14-generic #1 SMP Wed Oct 10 05:28:36 GMT 2007 x86_64 GNU/Linux -- suspend-to-ram problems with fglrx module loaded https://bugs.launchpad.net/bugs/133363 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133363] Re: suspend-to-ram problems with fglrx module loaded
Correction: I misreported my GFX card above. I actually have ATI Mobility RadeonTM X1350 Graphics installed. -- suspend-to-ram problems with fglrx module loaded https://bugs.launchpad.net/bugs/133363 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152375] Touchpad tab in gnome-mouse-properties on Gutsy with xserver-xgl
Public bug reported: Binary package hint: xserver-xgl When the regular xserver that ships with Gutsy RC, I can set the properties for my touchpad (such as disable tap to click) from within Mouse Preferences (gnome-mouse-properties). However after installing xserver-xgl the Touchpad tab in gnome-mouse- properties disappears. Bring it back! ** Affects: xserver-xgl (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Touchpad tab in gnome-mouse-properties on Gutsy with xserver-xgl + Touchpad tab missing in gnome-mouse-properties on Gutsy with xserver-xgl -- Touchpad tab missing in gnome-mouse-properties on Gutsy with xserver-xgl https://bugs.launchpad.net/bugs/152375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152375] Re: Touchpad tab missing in gnome-mouse-properties on Gutsy with xserver-xgl
** Description changed: Binary package hint: xserver-xgl - When the regular xserver that ships with Gutsy RC, I can set the + With the regular xserver that ships with Gutsy RC, I can set the properties for my touchpad (such as disable tap to click) from within Mouse Preferences (gnome-mouse-properties). However after installing xserver-xgl the Touchpad tab in gnome-mouse- properties disappears. - - Bring it back! -- Touchpad tab missing in gnome-mouse-properties on Gutsy with xserver-xgl https://bugs.launchpad.net/bugs/152375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83028] Re: linHDD missing menu entry
You must use on kubuntu for example: 'sudo linHDD' not 'sudo linhdd' Saurus: Sam Cater's comment where he wrote sudo linhdd is wrong. Because the actual command is sudo linHDD as you point out. Other than this, is there something you wanted to add to this bug report? Because currently I am not sure what you are drawing attention to. -- linHDD missing menu entry https://bugs.launchpad.net/bugs/83028 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49340] Re: Forgets Fit Page Width option on each click on the index
sorry, but this is not fixed yet. i am still experiencing this problem with ubuntu feisty. i have a pdf which i set my layout to page width. whenever i click an entry in the index on the left-hand side the layout changes to best fit. every time i click a link, i have to change the layout back to page width, my preferred way of reading this particular ebook. using an example that is already mentioned, if you download flyspeck.zip provided by Gaëtan de Menten, you will notice that handout2-skills.pdf, among others, will force 125% page layout. however the first file in this archive handout1-classes.pdf has no such problem. -- Forgets Fit Page Width option on each click on the index https://bugs.launchpad.net/bugs/49340 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49340] Re: Forgets Fit Page Width option on each click on the index
shall i reopen a bug report or are we staying in this one? -- Forgets Fit Page Width option on each click on the index https://bugs.launchpad.net/bugs/49340 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59765] Re: wrong button labels in xfce-setting-show
Confirmed on Ubuntu 6.10 with English GB locale. This bug has not been fixed for a while. -- wrong button labels in xfce-setting-show https://bugs.launchpad.net/bugs/59765 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83026] Re: linHDD application broken
My bad. I thought because the bug has been fixed upstream, the correct status for it now is Fix Released. I guess that is not the case. -- linHDD application broken https://bugs.launchpad.net/bugs/83026 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83026] Re: linHDD application broken
I performed some basic debugging and discovered at least one problem in linHDD's source code. At line 381, self.perc is an empty string. Firstly, I suspect it should not be returning an empty string, so there could be an issue with self.get_free(). Perhaps it is parsing the output of df incorrectly. Secondly, at line 382, comparing it with None will never succeed because an empty string never None. This is the main problem why linHDD breaks. Changing this to string comparison fixed the problem. There is a patch attached. I will also get in touch with the author. Hope this helps. ** Attachment added: Fixed linHDD for some setups http://librarian.launchpad.net/6919538/linHDD.patch -- linHDD application broken https://launchpad.net/bugs/83026 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83028] Re: linHDD missing menu entry
i would suggest using gksu so it pops up a password prompt in the gui. this is consistent with other .desktop entries in ubuntu. but all this work would be in vain unless bug#83026 is fixed. have you had a chance to look at that one? -- linHDD missing menu entry https://launchpad.net/bugs/83028 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83028] linHDD missing menu entry
Public bug reported: Binary package hint: linhdd Currently, linHDD is missing a .desktop entry and does not appear in the menu's. Since linHDD should be run as the root user, the menu entry should go into System Tools. ** Affects: linhdd (Ubuntu) Importance: Undecided Status: Unconfirmed -- linHDD missing menu entry https://launchpad.net/bugs/83028 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83026] linHDD application broken
Public bug reported: Binary package hint: linhdd linHDD should be run as the root user, but it broken when running it as the root user. linHDD is a promising replacement for disks-admin which was removed from Ubuntu starting from Edgy. Essentially linHDD is a front-end to cfdisk. It is of very little use to run it as a non-root user since it is not possible to do any operation. In particular, an error message appears /dev/hda: Permission denied, and the Partition and Format operations are greyed-out. When running as the root user, the following errors appear: $ gksudo linHDD File /usr/bin/linHDD, line 534, in ? main() File /usr/bin/linHDD, line 529, in main DriveWin() File /usr/bin/linHDD, line 387, in __init__ self.frac = float(self.perc.rstrip(%)) / 100 ValueError: empty string for float() Additional Information: - Tested on Ubuntu Edgy x86. ** Affects: linhdd (Ubuntu) Importance: Undecided Status: Unconfirmed -- linHDD application broken https://launchpad.net/bugs/83026 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70057] Re: sun-java5-plugin does not set up equivalents
It is true that java-package did not remove the equivalents properly. But that does not matter in the case of the bug I reported with sun- java5. What I reported is that sun-java5-plugin should have proceeded instead of bombing out. There is no reason why it could not add itself to the equivalents system. This is the bug. -- sun-java5-plugin does not set up equivalents https://launchpad.net/bugs/70057 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70057] sun-java5-plugin does not set up equivalents
Public bug reported: After installing sun-java5-plugin, Firefox did not detect the Sun java plugin. On my system I had previously installed Java using a package that modified the equivalents. In particular, the old java package I had used set the following equivalents: /etc/alternatives/firefox-javaplugin.so - /usr/lib/j2sdk1.5-sun/jre/plugin/i386/ns7/libjavaplugin_oji.so /etc/alternatives/mozilla-javaplugin.so - /usr/lib/j2sdk1.5-sun/jre/plugin/i386/ns7/libjavaplugin_oji.so /etc/alternatives/netscape-javaplugin.so - /usr/lib/j2sdk1.5-sun/jre/plugin/i386/ns4/libjavaplugin.so Unfortunately, upon uninstallation, it did not clean up these equivalents. They were left as bad symlinks. When I installed the sun-java5-plugin package, it did not update the equivalents. In particular, it left firefox-javaplugin.so and mozilla- javaplugin.so alone. As a result, even running sudo update-alternatives --config firefox- javaplugin.so, for example did not do anything, since there was no equivalent installed. I am guessing that sun-java5-plugin didn't install its equivalent either because an equivalent was already there, or because the existing equivalent was effectively a dead symlink (usr/lib/j2sdk1.5 no longer exists). The fix was for me to manually remove the equivalents that were causing the problem and then reinstall sun-java5-plugin: apt-get remove sun-java5-plugin update-alternatives --remove-all firefox-javaplugin.so update-alternatives --remove-all mozilla-javaplugin.so update-alternatives --remove-all netscape-javaplugin.so apt-get install sun-java5-plugin I feel that sun-java5-plugin should have added its equivalents instead of bombing out and set them to be default. ** Affects: sun-java5 (Ubuntu) Importance: Undecided Status: Unconfirmed -- sun-java5-plugin does not set up equivalents https://launchpad.net/bugs/70057 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37521] Re: Zoom menu missing text
This was reported in Breezy Badger, still broken in Dapper Drake, and now not fixed in Edgy Eft. What is the deal with this bug? Imagine everyone in the UK does not have a working zoom box. How does that reflect on Ubuntu? -- Zoom menu missing text https://launchpad.net/bugs/37521 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37362] Re: unmount of encrypted volume via menu broken
** Bug 33859 has been marked a duplicate of this bug -- unmount of encrypted volume via menu broken https://launchpad.net/bugs/37362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33859] Re: disk-mount applet fails to umount a luks encrypted usbstick
*** This bug is a duplicate of bug 37362 *** ** This bug has been marked a duplicate of bug 37362 unmount of encrypted volume via menu broken -- disk-mount applet fails to umount a luks encrypted usbstick https://launchpad.net/bugs/33859 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37362] Re: unmount of encrypted volume via menu broken
I am still running Dapper. Yes this is broken for me since upgrading to Dapper. It worked fine in Breezy. Is there any chance of getting this fixed in Dapper, please. Or can someone post a howto/patch to getting the behaviour fixed. I don't think its right to expect people to wait for Edgy, or else upgrade to Edgy at this point, just to have this working properly. -- unmount of encrypted volume via menu broken https://launchpad.net/bugs/37362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
