FWIW:
The stacktrace looks very similar to this one:
https://github.com/saiarcot895/chromium-ubuntu-build/issues/5
...which was apparently caused by attempting to use MADV_FREE (which was
added in kernel 4.5) on 4.4.
** Bug watch added: github.com/saiarcot895/chromium-ubuntu-build/issues #5
** 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/1535085
Title:
Enable full touch support for ELAN0100 touchpad
To manage
FWIW:
- It looks like this happens after kernel logging is turned off, so
nothing in syslog
- From the code, it looks likely that one of these two is responsible:
1) do_plymouth
2) SysLogHandler
(Because: in progress is printed to console, so line 91
[logging.warning(...)] is
Public bug reported:
If the AI_ADDRCONFIG flag is passed to getaddrinfo() with AF_INET or
AF_INET6 address families, addresses in /etc/hosts are not resolved
properly.
The following test case illustrates the problem. Its output depends on the
configured networks, but if only lo is configured,
I see corruption on X1400 with external VGA screen (Thinkpad T60),
possibly the same issue? The corruption looks like every other line is
offset by a few (up to 10 or so) pixels, like a badly interlaced movie,
and the amount of offset moves in waves. For me, this is fixed by
changing (in Display
Public bug reported:
My eee-900 hangs when I plug in an external monitor (every time, it
seems). Note that background jobs run normally, but keyboard and screen
are dead (including console switch, lid close events, etc.).
Here's the relevant part of the syslog,
Dec 24 12:24:57 eee kernel: [
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37156339/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37156340/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37156341/Dependencies.txt
**
Another work-around seems to be to unset the environment variable
XAUTHORITY when upgrading or restarting atieventsd.
As in XAUTHORITY= aptitude dist-upgrade.
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a
No, this sounds like the normal and expected mode of operation (the gui
update tools also run under sudo, AFAIK).
I have now found an easy way to reproduce:
/etc/init.d/atieventsd restart
You have to log out to get back to normal operation (or do
/etc/init.d/atieventsd stop; chown $USER:$USER
Again today, after dist-upgrade. But this time gdm was not upgraded,
although xorg-driver-fglrx (which has atieventsd) was.
I tried to look deeper into this, and it seems that in this case it is
caused by atieventsd calling xauth add/remove -f /home/xxx/.Xauthority
as root, which triggers the
I have seen the same problem (I do not know if it is related to GDM, but
this is with hardy).
At the moment it's particularly bad; .Xauthority reverts to root:root
within a second of changing it by hand to user:user.
It seems to be atieventsd which is the trigger of this (but possibly not
the
I forgot to say: This also happened immediately after aptitude dist-
upgrade. A number of packages were updated, including gdm.
--
After gdm upgrade no X cliens can be run
https://bugs.launchpad.net/bugs/196464
You received this bug notification because you are a member of Ubuntu
Bugs, which is
12 matches
Mail list logo
