Thanks for the response. I'm on last year's model with a Core i5-7300U
CPU @ 2.60GHz.
A couple further notes for me: It seems some users are reporting 100%
repeatable failures. Mine are intermittent; so, it's a bit harder to
tell if things have started working again.
My failure mode might be
I'm running an Thinkpad X1 carbon (so no nvidia anything running), but I
am experiencing this same behavior. Also, it seems like this is the kind
of thing that should go in to the release notes. It cripples laptop
users and in my case has caused data loss.
--
You received this bug notification
Public bug reported:
In system config printer, I need to enter a URI such as
smb://win\myser:mypass@some.domain/printer_name. However, when I go to
enter the backslash, no character is entered in the textbox. it's like
there's some attempt to prevent illegal characters from being entered,
but
I just upgraded from 10.04 to 10.10 and then 11.04 and am experiencing
this problem. Wireless was dropping out every couple minutes between
rmmod/modprobe and these were showing up in dmesg:
[ 129.176839] iwlagn :03:00.0: low ack count detected, restart firmware
[ 129.176844] iwlagn
I don't think it is a duplicate. I've never had the crash occur while
browsing (though firefox is always open) and don't see a firefox core
dump or anything like that. I have intel hardware, not ATI. However, I
also cannot find a specific trigger, and it does look like it may be
caused by
Public bug reported:
Binary package hint: virtuoso-nepomuk
I've found Nepomuk to be indexing sub-folders in my home directory that
I un-clicked in the Nepomuk interface. When I go to the configuration,
the folders are still unselected and greyed-out, indicating that Nepomuk
should know that it
I completely failed to look at kdm.log, there seems to be useful
information there, for someone who is familiar with what looks to be
kernel code, specifically an intel driver of some kind. I'm attaching my
kdm.log from a crash.
P.S. For future reference, is it preferred for me to post the whole
I'm getting a similar error in an upgraded kubuntu (from 9.10 to 10.04)
on 64 bit hardware. There is nothing in Xorg.log files to indicate a
whole X crash, but my ~/.xsession-error has similar output:
XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0
after 394169 requests
