[Touch-packages] [Bug 1512012] Re: Kyocera Mita FS-1900 prints garbage
Hmf. "Invalid" adds insult to injury. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: Invalid Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1512012/+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 1512012] Re: Kyocera Mita FS-1900 prints garbage
Not going to collect that information again, don't want to waste time collecting information just to get ignored again. So yeah you can close this, but not with a success please. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: Incomplete Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1512012/+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 1512012] Re: Kyocera Mita FS-1900 prints garbage
Not sure whether this is the right status after submitting all the relevant info, but "Incomplete" isn't right anymore. Hopefully this thing will get a bit of love now... ** Changed in: cups (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: New Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1512012/+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 1512012] Re: Kyocera Mita FS-1900 prints garbage
Ping? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: Incomplete Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1512012/+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 1509326] Re: Various instabilities after resuming from standby
Okay... I'm seeing some glitches with Nouveau, but not all.
1) Spontaneous wake-ups, not going to sleep when told to, and similar are gone.
2) There is still improper detection of monitor configuration changes between
suspend and resume. Dlosing and reopening the lid fixed that in one instance,
don't know whether that is a general rule.
Now that monitor detection is clearly identified as an unrelated problem, I
agree it should go to a separate problem report.
How do I proceed about the spontaneous wake-ups?
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
'/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
I already have nvidia-352 installed.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
'/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
I can't file reports for different issues because I can't even name a
single issue. All I'm seeing is sporadic but nonreproducible, somehow
related failures. Some of them may be unrelated, some of them might be
misconfiguration leftovers from previous installs or attempts at getting
the machine to work reliably, but I have no way of determining which is
which.
Trying nouveau now. It used to deliver insufficient performance to drive
both of my monitors though; maybe it got upgraded, but I'm not
confident.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
'/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
Well, living with a single monitor for a while and seeing whether that
fixes the problems.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
'/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
Can you give me some instructions how to nail down the actual cause of these
problems?
The symptoms are so varied and instrutable, it almost looks as if some race
conditions deep down in the software stack leave stuff in inconsistent state.
Logging pertinent status information for each startup might be a good start.
The system is showing the login screen even though everything has been
configured to not show the login screen. Finding out the reason why would be a
good start, then I'd look for the reasons for the reason, until the root cause
is found.
(This might even be a hardware glitch, but without any pointers to a concrete
failure I can't turn in the machine for fixing. Also, if it's a hardware
problem, it would be worth it submitting a bug report to whatever software
subsystem should have logged it.)
** Changed in: xorg (Ubuntu)
Status: Expired => Incomplete
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
Issues are persistent in Wily BTW. Can't say if they are exactly the same since
the behaviour is so unstable.
Some of the old behaviour seems gone, but I'm getting new weirdnesses, such as
lightdm spontaneously restarting after unsuspending.
That particular incident:
Unsuspend started the machine, final X log message after loading was
[ 32016.399] (**) Option "xkb_layout" "de"
I switched to console 1, started investigating pstree|less. After a while, the
graphic screen came up with the login screen (which I had configured to never
show up, but ah well).
X log has this to say:
[ 32024.769] (II) evdev: Dell WMI hotkeys: Close
Not sure whether that means "lid closed" or the power button, but I was typing
on the USB keyboard, which has neither.
Not sure what to do next, any advice welcome.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Expired
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
Please unexpire. This bug report is waiting for feedback from support.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Expired
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
'/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1512012] Re: Kyocera Mita FS-1900 prints garbage
** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1512012/+attachment/4520218/+files/error_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: Incomplete Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1512012/+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 1512012] Re: Kyocera Mita FS-1900 prints garbage
Okay, finding time to deal with this again. Now I'm getting inconsistencies on the left-side port. Behaviour seems to vary according to previous history: Printing the test page first gave me the already-reported garbled output, switching off the printer and then switching it on again and retrying the printout gave me no activity on the printer and a hung print job. So I suspect it's not the USB port that made the difference but previous history and dirty state somewhere. What's the best way for get a full reset of all relevant state? For reference, I'm attaching the cups error log, timestamps of my activities: 17:48:38 I started system-config-printer 17:49:38 I opened the Properties context menu entry on the printer 17:50:25 I let the Properties dialog print the test page (not the self-test page) 17:51:10 I confirmed the OK button on the "test page submitted" dialog box -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: Incomplete Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
[Touch-packages] [Bug 1512012] [NEW] Kyocera Mita FS-1900 prints garbage
Public bug reported: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series; 10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea) Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks): ERROR rangecheck OFFENDING COMMAND: filter STACK: . 563135 --nostringval-- --nostringval-- 5 The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that. >From the DebuggingPrintingProblems page, I tried both usb-unidir-default and >usb-no-reattach-default, with no discernible difference. (Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CupsErrorLog: E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden. E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden. CurrentDesktop: XFCE Date: Sat Oct 31 21:45:05 2015 InstallationDate: Installed on 2015-08-24 (68 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lpstat: device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/ device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070 MachineType: Dell Inc. Precision M4600 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied grep: /etc/cups/ppd/FS-1900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago) dmi.bios.date: 12/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 08V9YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1512012 Title: Kyocera Mita FS-1900 prints garbage Status in cups package in Ubuntu: New Bug description: Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8 .-downloadcenteritem-Single- License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference). Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems. Steps in "USB Printer" gave the following results: 2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell) 3. tailing the syslog would show me USB activity during plug and unplug. 6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp. 8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript
[Touch-packages] [Bug 1512012] Re: Kyocera Mita FS-1900 prints garbage
Hm. Some more testing revealed an odd difference between the USB ports on the left and on the back side of my docking station. The back ports work as one would expect: printer is recognized and gets registered when plugged in, and gets unregistered when unplugged; USB drive when plugged in gets recognized and has its directory shown in Thunar (XFCE here). The left-side ports show inconsistent behaviour: The USB drive gets recognized and has its directory shown, but plugging in the printer does not provoke even a single new line in /var/log/syslog. I'm wondering how such a difference is even possible. For reference, here's the syslog from plugging the Kyocera to a back- side port: Oct 31 22:19:17 jodel kernel: [12061.944337] usb 3-1.2.1: new full-speed USB device number 16 using ehci-pci Oct 31 22:19:17 jodel kernel: [12062.038199] usb 3-1.2.1: New USB device found, idVendor=0482, idProduct=0004 Oct 31 22:19:17 jodel kernel: [12062.038202] usb 3-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 22:19:17 jodel kernel: [12062.038204] usb 3-1.2.1: Product: Kyocera Mita FS-1900 Oct 31 22:19:17 jodel kernel: [12062.038205] usb 3-1.2.1: Manufacturer: Kyocera Mita Oct 31 22:19:17 jodel kernel: [12062.038214] usb 3-1.2.1: SerialNumber: AAP2925070 Oct 31 22:19:17 jodel kernel: [12062.039274] usblp 3-1.2.1:1.0: usblp0: USB Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x0482 pid 0x0004 Oct 31 22:19:17 jodel mtp-probe: checking bus 3, device 16: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2.1" Oct 31 22:19:17 jodel mtp-probe: bus: 3, device: 16 was not an MTP device Oct 31 22:19:17 jodel systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:1a.0-usb3-3\x2d1-3\x2d1.2-3\x2d1.2.1)... Oct 31 22:19:17 jodel systemd[1]: Reached target Printer. Oct 31 22:19:17 jodel udev-configure-printer[22613]: add /devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2.1 Oct 31 22:19:17 jodel udev-configure-printer[22613]: device devpath is /devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2.1 Oct 31 22:19:17 jodel udev-configure-printer[22613]: MFG:Kyocera MDL:FS-1900 SERN:- serial:AAP2925070 Oct 31 22:19:22 jodel kernel: [12067.091976] usblp0: removed Oct 31 22:19:22 jodel kernel: [12067.094045] usblp 3-1.2.1:1.0: usblp0: USB Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x0482 pid 0x0004 Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI contains USB serial number Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI match: usb://Kyocera/FS-1900?serial=AAP2925070 Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI of detected printer: usb://Kyocera/FS-1900?serial=AAP2925070, normalized: kyocera fs 1900 serial aap2925070 Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI of print queue: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/, normalized: dnssd xerox phaser 6500dn d6 a3 e5 pdl datastream tcp local Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI of print queue: usb://Kyocera/FS-1900?serial=AAP2925070, normalized: kyocera fs 1900 serial aap2925070 Oct 31 22:19:22 jodel udev-configure-printer[22613]: Queue ipp://localhost/printers/FS-1900 has matching device URI Oct 31 22:19:22 jodel udev-configure-printer[22613]: Re-enabled printer ipp://localhost/printers/FS-1900 Oct 31 22:19:22 jodel systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:1a.0-usb3-3\x2d1-3\x2d1.2-3\x2d1.2.1). (The Xerox is a network printer, reachable only through LAN.) Unplugging syslog: Oct 31 22:20:52 jodel kernel: [12157.332544] usb 3-1.2.1: USB disconnect, device number 16 Oct 31 22:20:52 jodel kernel: [12157.332719] usblp0: removed Oct 31 22:20:52 jodel udev-configure-printer[22655]: remove /devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2.1 Oct 31 22:20:52 jodel udev-configure-printer[22655]: URI of detected printer: usb://Kyocera/FS-1900?serial=AAP2925070, normalized: kyocera fs 1900 serial aap2925070 Oct 31 22:20:52 jodel udev-configure-printer[22655]: URI of print queue: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/, normalized: dnssd xerox phaser 6500dn d6 a3 e5 pdl datastream tcp local Oct 31 22:20:52 jodel udev-configure-printer[22655]: URI of print queue: usb://Kyocera/FS-1900?serial=AAP2925070, normalized: kyocera fs 1900 serial aap2925070 Oct 31 22:20:52 jodel udev-configure-printer[22655]: Queue ipp://localhost/printers/FS-1900 has matching device URI Oct 31 22:20:52 jodel udev-configure-printer[22655]: Disabled printer ipp://localhost/printers/FS-1900 as the corresponding device was unplugged or turned off Oct 31 22:20:52 jodel systemd[1]: printer.target: Unit not needed anymore. Stopping. Oct 31 22:20:52 jodel systemd[1]: Stopped target Printer. ... this is getting weirder by the minute. Now the left-side USB ports show syslog messages, too. Well, the test page is *still* wonky. That's not
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
11) Did a reboot because graphics performance had dropped. Reboot through XFCE
desktop would make the screen go black, pstree showed that the desktop still
lived. reboot command from console would work, but boot into a black screen
(after a brief display of a background and something that might have been the
mouse pointer). Closing and opening the lid would not help, detaching the
laptop from the docking station and Ctrl-Alt-F7 would restore the XFCE desktop,
reattaching to the docking station would give access to the
docking-station-connected screens.
So... something wasn't properly initialized with the docking station attached
during boot.
For reference, I have placed the following script on a hotkey to switch
from laptop to docking-station-connected screens.
#! /bin/sh
echo == >>/home/jo/xrandr.log
echo docked.sh >>/home/jo/xrandr.log
date >>/home/jo/xrandr.log
echo >>/home/jo/xrandr.log
xrandr --output DP-6 --auto >>/home/jo/xrandr.log 2>&1
xrandr --output LVDS-0 --off >>/home/jo/xrandr.log 2>&1
xrandr --output DP-3 --auto --left-of DP-6 --primary >>/home/jo/xrandr.log 2>&1
It's extremely rigid and unable to deal with any variation in the
hardware situation, and sometimes is fails to disable LVDS-0 and cannot
activate DP-3 afterwards (I think because there are only two CRTCs), but
if all hardware is properly detected, it will work reliably on the
second attempt... barely good enough so I don't have to redo Display
configuration every time it fails to auto-reconfigure when attaching to
or detaching from the docking station.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic,
[Touch-packages] [Bug 1509326] Re: Various instabilities around hibernate, standby, and display control
Added Christopher M. Penalver (penalvch) as requested in #1313847.
Sorry for coming back to you so late, I've been trying to find out more but
couldn't determine anything.
Note that ubuntu-bug reported this to me when I started it from the
command line:
ubuntu-bug xorg
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_xorg.py", line 677, in add_info
attach_nvidia_info(report, ui)
File "/usr/share/apport/package-hooks/source_xorg.py", line 521, in
attach_nvidia_info
attach_file(report, logfile)
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 115, in
attach_file
report[key] = read_file(path, force_unicode=force_unicode)
File "/usr/lib/python3/dist-packages/problem_report.py", line 627, in
__setitem__
assert k.replace('.', '').replace('-', '').replace('_', '').isalnum()
AssertionError
(process:7289): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
--
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/1509326
Title:
Various instabilities around hibernate, standby, and display control
Status in xorg package in Ubuntu:
New
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby or shutdown cycle.
Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Dell Precision M4600
- did a BIOS update a while ago (that changed the problems, slightly for the
better I think)
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
[Touch-packages] [Bug 1509326] [NEW] Various instabilities around hibernate, standby, and display control
Public bug reported:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby or shutdown cycle.
Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think it's
blacklisted for my machine) -> Click on "Shutdown" -> no shutdown, I get
the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text mode
messages, monitor flashes and shows graphic content (mostly a mouse
cursor on some background, too fast to properly see), then the screen
goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the screen dark
again (both the builtin laptop screen and one of the external,
connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon is
reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Dell Precision M4600
- did a BIOS update a while ago (that changed the problems, slightly for the
better I think)
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
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:
[Touch-packages] [Bug 1509326] Re: Various instabilities after resuming from standby
It's my main and only work machine, I can upgrade if and only if I can easily
revert any upgrade.
I don't expect to be able to revert from Wily to Vivid, so that's not an option
unless I can have guarantees.
A driver update would be fine, I can always go back to Nouveau, then reinstall
the current Nvidia driver.
Given #1488206 and #1507328, and that I've been having these problems
for years now, I do not expect the driver update to fix anything, but I
can still check and see what's happening. (My bets are on a race
condition somewhere in the wakeup software stack since the symptoms are
so irreproducible, but I don't know how to validate that.)
More symptoms:
9) Sometimes (rarely), X stops recognizing the screen. I get a "default"
screen @1024x768 instead of the VGA-0, LVDS-0, and DP0...DP-6
connections in xrandr --verbose. It does not help to reboot, not even
when disconnecting from all power including battery. What does help is
installing Nouveau, then reinstalling nvidia-current.
10) Sometimes (slightly more often than symptom nr. 9), I get the same as nr.
8, shutdown does not complete. I cannot get a console through Ctrl-Alt-F1, but
I can Ctrl-Alt-F7 and get a graphic screen with a greyed-out desktop and an
empty dialog window (there's a white title bar and a grey dialog area, but no
title, no icons, no text, no buttons, no border, entirely unresponsive).
What I could do was to Ctrl-Alt-Del to get to the lock screen. From there, I
could resume my normal session (just to restore the same
greyed-out-with-unresponsible-dialog behaviour). I could also start a guest
session, but I didn't try anything there because I believe guest isn't in the
sudoers list.
Logging in with explicit user name gave me a black screen and unresponsiveness
to Ctrl-Alt-F1 and Ctrl-Alt-F7, so I power cycled the machine and called it a
day.
--
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/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package in Ubuntu:
Incomplete
Bug description:
None of these problems are readily reproducible, I'm having a roughly
30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think
it's blacklisted for my machine) -> Click on "Shutdown" -> no
shutdown, I get the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text
mode messages, monitor flashes and shows graphic content (mostly a
mouse cursor on some background, too fast to properly see), then the
screen goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the
screen dark again (both the builtin laptop screen and one of the
external, connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23
[Touch-packages] [Bug 1313847] Re: "xrandr: Configure crtc0 failed" on awake from sleep
I'm having the same symptoms, though I'm getting a different crtc in my messages and am using the Nvidia driver. Sometimes closing and reopening the desktop lid will help, sometimes it will not. -- 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/1313847 Title: "xrandr: Configure crtc0 failed" on awake from sleep Status in xorg package in Ubuntu: Expired Bug description: Every time I put my laptop to sleep and wake it up again I am presented with the graphical login prompt as expected. The prompt works, I have a mouse, keyboard works, etc. Once I successfully login the display turns black and remains that way no matter how long I wait. The computer is responsive and I can switch to a tty. Switching to a tty and then back to the graphical desktop does not produce anything (screen remains black.) From the TTY I've tried to configure X manually using xrandr and the --display argument: `xrandr --output LVDS1 --mode 1366x768 --pos 0x0 --rotate normal --display :0` This gives me the error "xrandr: Configure crtc0 failed". Note that 1366x768 is the native display mode of my monitor. If it matters I'm using the i915 driver (I have an intel graphics controller, revision 9). If I run this command after a successful boot, it works (I can change to a different display mode and then back again no problem). Logs don't seem to have anything interesting in them; but I may not be looking in the right logs at the right time. Guidance needed :) If I reboot the computer from the tty; I get the xfce graphical shutdown screen. I'm currently running xubuntu 14.04. This laptop used to run xubuntu 12.10 without issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 28 09:57:21 2014 InstallationDate: Installed on 2014-04-20 (8 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313847/+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
