[Bug 1062623] Re: enable grub-2.00 boot-from-luks support
Thanks for keeping this updated Adam! I don't complete understand though - I believe the only real change needed is that this step: 8: append GRUB_CRYPTODISK_ENABLE=y to /etc/default/grub gets done automatically. Would it be harmful to just stick that in the default template for all setups? Other than causing a few extra modules to be installed in the grub partition, I don't think it would do any bad, or? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062623 Title: enable grub-2.00 boot-from-luks support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1062623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062623] Re: enable grub-2.00 luks support
I erroneously filed this bug against partman-crypto - should have probably been grub-installer. ** Package changed: partman-crypto (Ubuntu) = grub-installer (Ubuntu) ** Summary changed: - enable grub-2.00 luks support + enable grub-2.00 boot-from-luks support ** Description changed: (I suppose this comes too late in the release cycle to make the change, but perhaps it's simple enough:) With only minimal manual intervention, I found I could use today's Ubuntu Server 12.10 daily iso to install a system with luks+lvm and no separate /boot partition (which doesn't really have any security advantages, but it makes managing space on a smallish disk easier). If - partman-crypto could manage the final 2 steps below, it would all be + grub-installer could manage the final 2 steps below, it would all be fully automatic. Thanks! Steps: 1: go through the default installer motions 2: in partman, choose the manual option 3: create a single, whole-disk primary partition, use it as a luks encrypted volume 4: on top of that, create an lvm physical volume 5: insert lvm logical volumes for swap and / (I used btrfs, probably irrelevant) 6: finish remaining installer steps; find that grub install fails 7: drop into shell, per alt+f2, and chroot to /target 8: append GRUB_CRYPTODISK_ENABLE=y to /etc/default/grub 9: run grub-install /dev/sda (replace sda etc etc), then update-grub, reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062623 Title: enable grub-2.00 boot-from-luks support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1062623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062623] [NEW] enable grub-2.00 luks support
Public bug reported: (I suppose this comes too late in the release cycle to make the change, but perhaps it's simple enough:) With only minimal manual intervention, I found I could use today's Ubuntu Server 12.10 daily iso to install a system with luks+lvm and no separate /boot partition (which doesn't really have any security advantages, but it makes managing space on a smallish disk easier). If partman-crypto could manage the final 2 steps below, it would all be fully automatic. Thanks! Steps: 1: go through the default installer motions 2: in partman, choose the manual option 3: create a single, whole-disk primary partition, use it as a luks encrypted volume 4: on top of that, create an lvm physical volume 5: insert lvm logical volumes for swap and / (I used btrfs, probably irrelevant) 6: finish remaining installer steps; find that grub install fails 7: drop into shell, per alt+f2, and chroot to /target 8: append GRUB_CRYPTODISK_ENABLE=y to /etc/default/grub 9: run grub-install /dev/sda (replace sda etc etc), then update-grub, reboot ** Affects: partman-crypto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062623 Title: enable grub-2.00 luks support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/1062623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 878492] Re: Keyboard shortcut - F10 shortcut is used to show menu and this is wrong
On Tue, Feb 28, 2012 at 12:18:29AM -, Nick Rundy wrote: User has a almost maximized window and taps Alt+F5 to restore the window. But instead it maximizes. So then he's got to hit Alt+F5 again. Speaking as such a user, I'd say the cost of hitting Alt+F5 a second time, when my fingers are over those keys already, is close to zero. Oh well, I don't really care what the default shortcut will be, as long as there is a default at all... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878492 Title: Keyboard shortcut - F10 shortcut is used to show menu and this is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 877006] Re: regression: shortcut-keys can't be disabled anymore
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/877006 Title: regression: shortcut-keys can't be disabled anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/877006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 822382] Re: unchecking the Enable the menu shortkey (F10 by default) do not allow to th e midnigth commander to exit using F10 key
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/822382 Title: unchecking the Enable the menu shortkey (F10 by default) do not allow to th e midnigth commander to exit using F10 key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/822382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775435] Re: gnome-terminal under unity does not obey the enable menu shortcut setting
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775435 Title: gnome-terminal under unity does not obey the enable menu shortcut setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/775435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 766188] Re: None of the gnome-terminal keyboard shortcut settings let me use F10 for exit in mc
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/766188 Title: None of the gnome-terminal keyboard shortcut settings let me use F10 for exit in mc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/766188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750700] Re: Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750700 Title: Unity Compiz plugin captures F10 for menu even when explicitly disabled in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/750700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726639] Re: F10 is captured even if gnome-terminal setting is explictly set to not capture
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726639 Title: F10 is captured even if gnome-terminal setting is explictly set to not capture To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/726639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 722680] Re: Unexpected F10 key behaviour in GNOME terminal
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/722680 Title: Unexpected F10 key behaviour in GNOME terminal To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/722680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553864] Re: 'F10' keystroke captured by Terminal window
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553864 Title: 'F10' keystroke captured by Terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/553864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194155] Re: mc and gnome-terminal, F10 key conflict
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug is no longer a duplicate of bug 726639 F10 is captured even if gnome-terminal setting is explictly set to not capture ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/194155 Title: mc and gnome-terminal, F10 key conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mc/+bug/194155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 732249] Re: f10 keybinding of global menu conflicts with non-global-menu applications
*** This bug is a duplicate of bug 878492 *** https://bugs.launchpad.net/bugs/878492 ** This bug has been marked a duplicate of bug 878492 Keyboard shortcut - F10 shortcut is used to show menu and this is wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/732249 Title: f10 keybinding of global menu conflicts with non-global-menu applications To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/732249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878492] Re: Keyboard shortcut - F10 shortcut is used to show menu and this is wrong
With the latest packages for 12.04, the menu focus seems to have changed to Alt-F10 as proposed. It also seems though that there isn't a maximise shortcut at all anymore, is that right? (It would be fine I think to combine it into Alt-F5 as proposed above.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878492 Title: Keyboard shortcut - F10 shortcut is used to show menu and this is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782763] Re: update-manager marks updated packages as Manually installed
Confirmed: I see the same behaviour on a system that now runs 12.04 (Precise). (I believe fkrull is right that this was a problem for quite a while already, but have never paid attention to it much, as more than 9 out of 10 upgrades I run out of aptitude) Desired behaviour: update-manager would play nice with M-flags, applying them to packages it upgrades, or installs as dependencies. Workaround for now: run aptitude full-upgrade instead. ** Changed in: update-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782763 Title: update-manager marks updated packages as Manually installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/782763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 892609] Re: powernap reverts cpufreq scaling_governor setting to performance
Hi Andres, thanks for picking this up. I've been running the machine in question without powernap for a couple of weeks now, so I reinstalled it just now to answer your questions, and... I don't seem to be able to reproduce the previous problems. The scaling_governor is now ondemand as it should be, also after a reboot. Could you please display the output of: /var/run/powernap/cpu_governor.default As expected then, it has ondemand. And also check if /etc/rc3.d/S99acpi-support and exists /etc/rc3.d/S99ondemand. If not I have an idea of what might be going on. /etc/rc3.d/S99acpi-support does not exist (the package acpi-support isn't installed either), but S99ondemand does: it's a symlink to ../init.d/ondemand. Anyway, I suppose I should mark this invalid for now, and report back when/if there are issues again? Many thanks, Yung-Chin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892609 Title: powernap reverts cpufreq scaling_governor setting to performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/892609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892609] Re: powernap reverts cpufreq scaling_governor setting to performance
** Changed in: powernap (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892609 Title: powernap reverts cpufreq scaling_governor setting to performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/892609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892609] [NEW] powernap reverts cpufreq scaling_governor setting to performance
Public bug reported: After installing powernap on a Ubuntu 11.10 Server system, and possibly only after a subsequent reboot, I found the system to be running with the performance scaling_governor, which was a change from the original behaviour where the system would have the ondemand governor by default. Resetting the scaling_governor to ondemand, either via calling /etc/init.d/ondemand or by manually echoing the setting into /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor, was temporarily succesful, but after about a minute the scaling_governor would again be found set to performance. I believe the problem may be in /etc/pm/power.d/cpu_frequency, which doesn't seem to know about /etc/init.d/ondemand, but I'm afraid I don't know enough about upstart et al to suggest a good fix. Thanks for powernap, and thanks for reading! ** Affects: powernap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892609 Title: powernap reverts cpufreq scaling_governor setting to performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/892609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644825] Re: screen unpredictably crashes
*** This bug is a duplicate of bug 375625 *** https://bugs.launchpad.net/bugs/375625 I have experienced both this bug (where the client complains it can't find the master process anymore) and the bug now marked a duplicate, #375625 (where the client freezes, but indeed the master process also disappears). The comment in the other bug, https://bugs.launchpad.net/ubuntu/+source/screen/+bug/375625/comments/7 outlines steps that make that bug very reproducible for me, but I have not yet been able to actively reproduce this bug. All I know is this seems to strike when exiting vim. I guess what I'm asking is whether it's necessarily obvious that the two are duplicates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644825 Title: screen unpredictably crashes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629607] Re: hd-media images don't match latest 10.04.1 iso
Aha, great! Thank you for your patience to explain - it's much appreciated! -- hd-media images don't match latest 10.04.1 iso https://bugs.launchpad.net/bugs/629607 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 637635] [NEW] please make powernap depend on/recommend anacron
Public bug reported: Binary package hint: powernap This would seem useful to me because servers spending time sleeping will otherwise miss cron jobs. Thanks! ** Affects: powernap (Ubuntu) Importance: Undecided Status: New -- please make powernap depend on/recommend anacron https://bugs.launchpad.net/bugs/637635 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 629607] Re: hd-media images don't match latest 10.04.1 iso
** Package changed: ubuntu = debian-installer (Ubuntu) -- hd-media images don't match latest 10.04.1 iso https://bugs.launchpad.net/bugs/629607 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 571018] Re: lucid partitioner creates unusable disk space when creating software raid arrays
Just to add in case it's helpful: the same unusable entry can be seen when creating a partition in an encrypted volume. (Out of curiosity, can I ask what this space represents?) -- lucid partitioner creates unusable disk space when creating software raid arrays https://bugs.launchpad.net/bugs/571018 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 629607] [NEW] hd-media images don't match latest 10.04.1 iso
Public bug reported: I would like to request an update for the hd-media images under http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer- amd64/current/images/ to match the iso for the recent maintenance release 10.04.1 (I did manage to boot from a usb-disk with the vmlinuz / initrd.gz that are currently available there, but the installer obviously complains that it doesn't manage to load any modules) Many thanks! ** Affects: ubuntu Importance: Undecided Status: New -- hd-media images don't match latest 10.04.1 iso https://bugs.launchpad.net/bugs/629607 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 269974] Re: suspend via Fn+F1 or lid-close behave differently
I updated the description: the previous description conflated lots of different issues. (also, better late than never I guess: thanks Andres!) ** Description changed: - I just installed Ubuntu 8.04.1 with the amd64 alternate installer on a - Dell Latitude D630. It's an all-Intel version, ie X3100 graphics and - iwl3945 Wifi. All the latest updates have been installed. + Hardware: Dell Latitude D630, with X3100 graphics and iwl3945 Wifi. - Funny behaviour: when I close the lid, it smoothly goes into suspend, - and on opening the lid comes back again (great!). However, when instead - I hit Fn+F1, it takes much longer to go into suspend, then actually - seems to power down the hardware: no more blinking suspend light. So it - seems to call different scripts for these two cases! I checked in System - - Preferences - Power Management, and both for laptop lid is closed - and suspend button is pressed the setting is suspend. + Odd behaviour: when pressing the suspend button (Fn+F1), the system + hibernates, despite it being configured to suspend. On lid-close, it + does however properly suspend as expected. I checked in System - + Preferences - Power Management, and both for laptop lid is closed and + suspend button is pressed the setting is suspend. - Further info: when I try to restart the machine after the Fn+F1 way of - suspending, it cold-boots and shows grub, then refuses to mount the swap - partition - saying that this contains a valid suspend image. But it - doesn't use that image, and instead continues booting, only without the - swap space. I can then reenable the swap later using swapon - this - reinitialises the swap space. + Expected behaviour: the system ought to suspend instead of hibernate, as + specified in Preferences. - It's not important to me as I can get all the functionality I need - through lid-close, but I'd be happy and curious to investigate if you - can tell me where to look. Thanks. - - (There's also a second but probably unrelated issue - sometimes keyboard - and touchpad are not detected after resuming from lid-close. This can be - remedied by closing the lid again, sending the machine back into - suspend, then opening it once more. Not easy to replicate though and as - I said probably unrelated). + The same behaviour previously with Ubuntu 8.04, and now on 9.10. ** Description changed: Hardware: Dell Latitude D630, with X3100 graphics and iwl3945 Wifi. Odd behaviour: when pressing the suspend button (Fn+F1), the system hibernates, despite it being configured to suspend. On lid-close, it does however properly suspend as expected. I checked in System - Preferences - Power Management, and both for laptop lid is closed and suspend button is pressed the setting is suspend. Expected behaviour: the system ought to suspend instead of hibernate, as specified in Preferences. - The same behaviour previously with Ubuntu 8.04, and now on 9.10. + The same odd behaviour previously with Ubuntu 8.04, and the same on + 9.10. -- suspend via Fn+F1 or lid-close behave differently https://bugs.launchpad.net/bugs/269974 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 410933] Re: No sound in fresh jaunty install until disabling external amplifier
My findings are the same as Darxus': Using the 29 Sep daily-live i386 image, audio was not immediately audible, but Daniel's suggested alsa+modprobe commands fixed that. The model of Vaio used is a 'VGN-B1VP(E)' (as reported by lshal). Thanks Daniel! -- No sound in fresh jaunty install until disabling external amplifier https://bugs.launchpad.net/bugs/410933 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 410933] Re: No sound in fresh jaunty install until disabling external amplifier
ubu...@ubuntu:~$ lspci -nv |grep -A1 0401 00:1f.5 0401: 8086:24c5 (rev 03) Subsystem: 104d:81c5 Thanks again! -- No sound in fresh jaunty install until disabling external amplifier https://bugs.launchpad.net/bugs/410933 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 410933] Re: No sound in fresh jaunty install until disabling external amplifier
I can confirm the problem also occurs here, after a fresh install of Ubuntu 9.04 on a Vaio VGN-B1VP, and the fix works. I applied all available updates per 30 September 2009, played with the levels in alsamixer to no avail (and then restored them to their initial values), then found this mention of an External Amplifier setting (through Google). That is to say, disabling this was the only change from the default post-installation settings, and sounds could indeed be played back after the change. I think I just submitted further system details using ubuntu-bug although I don't see them on this page... -- No sound in fresh jaunty install until disabling external amplifier https://bugs.launchpad.net/bugs/410933 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 410933] Re: No sound in fresh jaunty install until disabling external amplifier
** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- No sound in fresh jaunty install until disabling external amplifier https://bugs.launchpad.net/bugs/410933 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 410933] Re: No sound in fresh jaunty install until disabling external amplifier
I'm taking the liberty to mark this bug confirmed, given that I can reproduce it on another Vaio model, and given that the same solution was also mentioned at https://wiki.ubuntu.com/LaptopTestingTeam/SonyVaioVGN-T350 (however, those wiki notes were written for 7.10 and 8.04). Desired behaviour: it would be great if this External amplifier setting was disabled by default. Not only is it rather hard to find the problem (I have no idea what the whole switch means, I just happened to see it in the wiki page!), but making the switch available in the volume-control window at all requires the user to actively select it in the Preferences window first. Thanks! -- No sound in fresh jaunty install until disabling external amplifier https://bugs.launchpad.net/bugs/410933 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 359531] Re: LVM file name maximum length is shorter than in ext3
Hi, thanks for the follow-up. So your tests suggest that ext3 long- filename support is broken in Ubuntu 9.04, while the use of encrypted LVM may or may not be influencing the problem. As 9.04 is still under development, can you add what date your install disc was from, and whether you tried to update the system to the latest state? I'll have to test this on an install of my own to be able to mark it confirmed, but am a bit pressed for time right now - hopefully someone else can pick up on this before I get to it, because this could turn out nasty as a dist-upgrade bug. -- LVM file name maximum length is shorter than in ext3 https://bugs.launchpad.net/bugs/359531 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 359531] Re: LVM file name maximum length is shorter than in ext3
Hi, you're right that ext3 has a limited filename size at 255 bytes - it depends on what character encoding you use how many characters that implies, but at most 255. In your example with only underscores and numbers I think you should be able to fit 255. It works for me. LVM is not a file system, but rather a modern partitioning model. Inside a logical volume, you would still set up a file system, like ext3. So... my first guess is that perhaps the installer selected something other than ext3 for the file system in your LVM test. Could you check what file system is in use? One quick way to do this is to look at the output of df -T (see the man page for details). -- LVM file name maximum length is shorter than in ext3 https://bugs.launchpad.net/bugs/359531 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 325343] Re: [python-gnuplot] plot() function plots only one point of data
I installed the newer package from Intrepid, available at http://packages.ubuntu.com/intrepid/python-gnuplot (all its dependencies are satisfied on 8.04, too). As far as I can tell this doesn't exhibit the one-data point bug. I'm not sure how to zoom though, so I couldn't get the module to either crash or zoom, as per your report. -- [python-gnuplot] plot() function plots only one point of data https://bugs.launchpad.net/bugs/325343 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
Re: [Bug 59695] Re: High frequency of load/unload cycles on some hard disks may shorten lifetime
On Fri, Feb 13, 2009 at 1:20 PM, Nicolò Chieffo 84ye...@gmail.com wrote: It's ok for me that my disk saves power while on battery, but I cannot understand why once the read head is unloaded, every minute it is loaded again. If the PC is idle who is causing the load cycle? There might be a process that every minute accesses the disk, which is not ok (in my opinion) Nicolò: this is not really related to the bug discussion... You might want to check out lm-profiler. Look at Bart's pages for a description: http://www.samwel.tk/laptop_mode/faq -- High frequency of load/unload cycles on some hard disks may shorten lifetime https://bugs.launchpad.net/bugs/59695 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 241331] Re: Running a non-existing command in the background causes exit
Sort of to my surprise, I managed to reproduce this. I entered does not exist at the bash prompt, and the shell exited. On opening a new Gnome terminal, I was quite surprised to find that that line made it into my bash history (which suggests it's a fairly clean exit). I had another succes with pester the system . As reported above, the shell exit does not occur every time. ** Changed in: bash (Ubuntu) Status: New = Confirmed -- Running a non-existing command in the background causes exit https://bugs.launchpad.net/bugs/241331 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 241331] Re: Running a non-existing command in the background causes exit
I had a look at the bash code that handles this, but there's so much conditional forking and all... really way over my head for now. As a guidance for setting the importance of this bug (to whomever is allowed to do that), I'd say it is of low importance. I just played around a bit in gdb, and the shell will refuse to exit when there are stopped jobs, so you won't lose work to this bug (as mentioned in my previous comment: you even keep your command history). Attached is the console output of that playing around. ** Attachment added: 241331stoppedjobs.txt http://launchpadlibrarian.net/22538071/241331stoppedjobs.txt -- Running a non-existing command in the background causes exit https://bugs.launchpad.net/bugs/241331 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 241331] Re: Running a non-existing command in the background causes exit
Sorry: clarification to the file just appended with the previous comment: I didn't type the line that says exit, it appears as a result of trying cats . This is the manifestation of the bug... -- Running a non-existing command in the background causes exit https://bugs.launchpad.net/bugs/241331 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 225130] Re: Cannot get back to a terminal after X has started
Many thanks for your answer, Trel. From your information it seems it was an nVidia driver issue. I hope you don't mind that I'll go ahead and mark this bug as invalid for bash. ** Changed in: bash (Ubuntu) Status: New = Invalid -- Cannot get back to a terminal after X has started https://bugs.launchpad.net/bugs/225130 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 225130] Re: Cannot get back to a terminal after X has started
Hello again Trel. I'm marking the bug as incomplete: could you add which hardware you are using with this (particularly the graphics hardware), and whether it's the free or non-free graphics driver? ** Changed in: nvidia-kernel-common (Ubuntu) Sourcepackagename: bash = nvidia-kernel-common Status: Invalid = Incomplete -- Cannot get back to a terminal after X has started https://bugs.launchpad.net/bugs/225130 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 327874] [NEW] Behaviour for unset HISTFILESIZE in bashrc not in accordance with man page
Public bug reported: Binary package hint: bash This is on Ubuntu 8.04.2 for amd64, with bash package version 3.2-0ubuntu18. (but in fact the problem occurs similarly on Red Hat Enterprise Linux 5.3, for example) According to man bash If HISTFILESIZE is not set, no truncation is performed. In my experience however, unsetting HISTFILESIZE in ~/,bashrc results in HISTFILESIZE being given a default value of 500, and the history file is truncated accordingly. To reproduce the bug, append the following line to ~/.bashrc: unset HISTFILESIZE Then, open a new terminal, and type echo $HISTFILESIZE This will return 500. In contrast, when we change our entry in ~/.bashrc to export HISTFILESIZE=0 when we now open a new terminal, we find HISTFILESIZE is indeed set to 0. Summary: effectively we can't unset this value in .bashrc, and the man page suggests otherwise. Desired behaviour: leave the history untruncated if we unset HISTFILESIZE in .bashrc. PS, for completeness: I'm also using the setting shopt -s histappend in .bashrc. As the man page specifies, this only results in the history being truncated on starting a new bash rather than on closing the old one. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- Behaviour for unset HISTFILESIZE in bashrc not in accordance with man page https://bugs.launchpad.net/bugs/327874 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 225130] Re: Cannot get back to a terminal after X has started
This is most likely not a bug in bash, but rather in the video driver, which doesn't allow switching between X and the consoles. Can you supply information on your brand of graphics hardware and the drivers used? Please then mark this as a bug against the relevant xserver-xorg package, and mark it as invalid for bash. Thanks. (To proof that it's not a bash issue: open an xterminal) -- Cannot get back to a terminal after X has started https://bugs.launchpad.net/bugs/225130 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 327874] Re: Behaviour for unset HISTFILESIZE in bashrc not in accordance with man page
I'm sorry for the noise. I was just looking at various versions of the bash source, and the described behaviour has been this way at least back until version 2.05 or so, so it is not reasonable to change this. Instead, I'll try to come up with a rewording of the man page info. Assigned to me and marked invalid. ** Changed in: bash (Ubuntu) Assignee: (unassigned) = Yung-Chin Oei (patsoe) Status: New = Invalid -- Behaviour for unset HISTFILESIZE in bashrc not in accordance with man page https://bugs.launchpad.net/bugs/327874 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 258383] Re: SLIME looks for wrong lisp by default
I can confirm this bug on a clean Ubuntu 8.04.2 amd64 (ie I never installed slime or even emacs on it before), and adding the proposed line to ~/.emacs is indeed a working solution. ** Changed in: slime (Ubuntu) Status: New = Confirmed -- SLIME looks for wrong lisp by default https://bugs.launchpad.net/bugs/258383 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 310213] Re: README.debian does not explain how to activate vimoutliner addon
I ran into the same surprise trying to install the addon on Ubuntu 8.04. I believe the fix suggested by Chris Schoonbee is perfectly in accordance with the cited Debian policy. The issue also affects Debian Unstable as well as Testing: neither declare a Recommend: vim-addon- manager ** Changed in: vimoutliner (Ubuntu) Status: New = Confirmed -- README.debian does not explain how to activate vimoutliner addon https://bugs.launchpad.net/bugs/310213 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 310213] Re: README.debian does not explain how to activate vimoutliner addon
The related Debian bug is http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=435704 (I can't figure out how to set the association in Launchpad). ** Also affects: vimoutliner (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435704 Importance: Unknown Status: Unknown -- README.debian does not explain how to activate vimoutliner addon https://bugs.launchpad.net/bugs/310213 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 158385] Re: addons path wrong in debian.vim
The original bug as reported by Daniel White concerns the absence of a registry file, and was fixed for Hardy, see https://launchpad.net/ubuntu/jaunty/+source/vimoutliner/0.3.4-8 - however, the problem still encountered by gravies and Daniel Chen is described in this other bug report: https://bugs.launchpad.net/ubuntu/+source/vimoutliner/+bug/310213 I guess the cleanest option is to close this bug, but please tell me off if this is bad practice. ** Changed in: vimoutliner (Ubuntu) Status: Incomplete = Fix Released -- 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 subscribed to 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
Oops, I linked a Jaunty page when I meant https://launchpad.net/ubuntu/hardy/+source/vimoutliner/0.3.4-8 but of course the package is the same. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 233942] Re: genisoimage generates wrong DVD-Video images
Without upgrading 8.04 to 8.10, the issue can also be resolved by upgrading only the genisoimage package. This only involved installing the binary package shipped in 8.10. After doing that I was able to produce an iso that is WinXP-readable. -- genisoimage generates wrong DVD-Video images https://bugs.launchpad.net/bugs/233942 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 269974] Re: suspend via Fn+F1 or lid-close behave differently
Further info, update: I get the same behaviour as I get with Fn+F1 when I choose hibernate from the quit-menu, so I guess that that's related. I believe the problem with resuming from hibernation is that the disk volume layout on my system, which consists of an LVM partition with several separately encrypted logical volumes, is something the resume- scripts weren't designed to deal with, so that's actually a separate bug (how do I deal with that? I'm relatively new to bug reporting). -- suspend via Fn+F1 or lid-close behave differently https://bugs.launchpad.net/bugs/269974 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 269974] [NEW] suspend via Fn+F1 or lid-close behave differently
Public bug reported: I just installed Ubuntu 8.04.1 with the amd64 alternate installer on a Dell Latitude D630. It's an all-Intel version, ie X3100 graphics and iwl3945 Wifi. All the latest updates have been installed. Funny behaviour: when I close the lid, it smoothly goes into suspend, and on opening the lid comes back again (great!). However, when instead I hit Fn+F1, it takes much longer to go into suspend, then actually seems to power down the hardware: no more blinking suspend light. So it seems to call different scripts for these two cases! I checked in System - Preferences - Power Management, and both for laptop lid is closed and suspend button is pressed the setting is suspend. Further info: when I try to restart the machine after the Fn+F1 way of suspending, it cold-boots and shows grub, then refuses to mount the swap partition - saying that this contains a valid suspend image. But it doesn't use that image, and instead continues booting, only without the swap space. I can then reenable the swap later using swapon - this reinitialises the swap space. It's not important to me as I can get all the functionality I need through lid-close, but I'd be happy and curious to investigate if you can tell me where to look. Thanks. (There's also a second but probably unrelated issue - sometimes keyboard and touchpad are not detected after resuming from lid-close. This can be remedied by closing the lid again, sending the machine back into suspend, then opening it once more. Not easy to replicate though and as I said probably unrelated). ** Affects: ubuntu Importance: Undecided Status: New -- suspend via Fn+F1 or lid-close behave differently https://bugs.launchpad.net/bugs/269974 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 204326] Re: nm-applet 0.6.6 does not show any wireless networks
*** This bug is a duplicate of bug 188282 *** https://bugs.launchpad.net/bugs/188282 This does not seem to be a duplicate of bug #188282. That bug report is about the b43 driver breaking the installer. This bug report is about a post-install problem. -- nm-applet 0.6.6 does not show any wireless networks https://bugs.launchpad.net/bugs/204326 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 48758] Re: [Ubuntu 6.06] couldn't find RGB GLX visual (not driver-specific)
See my comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-vesa/+bug/48758/comments/7 ** Changed in: xserver-xorg-video-vesa (Ubuntu) Status: Incomplete = Fix Released -- [Ubuntu 6.06] couldn't find RGB GLX visual (not driver-specific) https://bugs.launchpad.net/bugs/48758 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
Re: [Bug 48758] Re: [Ubuntu 6.06] couldn't find RGB GLX visual (not driver-specific)
Thanks for the update. I'm afraid I don't have the Ubuntu system handy anymore to test on, but when I upgraded to 7.04 last August the problem was gone. I realise that's not very much information, apologies for that! I looked at the bug you mention, but that sounds like a different problem to me (I didn't have any trouble just running X, only when I wanted to run some OpenGL apps things appeared broken). Thanks! On Jan 13, 2008 11:49 AM, Timo Aaltonen [EMAIL PROTECTED] wrote: DRI should be disabled by default if you use the ati driver, and on launchpad the bug is bug #163432. Please try 7.10 or Hardy alpha3 if vesa works better now. ** Changed in: xserver-xorg-video-vesa (Ubuntu) Sourcepackagename: xorg = xserver-xorg-video-vesa Status: New = Incomplete -- [Ubuntu 6.06] couldn't find RGB GLX visual (not driver-specific) https://bugs.launchpad.net/bugs/48758 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 110011] Re: Feisty ipython segfaults on import tab
The suggested fix works well here - although I didn't do %upgrade (I hadn't picked up that part) but rather just commented out the line in ~/.ipython/ipy_user_conf.py Thanks! -- Feisty ipython segfaults on import tab https://bugs.launchpad.net/bugs/110011 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 49559] Re: connected USB mouse prevents resume from suspend-to-RAM
The problem disappeared this week - I don't know exactly after which changes, I only found out by accident, when I forgot to unplug my mouse and the machine nevertheless resumed just fine! There was an update to acpi-support which I didn't pay too much attention to at the time, but supposedly that fixed it. Thanks! (I'd like to change the status of the bug - but there's no option to do that, so I'll just edit the original description). ** Description changed: - After a suspend-to-RAM, the machine fails to resume whenever I have my - USB mouse (MS Intellimouse Optical 1.1A) connected. The hard drive spins - up, the mouse light switches on and off two or three times, then - nothing. No reaction to any key combinations, no disk activity. + [edit/update:] Problem seems to have been resolved with updated acpi- + support. + + + After a suspend-to-RAM, the machine fails to resume whenever I have my USB mouse (MS Intellimouse Optical 1.1A) connected. The hard drive spins up, the mouse light switches on and off two or three times, then nothing. No reaction to any key combinations, no disk activity. Removing the mouse before resuming takes away the problem (that is, it is irrelevant whether the mouse is plugged in at suspend time). Please tell me how to provide you with relevant information. Thank you. Ubuntu version 6.06 (final) amd64. Machine is a HP Compaq nx6125 PY416EA (Turion64 ML-34, Radeon Xpress 200M chipset). -- connected USB mouse prevents resume from suspend-to-RAM https://launchpad.net/bugs/49559 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
