Thanks very much James for the very useful info (comment #92)! It has
helped me to finally solve this annoying problem on my machine.
I'm running Kubuntu 17.10 with a Logitech M310 mouse. For me, I had to
do things slightly differently to you.
"xinput" revealed that my mouse was device id 10,
I am also affected by this bug, and have been for a couple of months. I
have a Logitech M310 wireless mouse, which has been working fine for a
long time until recently:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer
I'm affected by this bug too.
This is not exactly a fix, more of a brush under the carpet: I realised
that I had absolutely no use for the Toolbar, as all of the functions
are easily accessible in the menu bar right above it (or by keyboard
shortcuts, of course). So I simply got rid of the
Just to echo Tugkan's question, I would also like to know when the fix
will be released on Yakkety. This is quite a high-profile bug, and it
would be really nice to have a fix soon! Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I also get this behaviour with my Logitech K520 keyboard and unifying
receiver, on Ubuntu 16.04 and on 15.10 before that.
I'm currently running
4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux
The same bug has been reported on the RedHat bug tracker:
I am also suffering from this issue (both the inability to use the
delete key, and occasional very slow save times). The ibus exit trick
works for me, but I also just found another workaround which you can do
without exiting ibus:
After pressing the delete key (once or multiple times) in Gnucash,
*** This bug is a duplicate of bug 1058303 ***
https://bugs.launchpad.net/bugs/1058303
** This bug has been marked a duplicate of bug 1058303
linux-image-3.2.0-31-generic-pae radeon regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Have a look at https://bbs.archlinux.org/viewtopic.php?id=133541
There are some suggested fixes there (which worked on my HP Pavilion dm1),
involving blacklisting the sp5100_tco driver and disabling the thermal module.
However, it appears that a more recent update to the driver has introduced
This appears to be an issue with the xorg video driver, which arose for
some reason when running in combination with 3.2.0-31 and subsequent
kernels, but not with earlier kernels.
It turns out that the laptop is not dead, but just that the screen does
not work at all. I can do CTRL-ALT-F1 to get
** Attachment added: dmesg log file from a failed boot (timestamps stripped)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414282/+files/dmesg-bad-stripped
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: dmesg log file from a successful boot (timestamps
stripped)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414283/+files/dmesg-good-stripped
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: dmesg log file from a failed boot (timestamps stripped,
lines sorted)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414284/+files/dmesg-bad-stripped-sorted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: dmesg log file from a successful boot (timestamps
stripped, lines sorted)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414285/+files/dmesg-good-stripped-sorted
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Unfortunately I spoke too soon again - this is an intermittent problem
and it occurred again this morning (I have now upgraded to Quantal with
kernel 3.5.0-17-generic).
I have collected dmesg log files from an occasion when the problem
occurred (the screen went blank during the boot process), and
** Attachment added: dmesg log file from a successful boot (original file)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414281/+files/dmesg-good
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am also attaching the Xorg.0.log files, from a failed and successful
boot, again also with versions which have the timestamps stripped and
the lines sorted alphabetically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log file from a failed boot (original file)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414286/+files/Xorg.0.log.bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log file from a successful boot (original file)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414287/+files/Xorg.0.log.good
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log file from a failed boot (timestamps stripped)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414288/+files/Xorg.0.log.bad.stripped
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Xorg.0.log file from a successful boot (timestamps
stripped)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414289/+files/Xorg.0.log.good.stripped
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Xorg.0.log file from a failed boot (timestamps stripped,
lines sorted)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414290/+files/Xorg.0.log.bad.stripped.sorted
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Xorg.0.log file from a successful boot (timestamps
stripped, lines sorted)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1058969/+attachment/3414291/+files/Xorg.0.log.good.stripped.sorted
--
You received this bug notification because you are a member of Ubuntu
I think this problem is now fixed. I was previously having problems
with CPU lock-ups on my laptop (an HP Pavilion dm1-4020sa), and had
fixed the problem by blacklisting the sp5100_tco driver, and disabling
the thermal module (as discussed at
https://bbs.archlinux.org/viewtopic.php?id=133541).
Unfortunately the problem re-emerged when booting this morning, so the
package updates listed above have not completely solved the issue.
The failure to boot does seem to be happening less frequently now,
though. I imagine that this is something to do with how the video
driver interacts with the
I upgraded a number of packages on my laptop this morning, and I think
these updates may have solved the problem. I've booted the system 6-7
times today without any problems. I'll report back if I spot a re-
occurrence of the issue, but I would assume it is fixed unless I post
anything else. The
I reinstalled kernel 3.2.0-31-generic-pae and changed the boot options
as described on the wiki.
The first thing to note is that when I edit the boot options, the system
boots up successfully most of the time (it seems to boot successfully
more often than if I just leave grub to run without
Public bug reported:
I recently updated my kernel packages to 3.2.0-31 (I'm using the
generic-pae flavour). I have a dual boot laptop with grub2. This has
always worked fine, but having upgraded to 3.2.0-31, grub fails to boot
the system. There are no error messages on screen - after a couple
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058969
Title:
Kernel 3.2.0-31 fails to boot from grub
To manage notifications about this bug go to:
28 matches
Mail list logo
