[Bug 490729] [NEW] KMail keeps checking disabled account in an endless loop until I kill kontact from a console
Public bug reported:
Binary package hint: kdepim
1) Kubuntu Karmic:
Description:Ubuntu 9.10
Release:9.10
2) kontact:
Installed: 4:4.3.2-0ubuntu6
Candidate: 4:4.3.2-0ubuntu6
Version table:
*** 4:4.3.2-0ubuntu6 0
500 http://ftp-stud.fht-esslingen.de karmic/main Packages
100 /var/lib/dpkg/status
3) When disabling email checks on an account, I would expect not to have
checks happen on that account.
4) I have a DIAMP account at GMail which I've currently disabled (both
e-mail check options unchecked in settings) as the bandwidth limit has
been exceeded.
However, KMail still tries to check this account for new mail ("Checking
account DIMAP danielb...@gmail.com for new mail" in the status bar),
which fails, then it prompts for credentials, which won't help, which
reprompts, which... You get the picture ;)
I'm unable to stop this behavior in any other way than kill it from a
console as the prompts just reappear every time I cancel them.
** Affects: kdepim (Ubuntu)
Importance: Undecided
Status: New
--
KMail keeps checking disabled account in an endless loop until I kill kontact
from a console
https://bugs.launchpad.net/bugs/490729
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 1750645] Re: 18.04 Server installation missing partition options
I know I probably shouldn't join the negativity train here, but... OMG, why? The usual installer is the best I've ever used in my 18 years of Linuxing. This new one is just broken beyond belief. Why is it here? A few weeks ago, I had to give up on installing Ubuntu Server 18.04 on a machine without internet because, hey — the new installer won't let you install without internet. Now, I'm trying to install on another server with internet, but hey, the installer doesn't see the existing partitions. How on Earth does this level of broken software get into an LTS release, let alone *any* release? I mean Debian-style conservatism is tiring, and Ubuntu is deliciously free of this, but hey — there's gotta be a limit somewhere :) I don't understand how it's now June, and the online images still have this broken new installer bundled. Again, why? Why is it here? :D Sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750645 Title: 18.04 Server installation missing partition options To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1750645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1474534] Re: Screen Energy Saving and Dim Screen do not work reliably
Well, to be fair, this is beta software, and the disclaimer is "do not use for work or production," right? I mean, that's what it was in 2000, when I used it first, and it's only gotten more beta since then, so clearly, this is expected behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1474534 Title: Screen Energy Saving and Dim Screen do not work reliably To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1474534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-v3.11 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] [NEW] Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
Public bug reported: I just updated my box from Oneiric to Precise (linux- generic-3.2.0.23.25). The box has 22 SATA drives, 6 on ICH10R 15 on three sata_sil24 PCIe 1-port cards using three 1:5 PMPs 1 on a sata_sil PCI32 4-port card After upgrading, two things are apparent: 1) GRUB hangs for quite a long time upon booting, but eventually continues. dmesg (attached) mentions a whole lot of hard resetting of my sata_sil24 devices until finally continuing. 2) Random SATA drives attached to the sata_sil24 will be missing. dmesg attached, other output to follow. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia zfs zcommon znvpair zavl zunicode AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 2627 F pulseaudio /dev/snd/controlC1: daniel 2627 F pulseaudio /dev/snd/controlC0: daniel 2627 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfaef8000 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,18490888,0011' Controls : 37 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfebfc000 irq 17' Mixer name : 'Nvidia GPU 1c HDMI/DP' Components : 'HDA:10de001c,104383a0,00100100' Controls : 12 Simple ctrls : 2 Card2.Amixer.info: Card hw:2 'NVidia_1'/'HDA NVidia at 0xfcbfc000 irq 23' Mixer name : 'Nvidia GPU 1c HDMI/DP' Components : 'HDA:10de001c,19da1228,00100100' Controls : 12 Simple ctrls : 2 Date: Mon Apr 23 17:00:48 2012 HibernationDevice: RESUME=UUID=ad3d1ee7-2108-47b0-b764-a1ec42898ba2 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US:en TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.2.0-23-generic root=UUID=aa16e554-8ba2-4537-8bc6-a2c37f160369 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.10 dmi.board.name: P43Twins1600 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd12/01/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP43Twins1600:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel pmp precise sata sata-sil24 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/987353/+attachment/3100148/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+attachment/3100175/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
FYI: Hot-unplugging and re-plugging the affected drives properly presents them to the system, and I can then use them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+attachment/3100174/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
I will try different kernels promptly. Btw, I wasn't perfectly clear in my phrasing (sorry): By "updated my box from Oneiric to Precise" I didn't mean a dist upgrade, I meant a wipe of Oneiric and fresh install of Precise daily. Just to clear that up :) Will report back with results on other kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
Just tried the 3.4.0-030400rc4-generic from http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.4-rc4-precise/, same problem. I'll try an Oneiric one now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
Installed 3.0.0-17-generic for Oneiric, GRUB now goes happily and immediately from its selection screen to the Kubuntu loading logo, and all drives are present at boot (which is a LOT faster, now that the link resets aren't triggered anymore). Is there anything I should attach or report about in this configuration? Also, is it "safe" to use this build for the time being until the issue with 3.2+ is resolved? (e.g. I had to force install as I couldn't immediately satisfy a wireless-crda package dependency (and I don't use wireless on this box)). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987353] Re: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot
Thanks for your time and help, I've created a kernel bug report (#43153) here: https://bugzilla.kernel.org/show_bug.cgi?id=43153 ** Bug watch added: Linux Kernel Bug Tracker #43153 http://bugzilla.kernel.org/show_bug.cgi?id=43153 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987353 Title: Random SATA drives on PMPs on sata_sil24 cards not being detected at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465761] [NEW] Multiverse ec2-api-tools broken in Trusty
Public bug reported: Hi :) The ec2-api-tools version that's in the multiverse repository for Ubuntu seems to predate Amazon's latest data center in Germany, eu-central-1. I can't say if there are other issues with this version, but at least authentication attempts with the eu-central-1 region will fail. Using the version from the Utopic repository, 1.6.14.1-0ubuntu1, works just fine. ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: aws ec2 multiverse trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465761 Title: Multiverse ec2-api-tools broken in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1465761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 868970] Re: User should be able to disable Akonaditray when akonadi/nepomuk is not used
I can confirm that the hack in #3 doesn't work. Rather than having to re-hack system files after each update, and given that we're not allowed to uninstall akonadi, what I've done is simply to create a small bash script, #!/bin/bash sleep 10s && killall -9 akonaditray And added it to the scripts to run on startup. Not pretty, but it works. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim-runtime in Ubuntu. https://bugs.launchpad.net/bugs/868970 Title: User should be able to disable Akonaditray when akonadi/nepomuk is not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim-runtime/+bug/868970/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1007752] [NEW] Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Public bug reported: Hello :) The recent update (today) of grub, grub-pc:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1) grub-pc-bin:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1) grub-common:amd64 (1.99-21ubuntu3, 1.99-21ubuntu3.1) killed my grub, apart from also looking strange (used to be gray background, and a nice logo splash when booting, now black background and just low-res text when booting). The BOOT_IMAGE command defined root as - in my case - /dev/sdq2, while at boot it would be /dev/sdb2. Also, this might not stay the same regardless, and as I understand it, this should point to either a partition UUID or perhaps /dev/disk/by-id/something-or-other? In any event, as it stands, all boot options ends with busybox and an initramfs prompt. Editing the grub command and fixing the root= to the right path before booting will send me normally into Kubuntu where I can (hopefully) fix the problem manually. Cheerio :) Daniel ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 NonfreeKernelModules: nvidia zfs zcommon znvpair zavl zunicode ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 2 10:44:50 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421.1) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts grub kubuntu precise third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Sorry for being unclear. With BOOT_IMAGE, I was referring to the output of cat /proc/cmdline, e.g. BOOT_IMAGE=/@/boot/vmlinuz-3.0.0-17-generic root=/dev/sdq2 ro rootflags=subvol=@ quiet splash vt.handoff=7. Above is what grub creates on my system with this is /etc/default/grub: # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true So either GRUB_DISABLE_LINUX_UUID is now defaulting to true, or something else is going on. Actually, it seems allright in the generated /boot/grub/grub.cfg (see attached). I do note, however, the "set root='(hd16,msdos2)'" bit in grub.cfg. This corresponds exactly to sdq2 with hd0 being sda. It wasn't in grub.cfg I saw the "root=sdq2", as at that point I wasn't able to boot the system (root drive being sda), it was when editing the command line in the GRUB interface. This may be a wildly inaccurate bug report in that this behavior may either be the default(?) or it may be much older than the most recent update. It just happend to coincide with me doing hard drive fiddling and updates to GRUB rolling in. ** Attachment added: "Generated grub.cfg" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+attachment/3174567/+files/grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742041] Re: autocompletion fails to work entirely for some commands (e.g. mount)
As the bug continues to exist with Precise, maybe it's time to actually assign this to someone, perhaps give it some importance? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742041 Title: autocompletion fails to work entirely for some commands (e.g. mount) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/742041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742041] Re: autocompletion fails to work entirely for some commands (e.g. mount)
FWIW, the fix is apparently quite trivial: http://ubuntuforums.org/showthread.php?t=1769100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742041 Title: autocompletion fails to work entirely for some commands (e.g. mount) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/742041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Hi, sorry for the very long delay (holiday! yay!) :) Returning this weekend, I decided to get rid of my secondary NVIDIA card and use this box solely as an HTPC machine (at least GUI-wise, it's still a server otherwise ;) ). Tons of updates, and I removed my SII3114 PCI card and replaced it with a PCIe-based 3132 one now that I had the vacant PCIe slot. During this, a lot of drives changed ports, including the system one. No problems occurred. So, I cannot say if this was due to an upgrade, if my problem was just some weird cosmic ray hitting me, or what, but there's no problem anymore. Sorry to keep you busy, and thanks for everything. I'm marking this invalid. Cheers, Daniel ** Changed in: grub2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048819] [NEW] Dolphin doesn't reflect changes made in details mode
Public bug reported: Open dolphin. Right-click and select new folder. Name it something, like "test". Right-click created folder and select to create a new (sub)folder. Name it something. Notice how there's now no indication that test has a subfolder. Won't happen until exiting dolphin and reopening it, or pressing F5. ** Affects: dolphin (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/1048819 Title: Dolphin doesn't reflect changes made in details mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1048819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048819] Re: Dolphin doesn't reflect changes made in details mode
Same goes for copying anything into a folder, the display won't reflect the change until you restart dolphin or refresh the display, even though dolphin was the one doing it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048819 Title: Dolphin doesn't reflect changes made in details mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1048819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970260] Re: Setting up memtest86+ hangs because of "grub-probe: error: unknown filesystem"
In my case, grub was trying to mount an eSATA connected NTFS drive and hanging there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970260 Title: Setting up memtest86+ hangs because of "grub-probe: error: unknown filesystem" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/970260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037063] [NEW] Cannot safely remove USB devices. Changes are not written (completely) before being ejected.
Public bug reported: This has happened several times over a longer period of time with several versions of Kubuntu on several pieces of hardware. I'll attach some USB device, choose to open it with Dolphin, make some changes, safely remove it, and then on next mount, the files I'd written either weren't there, or the filesystem has been totally trashed. I just experienced this. I need to fire up a live stick on another rig to do some data checking on a harddrive, and needed some scripts and apps to go with it. I put in the live stick on my desktop box, mounted it, wrote the files, safely removed it. Actually, that's not entirely true, before *and* after safely removing it, I did `sudo sync` and `echo 3 | sudo tee /proc/sys/vm/drop_caches > /dev/null` in the hopes of avoiding this exact scenario. I then re-mounted it to make sure the files were still there (without physically removing the stick). Only the folder I had created was still there, the files inside were not. I then copied the files again, repeated the whole thing, and upon remounting, the folder was now gone. At least to Dolphin. In a terminal, I get, d? ? ? ? ?? par2/ on the folder. I'm now assuming the filesystem on the stick is broken, and preparing to recreate my live stick. This is not only frustrating, it can also be seriously devastating when important files are lost. Which happened to me not so long ago, where I foolishly trusted Kubuntu with my USB stick for a brief backup as I had to wipe a laptop's harddrive. The issue seems to be worse with vfat devices, either because it's more prone to happen there or simply because fat doesn't use journaling and therefore easily get completely trashed because of this bug. ** Affects: linux (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/1037063 Title: Cannot safely remove USB devices. Changes are not written (completely) before being ejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1037063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037063] Re: Cannot safely remove USB devices. Changes are not written (completely) before being ejected.
I can confirm that the stick in question was indeed trashed. I created a new one. Copied my files to an ext4 one with manual mount -o sync, and had no problems. Perhaps it just is vfat. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037063 Title: Cannot safely remove USB devices. Changes are not written (completely) before being ejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1037063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99437] Re: umount: mount disagrees with the fstab
It is now almost six years later since the original bug report (#71609) was filed, and Precise still has this bug (sshfs). The workaround described in post #22 (which I believe stems from here: http://www.unicom.com/blog/entry/651) may work for umount, but it breaks pubkey authentication on mount (I'm prompted for my password even though I have working file-based authentication). I was under the impression that this was a trivial one-liner bugfix? Why is this still unsolved after six years with a working fix having been released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/99437 Title: umount: mount disagrees with the fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/99437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Well, it was exactly doing 'e' in GRUB that revealed the problem it first. This is also where I manually edited it at the time from sdq2 to sdb2 (IIRC) to be able to boot. Sorry if I'm unclear in my explanations. Bottomline: hitting 'e' shows sdq2. The only place I can see in the grub cfg that doesn't use a UUID is the "set root='(hd16,msdos2)'" part I noted earlier. And after an update- grub, it's all still the same. Your /proc/cmdline shows a UUID for root? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Well, since it's the root fs, I can't mount it twice, but I already have the btrfs root volume set up in fstab to be mounted in /mnt/btrfs, so it looks like this: daniel@lnxsrv:~$ sudo mount /mnt/btrfs daniel@lnxsrv:~$ ls /mnt/btrfs/@/boot/ abi-3.0.0-17-generic config-3.2.0-24-generic initrd.img-3.2.0 memtest86+_multiboot.bin vmcoreinfo-3.0.0-17-generic abi-3.2.0-24-generic grub initrd.img-3.2.0-24-generic System.map-3.0.0-17-generic vmlinuz-3.0.0-17-generic config-3.0.0-17-generic initrd.img-3.0.0-17-generic memtest86+.bin System.map-3.2.0-24-generic vmlinuz-3.2.0-24-generic FYI, in fstab: UUID=aa16e554-8ba2-4537-8bc6-a2c37f160369 /mnt/btrfs btrfs defaults,noatime,noauto,ssd,subvolid=0 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Could me being with kernel 3.0 still have anything to do with it? (Don't see why personally, but then again, there's a lot of things I don't know ;) ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
It's weird, I just installed Ubuntu in a VM on my Air, and it doesn't show this at all. It uses UUID just fine. Exact same GRUB version. It can't be the sheer number of drives in my desktop triggering it? Like if your root volume is on drive > 16... Doesn't make sense, though :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Ah, that's why you asked. I thought it was a typo, as there's only @ and @home, and snapshots thereof: drwxr-xr-x 1 root root 302 Jun 2 12:36 @/ drwxr-xr-x 1 root root 204 Apr 23 13:35 @-2012-04-23.1438/ drwxr-xr-x 1 root root 218 Apr 23 14:44 @-2012-04-23.1553-manual/ drwxr-xr-x 1 root root 252 Apr 23 16:12 @-2012-04-23.1719-zfs/ drwxr-xr-x 1 root root 252 Apr 23 16:12 @-2012-04-23.1742-nvidia-and-messages-logging/ drwxr-xr-x 1 root root 252 Apr 23 23:03 @-2012-04-24.0010-misc/ drwxr-xr-x 1 root root 252 Apr 23 23:03 @-2012-04-24.1904-misc/ drwxr-xr-x 1 root root 302 May 6 10:30 @-2012-05-20.1731/ drwxr-xr-x 1 root root 302 May 6 10:30 @-2012-05-28.0926/ drwxr-xr-x 1 root root 46 Apr 25 12:13 @home/ drwxr-xr-x 1 root root 32 Apr 23 13:00 @home-2012-04-23.1442-initial-not-yet-logged-in/ drwxr-xr-x 1 root root 46 Apr 24 10:47 @home-2012-04-24.1904-misc/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Attached. /proc/cmdline shows sdq2 (which IS correct — though only as long as I don't add or remove drives, swap cables, USB HDDs, etc. :) ) ** Attachment added: "RESULTS.txt" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+attachment/3175979/+files/RESULTS.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
There you go :) ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+attachment/3176446/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
Yes, but it's the most recent boot. I won't be able to reboot before in about four days (jobs running), but I can assure you nothing has changed since then so it'll boot the same :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007752] Re: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot
FWIW, prior to that boot I redid update-grub and update-initramfs in the hops it'd "fix" something. Everything stayed the same. Just to make sure we're on the same page: /dev/sdq2 *IS* my root partition (normally, and right now). It's not that sdq2 was fetched out of thin air. On my MacBook Air with a freshly installed Kubuntu 12.04, the behavior is the same, although here root=/dev/mapper/sda6_crypt, both in GRUB itself and /proc/cmdline. I don't mean to sound wise-assy, but did you try cat'ing /proc/cmdline on your own install? Or hitting 'e' in GRUB to see what root= says there? Cheers :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007752 Title: Most recent grub update uses root=/dev/sdX for boot image, may fail to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1007752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97322] Re: rtl8187 module has no ad-hoc support
Still no donut in Oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/97322 Title: rtl8187 module has no ad-hoc support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/97322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742041] Re: autocompletion fails to work entirely for some commands (e.g. mount)
I'd like to point to the *original* poster's (i.e. Ngassam's) description of the issue. 769866 is not the same issue. The issue at hand here is that some commands (e.g. the mount command) fail autocompletion when prefixed with sudo. Using "mount" as regular user will autocomplete on tabbing in order to find source device and mount target folder paths. Same applies if logged in as root. When prefixing "sudo" tab path autocompletion stops working. This applies to Oneiric and Natty, in X sessions, TTYs and SSH. Not sure if it applied to Maverick -- AFAIR it didn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742041 Title: autocompletion fails to work entirely for some commands (e.g. mount) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/742041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774089] Re: Booting fails 3 times, works every fourth time after new install of Natty Narwhal amd64 on Macbook Pro
So... It's been a month since anyone posted on this bug. Any reason the status hasn't changed? Having ordered an Air, I'm quite interested in knowing if this bug has been solved or not? So far, 11.04 has been the worst 'buntu release yet - works improperly or not at all on all of the systems I've installed it to. Are the new "Mac" images that are available for download safe to use with a fix for this bug? And if so, why isn't this bug closed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774089 Title: Booting fails 3 times, works every fourth time after new install of Natty Narwhal amd64 on Macbook Pro To manage notifications about this bug go to: https://bugs.launchpad.net/efibootmgr/+bug/774089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/R500/W700/X60/T6x suspend fails
Changes for me with the new 2.6.38-3 kernel that was uploaded to the kernel ppa earlier today: Resume after suspend now doesn't go directly to POST, but gives "old" behavior where X and TTY hangs instead. Hibernate now works! This will have to be my workaround for sleeping when on battery until the issue is completely fixed. With an SSD, this isn't that bad, but would probably suck with a 5400 rpm spinning platter ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/R500/W700/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails
Did any of these patches that are suspected of causing this go into the 2.6.38 branch as well? I've just bought an SSD for my laptop and installed Kubuntu Maverick. Before I was using Mint 9 KDE, with which my hotkeys (volume, brightness, etc.) worked fine. With Maverick, even with dist-upgrade, they did not. I then used the Ubuntu kernel PPA for Lucid to install the 2.6.38-27~lucid generic image, and all buttons work, even my touchpad is properly recognized and customizable, which is a first for Linux on this laptop. Susend/resume, however, results in a hard lock on resume. I can usually either get a flash of the X session, or get the mouse cursor to hover over a TTY by (Ctrl+)Alt+Fx'ing around, but it's always "dead" and requires a hard shutdown. No blind-typing possible and power button does not trigger the ACPI shutdown (or how you put it) that it usually does. I tried the latest natty version, 2.6.38-1.28, and the issue is the same. I also just re-reinstalled as I decided to use Btrfs instead of ext4, but as you'd expect that didn't change anything. The reason I'm mentioning this last thing is because I'm currently looking at what looks like a kernel oops, and it's mentioning btrfs, kernel BUG at /build/buildd/linux-2.6.38/fs/btrfs/disk-io.c:2344! The fact that this is the first line after the [ cut here ] one might suggest it is IO-centric? I don't know. I'm gonna photograph the display in case anyone wants to see it :) FTR, I opted to encrypt my home dir when installing, which also meant I have swap on cryptoloop, apparently. Don't know if this matters, just saying ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails
Well, I only use the kernel from Natty, and I experience failure to resume. I'll download Natty now and install it to check it out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails
Just booted into the latest Natty daily build using the livecd. As far as my issue is concerned, this release has fixed whatever the problem was. It suspends and resumes without any problems. Which is funky as the kernel is the exact same that I downloaded for Maverick. Or maybe that's the cause of the problem in the first place ;) And on an unrelated sidenote, and so sorry to put this in here, but I just have to vent this after having seen the upcoming Natty for the first time: This is not the Ubuntu I'm used to. What the h*** just happened to Ubuntu & Gnome? They look f***ing awesome!!! I think I'm gonna have to switch from Kubuntu to Ubuntu on my laptop now Wow... :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails
Back again. Problem *not* solved after all with the latest daily Natty. The *live cd* suspends and resumes correctly, but as I just found out opening my laptop which has been asleep all night, the installed system does not. Black screens for TTYs and X. Blind-typing in TTYs not possible. I can Alt+F7 my way back to X from the black TTYs, and here I can move a mouse cursor around on a black X screen. Power button does not trigger ACPI shutdown, and I must power off the system. Now I'm back to hinting at the mentioning of the FS in the kernel oops I saw on my previous Kubuntu installation. Because the livecd does not live on a regular fs, it lives on cd + unionfs in mem, right? The kernel oops stated that the origin for the panic was in the fs code. While the Kubuntu installation had an encrypted swap and lived on btrfs, this Ubuntu installation has unencrypted swap and lives on ext4 (because GRUB wouldn't boot after installing / on btrfs (/boot on ext3)). So while this probably means that it *isn't* a problem with fs code, might it be that whatever the system is trying to do at that point, fs-wise, is the culprit? Like, which filesystem operations run when you resume after suspend? I'd look there if it were me, anyway ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
Latest 2.6.38-4 kernel from the kernel PPA shows regression compared to the -3 kernel. Suspend just crashes the system (black screen, fans at full throttle), and also none of the special function keys (brightness, volume, etc.) work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
tully's comment #151 hints at the same thing I hinted at in #103 - did anyone ever look into this? i.e. the problem being swap or other fs related? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
These issues reek of serious ACPI trouble with the recent kernels. I'm also on the Ubuntu on MacBook discussion list, and here brightness keys stopped working with Natty: http://ubuntuforums.org/showthread.php?t=1603365&page=31#308 Same thing on my laptop - I'm also missing /var/log/messages now (don't even know how that's possible and if that's related). My desktop (i7 920 on ASUS RoG II GENE) kernel panics if booted without noacpi nolapic. I'm starting to believe that the ACPI code in the 2.6.38 kernels may be seriously flawed, and that the kernel team has some massive work to do before any of us see all of our issues resolved - and I fear that the Ubuntu team can's do a whole lot... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
Also reproducible on Lubuntu 11.04 in lxterm. Switching back and forth between a TTY (which will be just a black screen) and X coated with a little patience sugar will bring back interaction (just did it while writing this). Don't know if this is due to lxdm being more stable than gdm and kdm, or just my luck, but that's how it "works" in LXDE :) Doesn't seem to happen with other windows, though (Chromium or File Manager, although the latter may a resize corner that won't function). Strange that it's terminal related, across gnome-terminal, konsole, and lxterm...?!?!?! Gonna try Szymon's workaround, thanks for that! Hopefully the nvidia folks will have a proper fix soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736743] Re: environment block not implemented on btrfs
With the risk of sound like another "me too, waa waa", I just want to
ask a question based on the piece of info in #5 ("and so we could use
1KB of it for an environment block") compared to the piece of info on
https://help.ubuntu.com/community/btrfs ("take care to keep about 1 Mib
space free at the beginning of the disk").
Will doing this (keeping a meg free at the beginning of the disk) work
around this semi-error? I forgot to do so when installing, and while it
installed just fine, I ended up with this error message at boot. Just
want to know if re-installing with a bit of space reserved in the
beginning would help.
Sorry if I'm butting in where I should keep quiet :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736743
Title:
environment block not implemented on btrfs
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736743] Re: environment block not implemented on btrfs
Nevermind, on closer inspection, my disk has exactly 1 MB free at the beginning, as it's been partitioned with ubiquity and therefore follows the best-practice of 4k properly aligned sectors. So to answer my own question: No, this does not change this particular issue - these two things are not related :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736743 Title: environment block not implemented on btrfs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784125] [NEW] btrfsctl -s exits with code 1 on a successful operation
Public bug reported: Binary package hint: btrfs-tools I wrote a small script to automate snapshotting of my volumes, and discovered that even on success, btrfsctl -s will exit with 1, rather than 0. It also exits with 1 on errors. ** Affects: btrfs-tools (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/784125 Title: btrfsctl -s exits with code 1 on a successful operation -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736743] Re: environment block not implemented on btrfs
As Colin pointed out in #8, there's no need to add any more confirmations and "me too"s - the bug is known and being attended too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736743 Title: environment block not implemented on btrfs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741223] Re: Natty: Unable to adjust brightness for Acer Aspire 5731, requires reboot to reflect change
One thing that's disturbing here is that sometimes when I boot, I get a short glance of some ACPI and other things severely failing. I also have the odd behavior that if I use the brightness up and down keys shortly after grub, while the splash is showing, they work and continue to work throughout my entire session. If I don't use the brightness keys until in X, they do not work 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/741223 Title: Natty: Unable to adjust brightness for Acer Aspire 5731, requires reboot to reflect change -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741223] Re: Natty: Unable to adjust brightness for Acer Aspire 5731, requires reboot to reflect change
Not sure if this is related, but I've been fetching kernels from the Ubuntu Kernel PPA before previewing Ubuntu Netbook and later Kubuntu Natty on my ASUS UL30A. The 2.6.38 kernels have had broken suspend/resume from the get-go, but versions since -4 have also had various degrees of broken Fn keys, i.e. broken ACPI support for my model. 2.6.38-3 works with Fn keys, 2.6.38-4 and up to the current -8 do not. ATM, with -8, the broken keys are isolated to brightness up/down which, with acpi_listen running, will be logged *extremely slowly* (like once every 20 or 30 seconds) and block the queue for any other buttons being pressed (like sound up/down). Also, no KDE overlays will be shown for the brightness keys, and no change in brightness will take place. Here's me pressing keys: daniel@daniel:~$ acpi_listen video LCDD 0086 video LCDD 0087 video LCDD 0086 video LCDD 0087 hotkey ATKD 0030 hotkey ATKD 0031 hotkey ATKD 0030 0001 hotkey ATKD 0031 0001 hotkey ATKD 0030 0002 hotkey ATKD 0031 0002 hotkey ATKD 0031 0003 ... The first ones are the brightness keys (took well over a minute for those four lines to appear), the rest are volume keys. I don't know if it's related to suspend/resume not working, but the issues arose simultaneously, and both are ACPI stuff, so I'm guessing they are :) Also, if this is unrelated to the OT, I'll back off :) Let me know if I can supply any useful output from somewhere. If nothing else, I think these might be of interest: daniel@daniel:~$ dmesg | grep -i asus [0.00] DMI: ASUSTeK Computer Inc. UL30A /UL30A , BIOS 212 12/28/2009 [0.00] ACPI: XSDT bdda0100 0008C (v01 _ASUS_ Notebook 20091228 MSFT 0097) [0.00] ACPI: SLIC bdda0470 00176 (v01 _ASUS_ Notebook 20091228 MSFT 0097) [0.00] ACPI: ATKG bddb1440 08024 (v01 _ASUS_ OEMATKG 20091228 MSFT 0097) [ 10.487942] asus_laptop: Asus Laptop Support version 0.42 [ 10.488151] asus_laptop: UL30A model detected [ 10.498208] asus_laptop: Backlight controlled by ACPI video driver [ 10.498785] input: Asus Laptop extra buttons as /devices/platform/asus_laptop/input/input5 daniel@daniel:~$ dmesg | grep -i lcd [ 43.810726] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.LCDD._BCM] (Node 8801376382f8), AE_AML_BUFFER_LIMIT (20110112/psparse-536) [ 43.811048] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.LCDD._BCM] (Node 8801376382f8), AE_AML_BUFFER_LIMIT (20110112/psparse-536) [ 129.728303] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.LCDD._BCM] (Node 8801376382f8), AE_AML_BUFFER_LIMIT (20110112/psparse-536) ... and a good 100 more of these ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741223 Title: Natty: Unable to adjust brightness for Acer Aspire 5731, requires reboot to reflect change -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756873] [NEW] Ubuntu Font Rendering Incorrectly in QT/KDE with Hinting "Slight" or "None"
Public bug reported: As described here, http://kubuntuforums.net/forums/index.php?topic=3116117.0 The Ubuntu font that is bundled with Natty in Beta 1 of Kubuntu renders in bold in KDE and QT apps when using either "none" or "slight" as hinting style, while "medium" or "full" correctly renders the font in regular weight. This applies both to sub-pixel rendering and regular anti-aliasing. The issue seems to have happened around the Beta 1 mark, as replacing /usr/share/fonts/ with the one from a previous build (not sure which exactly, but pre-beta anyway) fixes the problem. GTK rendering is unaffected (Firefox renders the Ubuntu font in regular weight). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin DRM.card0.DP.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.DP.2: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.HDMI.A.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1366x768 edid-base64: AP///wAGrywQAAESAQOAHRB4Crplm1lUniYaTVIBAQEBAQEBAQEBAQEBAQEBIBxWgFAAIzAwIDYAJaQQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzWFcwMSBWMCAKALw= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Sun Apr 10 23:07:30 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: kubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Subsystem: ASUSTeK Computer Inc. Device [1043:1862] InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta 1 amd64 (20110329.1) MachineType: ASUSTeK Computer Inc. UL30A ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=ee12fef7-92d5-4228-9933-2997a17f0555 ro rootflags=subvol=@ quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL30A dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr212:bd12/28/2009:svnASUSTeKComputerInc.:pnUL30A:pvr1.0:rvnASUSTeKComputerInc.:rnUL30A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL30A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs 20090808ubuntu11 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bold font kde kubuntu natty qt rendering ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756873 Title: Ubuntu Font Rendering Incorrectly in QT/KDE with Hinting "Slight" or "None" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756873] Re: Ubuntu Font Rendering Incorrectly in QT/KDE with Hinting "Slight" or "None"
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/756873 Title: Ubuntu Font Rendering Incorrectly in QT/KDE with Hinting "Slight" or "None" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 570542] Re: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest
With the bug re-appearing in Maverick final, and persisting, shouldn't this bug be re-opened for Maverick current? The problem remains up to, and including the latest 2.6.35-24-virtual kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570542 Title: linux-image-virtual does not include ahci module, prevents virtualbox from booting an Ubuntu guest -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails
On my rig, the new -5 kernel is as bad as the -4 kernel. I.e. the same as described in post 112 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad R500/T6x/T400[s]/T500/W500/W700/X60/X200 suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713865] [NEW] Evolution icon in dock will only open Mail component, not the full PIM component
Public bug reported: Binary package hint: unity Hi :) Just started using the Netbook edition of 10.10, coming from Kubuntu, so quite a few things are new to me. I was very confused when I started Evolution, configured it with calendars and such, and the next time I clicked the Evolution icon in the dock, I was presented only with my mail accounts and were completely unable to find the calendar window that I had seen just before. I tried a couple of stupid things like wiping the entire evolution config folders from ~, and rebooting, and finally figured out that the icon in the dock specifically requests that the Mail component should be opened, and not the "Full Suite" of Evolution, with the different components selectable in the bottom-left of the window. Fine, I thought, I'll just remove the icon, start "evolution" from the terminal, and then right-click Evolution's icon when it appears and choose to pin it to the dock. However, it's impossible to pin just "evolution" to the dock. It'll automatically change the launch command to "evolution --express -c mail" so that next time you're once again greated with just the mail component. This is seriously frustrating :) Any chance this could be fixed? Cheerio, and thanks for this version of Ubuntu - it's seriously awesome, even with the quirks. ** Affects: unity (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/713865 Title: Evolution icon in dock will only open Mail component, not the full PIM component -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713865] Re: Evolution icon in dock will only open Mail component, not the full PIM component
Okay, seems it's seriously easy to fix, as it's launching evolution the way it's being told in /usr/share/une/applications/evolution.desktop So changing Exec=evolution --express -c mail %U to just Exec=evolution should do the trick. However, the %U would indicate that it's also used for something else, like going directly to compose mode or something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/713865 Title: Evolution icon in dock will only open Mail component, not the full PIM component -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713865] Re: Evolution icon in dock will only open Mail component, not the full PIM component
Seems like, with specific .desktop files for calendar and contacts, one might create one for mail also, and then use the "non-explicit" one for "regular" loading? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/713865 Title: Evolution icon in dock will only open Mail component, not the full PIM component -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 625364] Re: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails
Just switched to the -pae kernel in UN 10.10 (which is i386, hadn't considered the 1G penalty without -pae, so I just got around to it now). Whereas before it would hang and become unresponsive on resume like described earlier, I now experience the suspend-and-resume-to-POST behavior. As in it behaves like a very quick sudo reboot without unmounting anything first ;) FTR, suspend-to-disk does nothing except lock the screen with a login prompt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/625364 Title: lenovo/thinkpad T400[s]/T500/W500/W700/X60/T6x suspend fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713865] Re: Evolution icon in dock will only open Mail component, not the full PIM component
Okay, fair nuff, although I fail to see why the express interface is more netbook-centric than the other one, as the only difference I see are buttons in the bottom of the left pane, a pane which is the same width in both versions. Or why having two open windows (with one of them missing an icon or another intuitive means of access) is better for a netbook. And even then, why one wouldn't be able to pin the full program to the launcher... Oh well :D But good to hear it's the other way around in Natty. I *am* a desktop user who saw natty and thought, 'cool!', and therefore sprang to the netbook maverick for a desktop OS ;) Until then, one can just do as I did, if they want the icon to open the full interface: $ cp /usr/share/une/applications/evolution.desktop ~/.gconf/desktop/unity/launcher/favorites/app-evolution.desktop/ $ nano ~/.gconf/desktop/unity/launcher/favorites/app-evolution.desktop/evolution.desktop change "Exec=evolution --express -c mail %U" to "Exec=evolution" Ctrl+O Ctrl+X $ nano ~/.gconf/desktop/unity/launcher/favorites/app-evolution.desktop/%gconf.xml change the value in the first to /home//.gconf/desktop/unity/launcher/favorites/app-evolution.desktop/evolution.desktop Ctrl+O Ctrl+X Log out and back in Cheerio, and thanks for your time :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/713865 Title: Evolution icon in dock will only open Mail component, not the full PIM component -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455073] Re: A mouse pointer keeps reappearing during video playback in smplayer
@#29: Nice trick! @rvm: Even if this is a distro patch which triggers this ghost moving of the cursor, you mention twice that "smplayer receives the mouse event and shows the cursor". Specifically, that the patch causes the mouse event to be sent to smplayer, but that smplayer has the decision to show the cursor or not. Might it be a good idea to set a threshold on mouse movement before deciding to show the cursor then? This would also help people with sensitive mouses which see the cursor appear as a result of the impact on the mouse from loud bass from loudspeakers, vibrations in the computer table, etc. Basically a "fix" with an improvement added on for free? I know from experience that when I grab the mouse or finger the pad to get at controls, I move the mouse a lot, like at least half the screen. A threshold on how much movement would be required to trigger the display of the cursor seems a good idea in any case, and is standard behavior on many other players. Just an idea. Which I hope you'll like, cause this problem is a showstopper for me, even if it isn't your doing ;) -- A mouse pointer keeps reappearing during video playback in smplayer https://bugs.launchpad.net/bugs/455073 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 491324] Re: smartmontools init scripts fails on 'status' action
Not sure what exactly was fixed, but "/etc/init.d/smartmontools start" doesn't seem to work in Maverick, either. Either it fails silently, or explicitly with a [fail] appendix. "service smartmontools start" works as expected, though. The daemon is still not set to start on boot, as pointed out by #4 https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/491324/comments/4 Also, the example scripts provided are buggy, though that is hardly a package maintainer issue (wall commands erroneously use the message as an argument although wall expects its input through STDIN, and the emailer tries to capture output from smartctl by feeding it the full $SMARTD_DEVICE environment variable, which includes the drive type in square brackets, e.g. "/dev/sdn [SAT]", which obviously fails. It's easily converted to something useful by for example SMARTD_DEVICE_CLEAN=`echo "$SMARTD_DEVICE" | sed 's/ .\+$//'` but still kinda sucks that the example scripts don't work :) -- smartmontools init scripts fails on 'status' action https://bugs.launchpad.net/bugs/491324 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 360378] Re: Gave up waiting for root device after upgrade then busybox console
For those of you encountering this with VirtualBox, moving the system drive(s) to a virtual IDE controller instead of a virtual SATA controller fixes it. I had the same issue after installing 10.04 to two virtual SATA drives (1 sys + 1 swap), I then tried an expert install using LILO instead of GRUB, but the same problem appeared. I then moved the two virtual drives from the virtual SATA controller to the virtual IDE controller, and it booted nicely. -- Gave up waiting for root device after upgrade then busybox console https://bugs.launchpad.net/bugs/360378 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
