[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
I also see these on 18.04 bionic server installs ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Triaged Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...
OK, the touchpad issue is not related at all, there is a kernel driver explanation of that. Now it works (the touchpad) but still, the mentioned dbus error message occurs from time to time, not so consistent though now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: Confirmed Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...
** Attachment added: "core dump file" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+attachment/5214227/+files/apport_core_0k2jxx4e -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: New Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804027] Re: dbus-daemon sigsegv, apport cannot report it: expected core size ...
** Attachment added: "crash file from /var/crash" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+attachment/5214228/+files/_usr_bin_dbus-daemon.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: New Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804027] [NEW] dbus-daemon sigsegv, apport cannot report it: expected core size ...
Public bug reported: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1804027/+attachment/5214223/+files/Screenshot%20from%202018-11-19%2017-32-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1804027 Title: dbus-daemon sigsegv, apport cannot report it: expected core size ... Status in dbus package in Ubuntu: New Bug description: At almost every boot and login after a while I get a "Ubuntu 18.10 has experienced an internal error" window. However it says, coredump size is too small (see attached screenshot). Also no idea if it is related but touchpad of the notebook does not work only external mouse. This is a fresh 18.10 install on this new Lenovo L580 notebook, live version of ubuntu worked fine with touchpad and there was no window on dbus like that. However after the install it worked only once, then not anymore, regardless of reboot, powering off and on etc, and usually the mentioned internal error window is shown. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: dbus 1.12.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 17:24:50 2018 InstallationDate: Installed on 2018-11-15 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1804027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373070] Re: full fix for disconnected path (paths)
Same problem with powerdns, I can't run it with apparmor profile, because it complains: operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/pdns_server" name="run/systemd/journal/dev- log" pid=17236 comm="pdns_server" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 I am not an expert, but I tried to put run/systemd/journal/dev-log into the profile, but it is not accepted as it does not start with / ... But this is what kernel log suggest, so what can I do otherwise? Note: I have: /usr/sbin/pdns_server flags=(complain,attach_disconnected) But still ... (now I have only complain mode). If I exclude pdns from systemd it works btw, and no wonder as it seems the problem somehow connected to systemd's journal, so it's better not to use systemd if possible since it renders apparmor unusable in my experience :( But for sure, I would be more than happy to have a better option, rather than deleting systemd's unit file each time after upgrade pdns ... Or so. this is up-to-date Ubuntu 16.04.3 LTS 64 bit, fresh install, but I have about a dozen of servers with this problem with different daemons as well, not only powerdns. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1373070 Title: full fix for disconnected path (paths) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: Confirmed Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so much other solution I could find :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Ok, I've found a workaround, to specify this kernel parameter in GRUB:
video=VGA-1:1920x1080@60
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so much other solution I could find :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Please tell me, if you need further information of some kind of co-
operation to resolve this issue. Thanks a lot, in advance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Another interesting finding with grep'ing around in /var/log for VGA-1:
root@vega:/var/log# grep VGA-1 syslog
May 4 14:27:10 vega unity-settings-[1644]: unable to get EDID for
xrandr-VGA-1: unable to get EDID for output
And maybe the even more interesing part in /var/log/gpu-manager.log
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.10.0-21-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.10.0-21-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? no
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 8086:152
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-VGA-1
Number of connected outputs for /dev/dri/card0: 1
Does it require offloading? yes
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? no
How many cards? 1
Has the system changed? No
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
Single card detected
Nothing to do
No change - nothing to do
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
I'm really not an xrandr / etc wizard, but what looks strange for me,
that it seems something reports "VGA-1" when all the examples on the Net
(and in xrandr man page) mentions "VGA". Even in Xorg.log:
root@vega:~# fgrep VGA /var/log/Xorg.0.log
[25.034] (II) modeset(0): Output VGA-1 has no monitor section
[25.037] (II) modeset(0): EDID for output VGA-1
[25.037] (II) modeset(0): Printing probed modes for output VGA-1
[25.037] (II) modeset(0): Output VGA-1 connected
[25.037] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology
[Touch-packages] [Bug 1688253] [NEW] Wrong resolution, and "unknown monitor" since upgraded to 17.04
Public bug reported:
I've never had a problem like this before. Now, after upgraded to Ubuntu
17.04 it was already strange to see the boot logo in a kind of low and
fuzzy resolution. And it remained for the LightDM login screen, also for
the desktop after logged on. System setting -> Display reports "Unknown
Display". System settings -> Software & updates -> Additional drivers
shows title "Unknown: Unknown" though after that "Using Processor
microcode firmware for Intel CPUs from intel-microcode" is active. I
could "work the problem around" (see the end of this writing) but it's
really ugly that I need to run a script every time, when it always
worked well on the same machine before this Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis)
0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection (this
monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120
-hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my script
(I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock 67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Touch-packages] [Bug 1562398] [NEW] Xorg freeze on SDL2 using full screen with wine with windows program
Public bug reported: My problem seems to be rather specific. I develop an emulator for a 8 bit computer with SDL2, capable of running on Linux and Windows. I use cross-compiling with mingw for Windows, and wine to test it. It seems the problem occurs when I try the windows build, with full screen mode. When I try to switch full screen off, I get back my desktop, and mouse can be moved, however I can't simply do anything with keyboard and neither with mouse anymore. If I press power-off button of my notebook, system seems to shuts down though, but I need to do that, as it's not possible to use my desktop anymore. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 26 22:03:58 2016 DistUpgraded: 2015-10-18 23:18:25,282 INFO cache.commit() DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-30-generic, i686: installed virtualbox, 5.0.14, 4.2.0-34-generic, i686: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 (1484 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to wily on 2015-10-18 (159 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Mar 26 20:31:35 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 ubuntu wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1562398 Title: Xorg freeze on SDL2 using full screen with wine with windows program Status in xorg package in Ubuntu: New Bug description: My problem seems to be rather specific. I develop an emulator for a 8 bit computer with SDL2, capable of running on Linux and Windows. I use cross-compiling with mingw for Windows, and wine to test it. It seems the problem occurs when I try the windows build, with full screen mode. When I try to switch full screen off, I get back my desktop, and mouse can be moved, however I can't simply do anything with keyboard and neither with mouse anymore. If I press power-off button of my notebook, system seems to shuts down though, but I need to do that, as it's not possible to use my desktop anymore. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz
[Touch-packages] [Bug 1434396] Re: Xserver does not start or freezes with systemd + lightdm
Meanwhile, I've upgraded to 15.10. Now the system _mostly_ works, but let's say about every 5th boot the system freezes with black screen if systemd is used. Upstart always work. Interestingly in most cases systemd works as well, but not always. I cannot find any reason about this always changing behaviour if I try to boot multiple times. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start or freezes with systemd + lightdm Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on freezes with systemd + lightdm
** Summary changed: - Xserver does not start on boot (low-graphics mode) + Xserver does not start on freezes with systemd + lightdm ** Summary changed: - Xserver does not start on freezes with systemd + lightdm + Xserver does not start or freezes with systemd + lightdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start or freezes with systemd + lightdm Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
This bug seems to be still valid, but its behaviour is somewhat different at least for me. When I first noticed this, X did not start at all, and it dropped to the screen to allow to choose for low graphics mode, exit to console, etc. Now, X starts however it freezes in a way that no keyboard can be used (ie to type my password to be able to log in). I use the system with upstart to work the problem around, but of course it would be better to forget those workarounds ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
It seems though it can be guessed more or less what can cause problems (ie thinkpad + lightdm + systemd) the exact details are not the same, and some other conditions can/do count as well. Also the not always factor sometimes, kinda odd. However, as bug 1340964 if often referenced for me, and it is about some kind of VT activation problem, can it be because some race condition on using VTs or such? Since systemd may do deeper parallelism on the boot process than upstart (I am not sure just guessing) or at least it did it not the very same way, it can explain why it works with upstart but not with systemd. But really, I am just guessing, and trying to give hints, as release data for vivid is coming and this bug still exists rendering ubuntu totally unusable for normal users on some hardware like some thinkpad notebooks which are not so rare, I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
For me, it's kinda odd. It seem to work (and worked even some day ago), then trying again (boot again) and it does not work again then ... Recently it seems to be quite unpredictable. But it can be a reason that sometimes I attach external monitor via the VGA D-SUB connector, but sometimes I don't. I'll check both cases out soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Ok, I was too fast ... Tried again: now, X server starts and logic screen is shown (though with the default background not the one based on the last user logged in) but keyboard does not usable and no mouse cursor either. Still, choosing upstart seems to work! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Today I tried again and now it seems system boots normally, I can log in, with lightdm+systemd. I guess some of the updates solved the problem, but it would be useful to hear that it's not only me ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
@asala But does using upstart (or systemd, but with gdm instead of lightdm) fixes it for you? Then it can be said, at least lightdm+systemd issue ... However reading duplicates, and comments here, at least it seems, Lenovo Thinkpads are highly affected for some reason, even if not only ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
ThinkPad L520: exactly the same as professordes wrote: systemd + lightdm does not work, dropping to console login freezes (interestingly it worked some days ago when I managed to use service lightdm stop/start to cure the problem at least so systemd could be used with some extra work though, not the system is simply not usable with systemd). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Now it turns out even more bizarre, I can no longer use my notebook with systemd. After having that low-graphics dialog, only exit to console helped (eg stopping/starting lightdm service by hand) but now exit to console cause a freeze that the computer does not react to keyboard anymore (not even num lock led etc). Though sysreq magic key combos seem to work. The only option now is to choose upstart from grub. Then system boots without any problem (not even need to exit console etc) as it should be. Again apport wanted to report Xorg crash after a reboot with upstart, but again, bug 1340964 is referenced. It seems nothing bad happens with upstart, only systemd though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
And it seems after I can login the crash report dialog brings me to bug 1340964 then. What is interesting for me: why is there a problem Xorg does not start, when it does if I try it then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in lightdm package in Ubuntu: Confirmed Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Hmm, reading the duplicates, it seems it's a Lenovo notebook + systemd + lightdm combined problem, and does not occur too much if all of the three conditions do not meet? For me, it's true, all of them, and I have the problem at least ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
The dialog box saying low graphics mode allows me to exit to console, if I do that, I can see on console 7 (ALT+F7): [FAILED] Failed to start Light Display Manager. See systemctl status lightdm.service for details. [DEPEND] Dependency failed for Graphical Interface. Entering the suggested command: lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Sun 2015-03-22 11:57:36 CET; 4min 44s ago Docs: man:lightdm(1) Process: 982 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Process: 978 ExecStartPre=/bin/sh -c [ $(basename $(cat /etc/X11/default-display-manager 2/dev/null)) = lightdm ] (code=exited, status=0/SUCCESS) Main PID: 982 (code=exited, status=1/FAILURE) Mar 22 11:57:35 antares systemd[1]: Unit lightdm.service entered failed state. Mar 22 11:57:35 antares systemd[1]: lightdm.service failed. Mar 22 11:57:36 antares systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 22 11:57:36 antares systemd[1]: lightdm.service failed to schedule restart job: Transaction is destructive. Mar 22 11:57:36 antares systemd[1]: Unit lightdm.service entered failed state. Mar 22 11:57:36 antares systemd[1]: lightdm.service failed. issuing command service lightdm start starts lightdm though, and I can login and work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
** Package changed: xorg (Ubuntu) = lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in lightdm package in Ubuntu: New Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] [NEW] Xserver does not start, on boot (low-graphics mode)
Public bug reported: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start, on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core
[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
** Summary changed: - Xserver does not start, on boot (low-graphics mode) + Xserver does not start on boot (low-graphics mode) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434396] Re: Xserver does not start, on boot (low-graphics mode)
By the way I am not sure if it's related: on booting backlight of the LCD (of the notebook) is always set to minimal during the boot at one moment, barely visible (but surely I can use the keyboard Fn + corresponding key to increase to a readable level). It was also the situation with the previous ubuntu version ... Also I am using an external monitor through the VGA connector connected, till logging in, the login is presented on the notbook's own LCD (with that dimmed backlight ...) the external monitor has no signal at all till the login screen appears after that only an ubuntu logo is shown in front of my background picture. After logging in, the configured situation works, ie the internal LCD of the notebook goes off, and I can use the external monitor. In case of shutting the system down, the notebook's internal LCD turns on with that very dimmed backlight till the machine powers off completely. However this behaviour was more or less the same, now my current problem that X doesn't seem to start at all, which was not the case before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1416999] [NEW] After a while X becomes quite slow
Public bug reported: I am not sure if it's bug of xserver-xorg or other package. The problem: after reboot everything seems to be fine, scrolling within windows, moving windows are smooth and fast. After some time however everything becomes quite slow, eg output in gnome-terminal which made the content scrolling can bee seen when refreshing, even an editor (like geany) is slow when you move the cursor, moving windows is also slow and jerky. A reboot (or logging out then in, it seems) cures the problem but after a while problem return. I am not sure if it's related, but /var/log/Xorg.0.log is full of lines like this: [191341.166] (II) intel(0): switch to mode 1920x1080@60.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none For example now I have 107 lines like this. I am using daily updated Ubuntu 14.10 (32 bit), and it's a problem experienced since some weeks (I can't tell more precisely, sorry), I haven't seen this before, ever. Also, Xorg seems to use quite lot of CPU (according to top), at least more than usual, but it's hard to tell exact numbers. Maybe related: I usually don't switch my computer off. Compiz seems to use more and more memory, according the top it used something like 4% (4Gbyte of RAM) but I also seend something like 22% after some days of uptime. Closing all windows on the desktop seems not to help so it's more like some kind of memory leaking? The only suspect log lines in the kernel log (dmesg): [ 13.493187] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 13.493198] [drm] Driver supports precise vblank timestamp query. [ 13.501309] [drm] Wrong MCH_SSKPD value: 0x20100406 [ 13.501311] [drm] This can cause pipe underruns and display issues. [ 13.501312] [drm] Please upgrade your BIOS to fix this. [ 13.940404] fbcon: inteldrmfb (fb0) is primary device [ 13.940502] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 13.981857] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 14.802073] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 22.099955] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [ 22.099959] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun However no screen corruption etc can be seen, just slowness after a while. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 2 09:15:43 2015 DistUpgraded: 2014-10-24 21:56:36,231 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-05-08 (270 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lsusb: Bus 002 Device 003: ID 1267:0213 Logic3 / SpectraVideo plc Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-24 (100 days ago) dmi.bios.date: 02/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I don't know if it helps, but I always had problems like no input field for password or the double unlock (if the first problem does not occur, unlock presented another unlock field with a sightly different screen) problem on my notebook. Then I noticed, I have a package installed named light-locker (I am not sure about the name though, just by heart now). After removing that package I had no problem like these since then! Since I've installed meta-packages xubuntu-desktop and lubuntu-desktop as well (so I can test different desktops) it can be a reason as (if I am correct) these packages depends on light-locker. Removing them caused those meta packages to be removed as well (again, if I remember well enough), but at least since then I have no problem with regular ubuntu (unity) desktop lockingunlocking. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Another observation: in case of problem also shutdown does not work sometimes, it simply doesn't do anything, even if try multiple times. The only solution then: switch to text console, log in, give command init 0 as root. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
