I'm now running 15.04, so the bug no longer applies. I've marked it as
invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/129704
> for d in /dev/input/event*; do if ! sudo evtest --query $d EV_SW
SW_DOCK; then echo $d; fi; done
Nothing.
Just a thought, but should the "suspend on boot" behaviour be made
configurable ?
Also, any idea what password lightdm is after when you resume after
booting with the lid down - it would h
The fix doesn't work for me. journal.txt attached.
Regards,
Robin
The fix as applied:
cat /lib/udev/rules.d/70-power-switch.rules
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License
I applied the fix from the ppa yesterday, but the problem is still
present. This is on a Dell E6420, docked to an E-port Replicator Plus
with a pair of external monitors.
** Attachment added: "grep -r . /sys/class/drm/* > /tmp/monitors.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+b
** Attachment added: "xrandr --query > /tmp/xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+attachment/4428458/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "journalctl -b > /tmp/journal.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+attachment/4428457/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
When booting my laptop while docked with the lid down (pair of external
monitors attached to dock), the system boots to the point of displaying
the login dialog, but immediately suspends. When resumed from suspend
by briefly pressing the power button, lightdm displays a login
Public bug reported:
No idea, this is an automatic bug report and I haven't seen the error.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvi
Public bug reported:
apport detected this error on a fresh boot.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.40
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia
Anno
*** This bug is a duplicate of bug 554795 ***
https://bugs.launchpad.net/bugs/554795
I don't have permission to access bug#554795 - could that bug be made
public ?
--
totem assert failure: totem: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:1485:
process_command: Assertion `0' failed.
https://
Public bug reported:
Dual-headed PC, gnome desktop, intrepid beta upgraded from hardy.
Monitors configured as separate X displays.
After working for a while on the 2nd monitor, power management will dim
the screen in preparation for powering down. Moving the mouse to the
primary display makes it
Looks like this has regressed in the Intrepid beta, package nvidia-
glx-173 173.14.12-1-0ubuntu3.
--
nvidia-glx is missing libnvidia-cfg.so.1
https://bugs.launchpad.net/bugs/34912
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu
Public bug reported:
Intrepid beta, upgraded from hardy via update-manager.
Running gnome on 2 monitors, in separate-x-screen mode. Click on a
quick-launch icon, and a blank error dialog pops up, and won't go away.
'top' shows gnome-panel running at a high rate of CPU utilization.
Killing the gn
Michael Vogt wrote:
> Could you please attach the output of:
> $ ls -l /etc/ld.so.nohwcap
>
>
# ls -l /etc/ld.so.nohwcap
ls: cannot access /etc/ld.so.nohwcap: No such file or directory
# ls /etc/ld*
/etc/ld.so.cache /etc/ld.so.conf
/etc/ldap:
ldap.conf
/etc/ld.so.conf.d:
i486-linux-gnui
Mine was installed from the ubuntu archives. Recently (ie Monday 31
Mar).
cheers
Michael Vogt wrote:
> Thanks for the additional information.
>
> It looks like everybody with the crash had nvidia-glx-new installed. Was
> that also the driver in use when the crash happend? If so, did you
> instal
15 matches
Mail list logo
