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
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
Appor
*** 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)
ProcVer
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:
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 Ubunt
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 ex
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
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
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 rece
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
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 ei
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 work
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
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 y
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/+attac
** 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
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 wi
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
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
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 unpa
@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, othe
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
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 extreme
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 manual
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
insta
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 memb
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.
--
crypt
...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 thi
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 th
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
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 i
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 th
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
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 er
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 ev
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 sw
** 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
** 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
** 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
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-gen
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 const
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
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 nex
43 matches
Mail list logo
