[Bug 1847389] Re: Prevent bpool (or pools with /BOOT/) to be upgraded
How exactly does it break booting? I did a zpool upgrade bpool on two machines (one VM and one laptop) before reading this warning. Both seems to boot just fine after the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Prevent bpool (or pools with /BOOT/) to be upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1160534] [NEW] The error occured short (1-2 Min.) after booting, I did not run libreoffice at all.
*** This bug is a duplicate of bug 1160533 *** https://bugs.launchpad.net/bugs/1160533 Public bug reported: The error occured short (1-2 Min.) after booting, I did not run libreoffice at all. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 18:37:20 2013 DuplicateSignature: Unpacking replacement libreoffice-common ... dpkg: error processing /var/cache/apt/archives/libreoffice-common_1%3a4.0.2~rc1-0ubuntu1~quantal2_all.deb (--unpack): trying to overwrite '/usr/lib/libreoffice/program/officehelper.py', which is also in package libreoffice-emailmerge 1:4.0.1~rc2-0ubuntu1~quantal1~ppa1 ErrorMessage: trying to overwrite '/usr/lib/libreoffice/program/officehelper.py', which is also in package libreoffice-emailmerge 1:4.0.1~rc2-0ubuntu1~quantal1~ppa1 InstallationDate: Installed on 2012-03-20 (370 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/program/officehelper.py', which is also in package libreoffice-emailmerge 1:4.0.1~rc2-0ubuntu1~quantal1~ppa1 UpgradeStatus: Upgraded to quantal on 2012-12-16 (100 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160534 Title: The error occured short (1-2 Min.) after booting, I did not run libreoffice at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1160534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1160533] [NEW] The error occured short (1-2 Min.) after booting, I did not run libreoffice at all.
Public bug reported: The error occured short (1-2 Min.) after booting, I did not run libreoffice at all. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libreoffice-common (not installed) ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 25 18:37:20 2013 DuplicateSignature: Unpacking replacement libreoffice-common ... dpkg: error processing /var/cache/apt/archives/libreoffice-common_1%3a4.0.2~rc1-0ubuntu1~quantal2_all.deb (--unpack): trying to overwrite '/usr/lib/libreoffice/program/officehelper.py', which is also in package libreoffice-emailmerge 1:4.0.1~rc2-0ubuntu1~quantal1~ppa1 ErrorMessage: trying to overwrite '/usr/lib/libreoffice/program/officehelper.py', which is also in package libreoffice-emailmerge 1:4.0.1~rc2-0ubuntu1~quantal1~ppa1 InstallationDate: Installed on 2012-03-20 (370 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libreoffice/program/officehelper.py', which is also in package libreoffice-emailmerge 1:4.0.1~rc2-0ubuntu1~quantal1~ppa1 UpgradeStatus: Upgraded to quantal on 2012-12-16 (100 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160533 Title: The error occured short (1-2 Min.) after booting, I did not run libreoffice at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1160533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Various Toshiba laptops - brightness controls work on first boot, but do nothing after suspend/resume to RAM.
Martin: With acpi_backlight=vendor and writing to toshiba/brightness after resume the backlight actually turns on, but leaves me with an empty screen. Xorg shows the following log entries: [ 211.813] (WW) intel(0): flip queue failed: Invalid argument [ 211.813] (WW) intel(0): Page flip failed: Invalid argument I can change to a still working console and back to X, but X stays blank. By killing X I get back a working X server. The Fn-F6/7 keys still manipulate the intel_backlight interface and the screen brightness is changed thereby. Seth: Without acpi_backlight=vendor nothing has changed. There isn't any difference between writing to toshiba/brightness manually or by script. The behaviour of the three interfaces is the same as before, see comment #33. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Various Toshiba laptops - brightness controls work on first boot, but do nothing after suspend/resume to RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
Yes, after resume the screen brightness can only be changed by writing to intel_backlight/brightness, not by writing to the respective brightness file of either of the two other interfaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
Thanks! I'm afraid, with this patched kernel there isn't any noticeable difference against the standard precise one. After suspend and resume the acpi_video0 and toshiba interface still respect writing to each other's brightness file, respectively, whereas intel_backlight/actual_brightness still exclusively honors the changes of its own brightness file, but doesn't respond to changes in neither of the two other interfaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
I don't know whether it may be helpful or even makes things more complicated, I had another look to the values of the brightness and actual_brightness files of the acpi_video0, toshiba and intel_backlight interfaces under /sys/class/backlight, and how they change when writing to it. A little script and its output are attached. The results show that before suspend as well as after resume the actual_brightness files of acpi_video0 and toshiba respect the changes in the brightness files of each other. The difference to be observed is the behaviour of the actual_brightness file of intel_backlight. Before suspend it respects the changes of both other interfaces' brightness files, whereas after resume it respects only the changes of the toshiba one. By the way, that's exactly what's new with your latest version of the module. With the unpatched module after resume it doesn't respect the changes of toshiba/brightness either. It could be concluded that the actual brightness of the display is neither represented by the value of acpi_video0/actual_brightness nor toshiba/actual_brightness, but the value of intel_backlight/actual_brightness. Before suspend it is modified by changes of acpi_video/brightness, after resume this fails. The Fn-F6/7 keys seem to modify the acpi_video0 interface only. Perhaps all this was obvious the whole time and I didn't realize it, but doesn't the solution have to be searched in keeping the connection between modifications of acpi_video0/brightness and the thereby changed values of intel_backlight/actual_brightness over a suspend/resume cycle? With your patched module it is no longer broken between toshiba/brightness and intel/actual_brightness. But the system tools and hardware keys apparently only read and change the acpi0_video interface. Please feel free to modify the script, if I should post further results. ** Attachment added: Script to test the connection between the different interfaces https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2971272/+files/brightness_test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
I couldn't manage to post three attachments in one comment. So here comes the output before suspend. ** Attachment added: brightness_test-before_suspend.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2971343/+files/brightness_test-before_suspend.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
And the output after resume. ** Attachment added: brightness_test-after_resume.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2971344/+files/brightness_test-after_resume.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
Oh, and I forgot something that could be of interest: I had to insert a short sleep after modifying the brightness files before reading the value of intel_backlight/actual_brightness. It seemed to need a little amount of time before it reached its new value. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
Thanks again. The value of hci_backlight is 1 after a fresh boot and 0 after supend and resume. I can't change it by writing to the file. echo 0 | sudo tee hci_backlight yields tee: hci_backlight: Invalid argument. Same result with echo 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
I'm afraid it's not that easy. The machine locks up immediately when writing to hci_backlight as with your first patched version from comment #8 on soft suspend. Regardless of whether I try to write a value of 0 after boot or 1 after suspend and resume. Not a single line in the logs, it looks like a sudden death. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
To be exact, I tried to write 1 when the value was 0 and vice versa. In both cases the machine locked up. I already read a bit about the problem on the net, so I think I have a basic idea of what you mean about the problem behind. Albeit not satisfying, at least the intel_backlight interface works after resume, and I usually don't change the brightness every few minutes. Therefore I can live with the workaround mentioned. Furthermore I tried to work around with the acpi_backlight=vendor kernel parameter. To my surprise with this parameter set intel_backlight seems to be used behind the scenes when the Fn-F6/7 keys are pressed. But after resume the backlight stayed off, hence I don't followed this approach any further. Thank you once again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
Thanks, great! The machine suspends and resumes without failure. And after resume the display brightness can now be changed by writing to the toshiba interface's brightness file. The brightness file of acpi_video0 still doesn't work after resume, what probably causes the Fn-F6/7 keys to not work either. A lesser problem? In any case, a definite progress. I'll be glad to do more testing tomorrow. For today I'm away now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
Thanks for the new build. With this version of the module my Tecra suspends and resumes successfully again. Before suspend pressing Fn-F6/7 still changes the brightness in all 8 steps as implied by the toshiba interface. Besides that, I didn't recognize any other obvious difference against the unpatched original version of the Precise kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
The Tecra R840 affected by bug #962142 has an ATI graphics card and uses the proprietary fglrx module, whereas James', who opened this bug here, and mine have Intel processor graphics, which might also make at least partly the difference between suspend failure and success. Of course that's just a guess. Indeed the error description in bug #962142 is very similar to what I could notice when my machine locked up on suspend. As you predicted with your new version from comment #15 suspend and resume still works and there is no noticeable difference against the version before from comment #12. Thanks for your continuous efforts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
I'm sorry, but the backlight file doesn't get created. There is no /sys/bus/acpi/devices/TOS1900:00. To be on the safe side I searched the whole /sys tree, but didn't find any backlight file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
It's TOS6208:00. In there is no backlight file, but a backlight directory. This contains nothing but the single subdirectory toshiba, which is the link target of /sys/class/backlight/toshiba. A directory listing is attached. I hope you understand that I don't want to play with those files without your explicit request. Jonathan Buzzard said on the linux-acpi mailing list The Toshiba provided Windows user space programs go to some length to establish what models they are running on before attempting any funny business. Over the years a number of users have tried randomly poking the HCI without knowing what they are doing and bricked their laptops. If you understood how the HCI really works under the hood, you would understand. The error checking in it last time I looked is virtually none existent. See http://www.spinics.net/lists/linux- acpi/msg20355.html ** Attachment added: Directory listing of /sys/bus/acpi/devices/TOS6208:00 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2957122/+files/dirlisting_TOS6208%3A00.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
** Attachment removed: Directory listing of /sys/bus/acpi/devices/TOS6208:00 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2957122/+files/dirlisting_TOS6208%3A00.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
I recreated the directory listing with LANG=C, because the content-type setting text/plain; charset=utf-8 doesn't seem to be respected with firefox. ** Attachment added: Directory listing of /sys/bus/acpi/devices/TOS6208:00 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2957152/+files/dirlisting_TOS6208%3A00.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
@Seth: Sorry for not having been clear enough. Without your patched driver: Suspend and resume work out of the box when suspend is initiated via panel menu entry and without closing the lid. When I suspend by closing the lid I have to disable the lock screen after screen turns off setting, otherwise the backlight stays off after resume. Before suspend I can change the brightness by directly putting some value into the brightness file of any of the three interfaces under /sys/class/backlight. After resume this only works with the brightness file of the intel_backlight interface. With your driver: Suspend is successful when initiated via lid close. But after resume the backlight stays off, even with the above mentioned lock screen setting disabled. But besides that, the resume seems to be successful. I can blindly switch to console, log in and shutdown. Yet I couldn't manage to get the backlight back on without reboot. Switching to console and back or vbetool dpms on/off cycles didn't help. When I try to suspend via menu entry the system locks up. The backlight stays on with blank screen and the fan starts running at high speed. Even the magic SysRq key as last resort withholds support. I have to hard power-off the machine. The logs (dmesg, syslog, pm-suspend, Xorg) don't show any failure entries. Before suspend all three interfaces in /sys/class/backlight are still present and the display brightness still changes when writing directly to any of their brightness files. In the case of the backlight staying off after resume I also tried blindly writing to the brightness files. But the backlight stayed off, so I can't tell whether the brightness would have changed. Of course seeing nothing but a blank screen there is certain possibility that I instead posted all my hidden secrets to Launchpad. I tested this several times and the behaviour is reproducable. With your driver the system either locks up on soft suspend or the backlight stayes off on resume after lid close suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 935778] Re: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume
My Tecra R840 shows the exact symptoms as described before. I'm on precise with all current updates (Linux brahms 3.2.0-20-generic #32-Ubuntu SMP Thu Mar 22 02:22:46 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux). With and without Seth' patched driver from #8 (Thanks, Seth, for your fine work. I already appreciated your alps patch while on oneiric.) I'm able to manipulate the brightness files of all three interfaces under /sys/class/backlight (acpi_video0, intel_backlight, toshiba). Before suspend the display respects all these changes and sets the brightness accordingly. After resume changes in acpi_video0 and toshiba are ignored, changes in intel_backlight still effectively change the brightness of the display. This is what I currently use as workaround by means of the little script attached, which translates the different values of intel_backlight and acpi_video0/toshiba. With Seth' driver installed my Tecra freezes on suspend or the backlight stays off on resume. Before suspend I recognized that changing the brightness via Fn-F6/7 uses all 8 levels, whereas without the patched driver one keystroke always takes two at a time. AFAICT the logs don't give any hint. ** Attachment added: Workaround script, sets brightness after resume https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+attachment/2925132/+files/set_brightness -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/935778 Title: Toshiba R840 - brightness controls work on first boot, but do nothing after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 773154] Re: Atheros AR9285 extremely slow unstable on 11.04
I can confirm I'm experiencing the same issue with a new Acer notebook with the Atheros AR9285 wireless controller. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773154 Title: Atheros AR9285 extremely slow unstable on 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246272] Re: support booklet format in gnome print options
Booklet printing would be a very nice feature! It is available in Adobe Reader (also for Linux). Internally, it's but 2 pages per side and flip short edge, with a correct list of pages For an 8 pages document, the pages list would be 8,1,2,7,6,3,4,5 Thus, it would be able to do it manually, if it would be possible to include white pages in the pages field of the print dialog. For a 6 pages document, the pages list would have to be W,1,2,W,6,3,4,5 where W indicates a white page -- support booklet format in gnome print options https://bugs.launchpad.net/bugs/246272 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 565407] Re: package fglrx (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 - inst_path_default or inst_path_override does not exist i
Workaround #10 / #24 worked for me. Thanks for the advice. -- package fglrx (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 - inst_path_default or inst_path_override does not exist in /etc/ati when ATI Drivers are previously installed https://bugs.launchpad.net/bugs/565407 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 433051] Re: cryptsetup fails to open LUKS partition
I had the same problem but I was able to boot and unlock the LUKS partitions after rolling back to kernel 2.6.28-16-generic. None of the kernel packages released after 2.6.28-16-generic have allowed me to complete booting and gets stuck trying to unlock the 3 LUKS partition on my system. -- cryptsetup fails to open LUKS partition https://bugs.launchpad.net/bugs/433051 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 488437] Re: cryptmount reports segfault in dmesg
I rolled back to kernel 2.6.28-16-generic as this allows me to boot, unlock and mount LUKS partitions successfully. All kernel releases since have the same bug. -- cryptmount reports segfault in dmesg https://bugs.launchpad.net/bugs/488437 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 440470] Re: [ubuntu-boot-experience] nForce2_smbus conflicts with ACPI region SM00
The acpi_enforce_resources=lax kernel boot option doesn't work for me. To be more specific, I have 3 LUKS encrypted partitions. I can unlock the first 2 but not the 3rd. I enter the passphrase and hit enter but nothing gives. I hit enter a second time and I get a message saying that unlocking the partition failed. -- [ubuntu-boot-experience] nForce2_smbus conflicts with ACPI region SM00 https://bugs.launchpad.net/bugs/440470 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 440470] Re: [ubuntu-boot-experience] nForce2_smbus conflicts with ACPI region SM00
...I forgot to mention that kernel 2.6.28-16-generic works fine. Something has changed in the Ubuntu kernel packages since 2.6.28-16-generic that has broken my system. -- [ubuntu-boot-experience] nForce2_smbus conflicts with ACPI region SM00 https://bugs.launchpad.net/bugs/440470 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 440470] Re: [ubuntu-boot-experience] nForce2_smbus conflicts with ACPI region SM00
Problem still exists in Kernel 2.6.31-15-generic. I'm running an Asus M2N32-SLI Deluxe motherboard. -- [ubuntu-boot-experience] nForce2_smbus conflicts with ACPI region SM00 https://bugs.launchpad.net/bugs/440470 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 350530] Re: crash x server 9.04
My system hasn't frozen in 10 days (since I replaced the graphics card). I can confirm that the issue I was experiencing was caused by the faulty card. -- crash x server 9.04 https://bugs.launchpad.net/bugs/350530 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 350530] Re: crash x server 9.04
I've been watching my dmesg log and I saw some backtraces that may mean a defective graphics card. I have replaced my nvidia card with an ATI card and will watch it's behavior for another couple of days. Glad to say my system hasn't frozen since I replaced the card last night. Looking closely at the old nvidia card, one of the memory chips seems to have some heat induced damage. -- crash x server 9.04 https://bugs.launchpad.net/bugs/350530 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 350530] Re: crash x server 9.04
X/gnome is pretty much unusable...it is crashing as soon as I launch an application (terminal, firefox, vuze...). I cannot kill X and get a console. I have tried SSHing from another machine and killing X and GDM on the command line, but the computer is still UNUSABLE UNTIL I REBOOT. There are no errors that stand out in the log files. -- crash x server 9.04 https://bugs.launchpad.net/bugs/350530 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 350530] Re: crash x server 9.04
Log files attached (dmesg, Xorg.0.log and Xorg.0.log.old). ** Attachment added: Logs.tar.gz http://launchpadlibrarian.net/24879924/Logs.tar.gz -- crash x server 9.04 https://bugs.launchpad.net/bugs/350530 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 350530] Re: crash x server 9.04
I also get the same random crashes in X. I'm using the free driver that comes with Ubuntu (nv). I was getting black screens while trying the Nvidia supplied driver (180.44) installed both manually and using the repository. The legacy drivers (173 and 177) didn't work either; it crashes before it even loads X/desktop. I have not tried nouveau but I suspect the result will be the same. I have an Asus EN7100GS graphics card; here is the output from lspci: 07:00.0 VGA compatible controller: nVidia Corporation GeForce 7100 GS (rev a1) Subsystem: ASUSTeK Computer Inc. Device 8222 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 5 Region 0: Memory at fa00 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e000 (64-bit, prefetchable) [size=256M] Region 3: Memory at fb00 (64-bit, non-prefetchable) [size=16M] Expansion ROM at fcfe [disabled] [size=128K] Capabilities: access denied Kernel modules: nvidiafb --- -- crash x server 9.04 https://bugs.launchpad.net/bugs/350530 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 251443] Re: keyboard layout switching shortcuts like Alt+Alt do not work anymore
I'm facing the same problem. The suggested preload fix doesn't help. Plus I have an addition to make: Generally, the layout can be switched either using the hot-keys or by clicking on the keyboard indicator. As described, after reboot the hot-keys (like Alt+Alt) don't work any more. Then I switch the layout by clicking on the indicator, then the alternative layout (Cze for Czech Default in my case) is displayed correctly, but then the behaviour is completely odd: The keys behave as if I would permanently press the Alt Gr key, e.g. when pressing the E key, the Euro sign € appears etc.. When I switch back to German (my default layout) everything works fine again. This step is fully repeatable. My workaround is similar to the one given in the bug description: The layout is correct as soon as I opened the keyboard preferences and modifid any option (seems that I just have to change anything, no matter what) and apply the changes. Afterwards the correct behaviour is restored until next reboot. Btw: Restarting gnome (Ctrl+Alt+Backspace) doesn't reproduce the problem, the problem occurs only after a complete reboot of the system. Hope my description helps tracking and solving the issue. Greetz. -- keyboard layout switching shortcuts like Alt+Alt do not work anymore https://bugs.launchpad.net/bugs/251443 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 89974] Re: usb disconnect
as my keyboard does not work while in 2.6.17-11-generic I will try to find the relevant info for you. $ uname -a (not the one i have problem with) Linux whitebox 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux ** Attachment added: dmesg from functioning kernel 2.6.17-10-generic http://librarian.launchpad.net/6644710/dmesg-working.log -- usb disconnect https://launchpad.net/bugs/89974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89974] Re: usb disconnect
** Attachment added: dmesg from 2.6.17-11-generic http://librarian.launchpad.net/6644724/dmesg.log -- usb disconnect https://launchpad.net/bugs/89974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89974] Re: usb disconnect
** Attachment added: lspci-vvnn.log http://librarian.launchpad.net/6644741/lspci-vvnn.log -- usb disconnect https://launchpad.net/bugs/89974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89974] Re: usb disconnect
** Attachment added: lspci-vvnn2.log (forgot sudo in previous one) http://librarian.launchpad.net/6644747/lspci-vvnn2.log -- usb disconnect https://launchpad.net/bugs/89974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89974] usb disconnect
Public bug reported: Binary package hint: linux-image-2.6.17-11-generic Keyboard and mouse are PS/2 connected via a PS/2-USB adapter (due to lack of PS/2 ports on the intel mac mini). After upgrade to linux-image-2.6.17-11-generic keyboard and mouse does not function. Keyboard leds flash constantly. Keyboard show no reaction to keypresses. Mouse cursor is not moving. No other USB devices are connected. /var/log/messages show multiple USB disconnect and redetections. [short version of a very long log:] Mar 5 22:18:00 localhost kernel: [17179602.916000] usb 4-2: new low speed USB device using uhci_hcd and address 11 Mar 5 22:18:00 localhost kernel: [17179603.10] usb 4-2: configuration #1 chosen from 1 choice Mar 5 22:18:02 localhost kernel: [17179605.196000] usb 4-2: USB disconnect, address 11 Mar 5 22:18:03 localhost kernel: [17179606.192000] usb 4-2: new low speed USB device using uhci_hcd and address 12 Mar 5 22:18:03 localhost kernel: [17179606.376000] usb 4-2: configuration #1 chosen from 1 choice Mar 5 22:18:06 localhost kernel: [17179608.724000] usb 4-2: USB disconnect, address 12 [end] System seem to be functioning otherwise. GDM starts. Pressing the Power button shuts down the system cleanly. Booting into linux-image-2.6.17-10-generic works fine. ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- usb disconnect https://launchpad.net/bugs/89974 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86674] xracer error: No such file or directory
Public bug reported: Binary package hint: xracer This is similar, but not identical, to this breezy bug: https://launchpad.net/ubuntu/+source/xracer/+bug/5604 . System: Ubuntu Edgy / 6.10 Filename: pool/universe/x/xracer/xracer_0.96.9-12_i386.deb Error: xracer:main.c:528: error: open: No such file or directory xracer:video.c:72: error: open: video/intro.mpeg: No such file or directory xracer:jpeg.c:92: error: powerups/cannon.jpg: No such file or directory xracer:texture.c:66: error: error loading texture file: powerups/cannon.jpg: No such file or directory How to reproduce: $ sudo apt-get install xracer [enter] $ xracer [enter] Additional info: According to dpkg -L xracer the files are not included in the package. ** Affects: xracer (Ubuntu) Importance: Undecided Status: Unconfirmed -- xracer error: No such file or directory https://launchpad.net/bugs/86674 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72995] Re: Need better way of handling permissions with nano and sudo mix
I can get this error as well. Each time nano is used with sudo the permission for .nano_history is set to rw for owner. Problem is that the owner is changed from user to root. Using chown/chmod on .nano_history to revert the owner of the file back to the user is only a temporary fix since the next time nano is used with sudo it will change these permissions back to the faulty ones. I did this to get rid of the error message: Edit /etc/nanorc and comment out set historylog. This will of course disable .nano_history all together. -- Need better way of handling permissions with nano and sudo mix https://launchpad.net/bugs/72995 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
