[Desktop-packages] [Bug 1799920] Re: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade
Hi, I have switched from Gnome to i3, this fixed the issue for me. The underlying issue might have been fixed by https://cgit.freedesktop.org/drm- tip/commit/?id=3cf71bc9904d7ee4a25a822c5dcb54c7804ea388, but I didn't check. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1799920 Title: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade Status in xorg-server package in Ubuntu: Won't Fix Bug description: Hi, Since upgrading to 18.10, my Dell P2715Q external screen (connected to a Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity: - leave the laptop idle for a while, gnome screen lock will take over and shut down the internal panel & external screen (it enters power saving mode). Same behaviour as 18.04. - however, if I come back after an hour or so and move the mouse or press a key, only the internal panel wakes up. The external screen remains blank (Xorg probably think that the external screen is on as the password prompt of gnome screen lock will not be visible on the internal panel, it's probably displayed on the blank surface -- I have to enter my password blind to get back to the desktop). Running xrandr without any argument sometimes helps getting the external screen to turn on. When it does not, I have to turn the screen OFF and ON again. I haven't seen any error message in dmesg or Xorg.0.log. $ uname -a Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci -vv 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Dell Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Dell Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) Subsystem: Dell Broadwell-U Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Dell Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Dell Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Dell Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pc
[Desktop-packages] [Bug 1799920] Re: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade
Hi, For some reason apport-collect just exit at the end, and doesn't send anything to launchpad... No error, no crash -- just exit to shell when being instructed to send the report. $ apport-collect -p xserver-xorg-core 1799920 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=&allow_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... $ (access granted to launchpad, answer the few questions asked, click send... and it just exit). Is there anything special I can provide manually? The bug I encounter might be related to https://bugs.freedesktop.org/show_bug.cgi?id=107446 ** Bug watch added: freedesktop.org Bugzilla #107446 https://bugs.freedesktop.org/show_bug.cgi?id=107446 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1799920 Title: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, Since upgrading to 18.10, my Dell P2715Q external screen (connected to a Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity: - leave the laptop idle for a while, gnome screen lock will take over and shut down the internal panel & external screen (it enters power saving mode). Same behaviour as 18.04. - however, if I come back after an hour or so and move the mouse or press a key, only the internal panel wakes up. The external screen remains blank (Xorg probably think that the external screen is on as the password prompt of gnome screen lock will not be visible on the internal panel, it's probably displayed on the blank surface -- I have to enter my password blind to get back to the desktop). Running xrandr without any argument sometimes helps getting the external screen to turn on. When it does not, I have to turn the screen OFF and ON again. I haven't seen any error message in dmesg or Xorg.0.log. $ uname -a Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci -vv 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Dell Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Dell Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) Subsystem: Dell Broadwell-U Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Dell Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Dell Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Dell Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
[Desktop-packages] [Bug 1799920] Re: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade
Just got the external screen in the same state again (ie, blank) after leaving the desk for 5-10 minutes. While in that state, the external screens tells that it doesn't receive any signal. Switching it's input from it's usual DP input to another one, and switching back again does restore the image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799920 Title: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade Status in xorg package in Ubuntu: New Bug description: Hi, Since upgrading to 18.10, my Dell P2715Q external screen (connected to a Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity: - leave the laptop idle for a while, gnome screen lock will take over and shut down the internal panel & external screen (it enters power saving mode). Same behaviour as 18.04. - however, if I come back after an hour or so and move the mouse or press a key, only the internal panel wakes up. The external screen remains blank (Xorg probably think that the external screen is on as the password prompt of gnome screen lock will not be visible on the internal panel, it's probably displayed on the blank surface -- I have to enter my password blind to get back to the desktop). Running xrandr without any argument sometimes helps getting the external screen to turn on. When it does not, I have to turn the screen OFF and ON again. I haven't seen any error message in dmesg or Xorg.0.log. $ uname -a Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci -vv 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Dell Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Dell Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) Subsystem: Dell Broadwell-U Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Dell Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Dell Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Dell Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERRE
[Desktop-packages] [Bug 1799920] [NEW] External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade
Public bug reported: Hi, Since upgrading to 18.10, my Dell P2715Q external screen (connected to a Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity: - leave the laptop idle for a while, gnome screen lock will take over and shut down the internal panel & external screen (it enters power saving mode). Same behaviour as 18.04. - however, if I come back after an hour or so and move the mouse or press a key, only the internal panel wakes up. The external screen remains blank (Xorg probably think that the external screen is on as the password prompt of gnome screen lock will not be visible on the internal panel, it's probably displayed on the blank surface -- I have to enter my password blind to get back to the desktop). Running xrandr without any argument sometimes helps getting the external screen to turn on. When it does not, I have to turn the screen OFF and ON again. I haven't seen any error message in dmesg or Xorg.0.log. $ uname -a Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci -vv 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Dell Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Dell Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) Subsystem: Dell Broadwell-U Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Dell Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Dell Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Dell Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) (prog-if 20 [EHCI]) Subsystem: Dell Wi
[Desktop-packages] [Bug 1636486] Re: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell
Glad it worked for you too. The guys who did the actual work are the one to be thanked ;) Now let's see when this gets merged in mainline & stock Ubuntu kernels! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1636486 Title: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi, I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel) laptop, directly attached to an external Dell P2715Q 4K (3840x2160 @60Hz) via DP. The 4K external screen is flickering when doing light activity -- easily reproduced when using an X terminal. Steps to reproduce: - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on the external 4K screen - do some light web browsing - give focus to the X terminal or gvim // at this point, display is still perfectly steady - press a key to enter a single character // as soon as the key is pressed, external screen goes black for a few seconds. Laptop screen is not affected. - Wait for the screen to come back, then continue typing // screen generally stays ON, but sometimes continues to flicker a few times in next minute. This happens almost every time I switch to the terminal window and start typing. OS specs: - Ubuntu 16.10 running Unity, modesetting Xorg driver - kernel 4.8.0. Issue is still present with 4.9.0rc1. The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11) doesn't exhibit this issue. Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1636486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636486] Re: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell
Hey The issue has just been solved for me in the "work in progress" Intel kernel branch (drm-tip). Try a kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm- tip/ I hope that those fixes will be included in kernel 4.12. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1636486 Title: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi, I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel) laptop, directly attached to an external Dell P2715Q 4K (3840x2160 @60Hz) via DP. The 4K external screen is flickering when doing light activity -- easily reproduced when using an X terminal. Steps to reproduce: - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on the external 4K screen - do some light web browsing - give focus to the X terminal or gvim // at this point, display is still perfectly steady - press a key to enter a single character // as soon as the key is pressed, external screen goes black for a few seconds. Laptop screen is not affected. - Wait for the screen to come back, then continue typing // screen generally stays ON, but sometimes continues to flicker a few times in next minute. This happens almost every time I switch to the terminal window and start typing. OS specs: - Ubuntu 16.10 running Unity, modesetting Xorg driver - kernel 4.8.0. Issue is still present with 4.9.0rc1. The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11) doesn't exhibit this issue. Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1636486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636486] Re: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell
Hi, Doesn't looks like a duplicate of bug 1626935 to me! The flickering in my case happens: - only when something light happens in somewhere on the external screen (like entering a single character in a terminal window). When nothing happens on screen, or when using graphics-heavier apps (like a web browser), the screen doesn't flicker - the flickering is not similar to a triple buffering issue neither is related to the nautilus wallpaper -- it looks like a DisplayPort reset (ie, as if you disconnect/reconnect the monitor), with a 2-3s complete blackout of the monitor - this is specific to the modesetting driver. The xserver-xorg-video-intel driver is fine. ** This bug is no longer a duplicate of bug 1626935 [yakkety] desktop is black and/or flickering after plugging in a second monitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1636486 Title: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell Status in xorg-server package in Ubuntu: New Bug description: Hi, I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel) laptop, directly attached to an external Dell P2715Q 4K (3840x2160 @60Hz) via DP. The 4K external screen is flickering when doing light activity -- easily reproduced when using an X terminal. Steps to reproduce: - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on the external 4K screen - do some light web browsing - give focus to the X terminal or gvim // at this point, display is still perfectly steady - press a key to enter a single character // as soon as the key is pressed, external screen goes black for a few seconds. Laptop screen is not affected. - Wait for the screen to come back, then continue typing // screen generally stays ON, but sometimes continues to flicker a few times in next minute. This happens almost every time I switch to the terminal window and start typing. OS specs: - Ubuntu 16.10 running Unity, modesetting Xorg driver - kernel 4.8.0. Issue is still present with 4.9.0rc1. The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11) doesn't exhibit this issue. Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1636486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1636486] [NEW] External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell
Public bug reported: Hi, I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel) laptop, directly attached to an external Dell P2715Q 4K (3840x2160 @60Hz) via DP. The 4K external screen is flickering when doing light activity -- easily reproduced when using an X terminal. Steps to reproduce: - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on the external 4K screen - do some light web browsing - give focus to the X terminal or gvim // at this point, display is still perfectly steady - press a key to enter a single character // as soon as the key is pressed, external screen goes black for a few seconds. Laptop screen is not affected. - Wait for the screen to come back, then continue typing // screen generally stays ON, but sometimes continues to flicker a few times in next minute. This happens almost every time I switch to the terminal window and start typing. OS specs: - Ubuntu 16.10 running Unity, modesetting Xorg driver - kernel 4.8.0. Issue is still present with 4.9.0rc1. The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11) doesn't exhibit this issue. Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1636486 Title: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell Status in xorg-server package in Ubuntu: New Bug description: Hi, I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel) laptop, directly attached to an external Dell P2715Q 4K (3840x2160 @60Hz) via DP. The 4K external screen is flickering when doing light activity -- easily reproduced when using an X terminal. Steps to reproduce: - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on the external 4K screen - do some light web browsing - give focus to the X terminal or gvim // at this point, display is still perfectly steady - press a key to enter a single character // as soon as the key is pressed, external screen goes black for a few seconds. Laptop screen is not affected. - Wait for the screen to come back, then continue typing // screen generally stays ON, but sometimes continues to flicker a few times in next minute. This happens almost every time I switch to the terminal window and start typing. OS specs: - Ubuntu 16.10 running Unity, modesetting Xorg driver - kernel 4.8.0. Issue is still present with 4.9.0rc1. The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11) doesn't exhibit this issue. Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1636486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1266970] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
Sending crash report generated by Apport, with all debug symbols loaded. The stack trace is then more informative, here is an extract: Stacktrace: #0 0x7fc03cf2ee37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7fc03cf30528 in __GI_abort () at abort.c:89 #2 0x7fc03d549b25 in g_assertion_message (domain=domain@entry=0x41ca51 "IBUS", file=file@entry=0x41de90 "panel.c", line=line@entry=2567, func=func@entry=0x41eec0 <__func__.55096> "panel_switch_engine", message=message@entry=0xfc1710 "assertion failed: (i >= 0 && i < m_engines.length)") at /build/buildd/glib2.0-2.42.1/./glib/gtestutils.c:2291 lstr = "2567\000\177\000\000\000H0\251t\322\361\037pJ\000(\300\177\000\000\230\344A\000\000\000\000" s = 0xfc1b50 "" #3 0x7fc03d549bba in g_assertion_message_expr (domain=domain@entry=0x41ca51 "IBUS", file=file@entry=0x41de90 "panel.c", line=line@entry=2567, func=func@entry=0x41eec0 <__func__.55096> "panel_switch_engine", expr=expr@entry=0x41e498 "i >= 0 && i < m_engines.length") at /build/buildd/glib2.0-2.42.1/./glib/gtestutils.c:2306 s = 0xfc1710 "assertion failed: (i >= 0 && i < m_engines.length)" #4 0x0040fe9f in panel_switch_engine (self=0xd81310, i=, force=) at panel.c:2567 #5 0x0041247f in panel_update_engines (self=0xd81310, unowned_engine_names=, unowned_engine_names_length1=, order_names=0xfa3d40, order_names_length1=) at panel.c:3019 #6 0x004130dc in panel_load_settings (self=0xd81310) at panel.c:2459 #7 0x7fc03db02264 in emit_signal_instance_in_idle_cb (data=0x7fc0300081b0) at /build/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:3753 ** Attachment added: "Crash report with debug symbols" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1266970/+attachment/4373711/+files/_usr_lib_ibus_ibus-ui-gtk3.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1266970 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: Confirmed Bug description: Testing x86 xubuntu ISO (jan 07), did login and apport pop-up me with this error. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.3-6ubuntu4 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CasperVersion: 1.336ubuntu1 Date: Wed Jan 8 04:19:45 2014 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 ExecutableTimestamp: 1385564596 LiveMediaBuild: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140107) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/i386-linux-gnu/libibus-1.0.so.5 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1266970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
Hello, there is no more crash since the reboot last week. I needed to wait more because we had a general power failure nearly at the hour where cupsd would usually crash. ( I needed to check your fix didn't cause the power failure :-P ) I think you can set the bug as fixed now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag:
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
My machine will be online the 3 following days and idle. I will see Tuesday if other crashes occurred. If you want I can also reboot the machine before leaving the office (in one hour). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
Here is my '/etc/logrotate.d/cups' file. ** Attachment added: "My /etc/logrotate.d/cups" https://bugs.launchpad.net/ubuntu/quantal/+source/cups/+bug/1086019/+attachment/3679435/+files/cups -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.versio
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
>> ls -l /etc/apport/blacklist.d/cups* ls: impossible d'accéder à /etc/apport/blacklist.d/cups*: Aucun fichier ou dossier de ce type ==> No such file or directory >> ls -l /etc/apport/blacklist.d/* -rw-r--r-- 1 root root 216 oct. 10 2012 /etc/apport/blacklist.d/apport -rw-r--r-- 1 root root 59 oct. 11 2012 /etc/apport/blacklist.d/firefox -rw-r--r-- 1 root root 217 oct. 1 2012 /etc/apport/blacklist.d/README.blacklist -rw-r--r-- 1 root root 71 oct. 11 2012 /etc/apport/blacklist.d/thunderbird -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
I just checked the '/etc/logrotate.d/cups' file and it has the same content as the improved script you provided. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.080305165
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
Here is the crash log found on /var/crash . ** Attachment added: "New crash after having tested the proposed patch (05-17-2013)" https://bugs.launchpad.net/ubuntu/quantal/+source/cups/+bug/1086019/+attachment/3679380/+files/_usr_sbin_cupsd.0.crash.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chass
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
Bad news : I had a cupsd crash this morning. I will try to post the apport crash here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
#25 done via automatic update: it worked but a dialog box asked me whether to replace or not the content of a file like "logrotate.d/cups" (I didn't note it, sorry). The file changes text field was empty. I choose "replace" as recommended by the dialog but if this file is related to the crash maybe the replace should be forced or at least it should be told that 'replace' is needed to fix a crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board A
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
Already did #21 two weeks ago and crashes came back. #22 does not work: cmarin@BAT:~/tmpdir$ sudo dpkg -i --force-confmiss cups-daemon_*.deb dpkg: erreur de traitement de cups-daemon_*.deb (--install) : ne peut pas accéder à l'archive: Aucun fichier ou dossier de ce type Des erreurs ont été rencontrées pendant l'exécution : cups-daemon_*.deb - in english: cannot access to archive: no such file or directory I tried to add a "apt-get download cups-daemon" but it does not work either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Committed Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bi
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
I think I missed something, where do I find the 'proposed package' ? Will automatic update propose it to me? Do I have to upgrade Ubuntu from 12.10 to 13.04 ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: In Progress Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day triggered by logrotate, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package the logrotate script is improved to not take a way log files from CUPS while it is running. It stops CUPS, moves the log files, and after that starts CUPS again. This way CUPS stops crashing during the logrotate once a day, so the system will behave normally now. Printing does not trigger the crash, so print jobs are always executed correctly. You can test whether crash reports still work with the proposed package by triggering an artificial crash running the command sudo killall -11 cupsd Check whether the crash report process of Apport gets triggered, but DO NOT post the generated bug report on Launchpad. Remove /etc/apport/blacklist.d/cups (remainder from earlier proposed package) if this does not happen and try again. [Regression Potential] None. No change in any executable which could cause a regression. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi
[Desktop-packages] [Bug 1075069] Re: cupsd crashed with SIGSEGV in _dbus_list_unlink
*** This bug is a duplicate of bug 1086019 *** https://bugs.launchpad.net/bugs/1086019 ** This bug has been marked a duplicate of bug 1086019 cupsd crashes regularly (daily) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1075069 Title: cupsd crashed with SIGSEGV in _dbus_list_unlink Status in D-Bus: New Status in “cups” package in Ubuntu: Confirmed Bug description: Crash on Resume ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 5 02:04:29 2012 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2012-03-31 (218 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331) Lpstat: device for Canon-MG5100-series: usb://Canon/MG5100%20series?serial=33CD93&interface=1 device for Generic-PCL-6-PCL-XL: socket://192.168.178.3:9100 device for Kyocera-Mita-FS-1350DN-KPDL: ipp://laser:631/ipp device for SipgateFax: sipgatefax://sipgate.de MachineType: LENOVO 6474A46 MarkForUpload: True Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: SipgateFax: SipgateFax Generic-PCL-6-PCL-XL: Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended) Canon-MG5100-series: Canon PIXMA MG5100 - CUPS+Gutenprint v5.2.9 Kyocera-Mita-FS-1350DN-KPDL: Kyocera FS-1350DN (KPDL) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f0aba9ede60:mov0x8(%rsi),%rax PC (0x7f0aba9ede60) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cupsd crashed with SIGSEGV UpgradeStatus: Upgraded to quantal on 2012-08-02 (94 days ago) UserGroups: dmi.bios.date: 04/19/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET86WW (3.16 ) dmi.board.name: 6474A46 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET86WW(3.16):bd04/19/2010:svnLENOVO:pn6474A46:pvrThinkPadT400:rvnLENOVO:rn6474A46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474A46 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO mtime.conffile..etc.cups.cupsd.conf: 2012-10-31T00:20:46.391143 To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1075069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1123121] Re: cupsd crashed with SIGSEGV
*** This bug is a duplicate of bug 1086019 *** https://bugs.launchpad.net/bugs/1086019 ** This bug is no longer a duplicate of bug 1075069 cupsd crashed with SIGSEGV in _dbus_list_unlink ** This bug has been marked a duplicate of bug 1086019 cupsd crashes regularly (daily) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1123121 Title: cupsd crashed with SIGSEGV Status in “cups” package in Ubuntu: New Bug description: This is the message that comes with the Crash notification. I don't know how it affects the system, because printing works. OS is Ubuntu 13.04 ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: cups-daemon 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Uname: Linux 3.2.0-32-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Sun Feb 10 15:46:32 2013 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2012-05-11 (276 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lpstat: device for DCP7030: usb://Brother/DCP-7030?serial=000M9N662992 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0951:1603 Kingston Technology DataTraveler 1GB/2GB Pen Drive MachineType: System manufacturer System Product Name MarkForUpload: True Papersize: a4 PpdFiles: DCP7030: Brother DCP7030 for CUPS ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae root=UUID=37682423-f02c-4f96-987d-1cdc5d614100 ro vga=775 quiet splash ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae root=UUID=37682423-f02c-4f96-987d-1cdc5d614100 ro vga=775 quiet splash SegvAnalysis: Segfault happened at: 0xb7585109:mov0x4(%eax),%edx PC (0xb7585109) ok source "0x4(%eax)" (0x0004) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 ?? () from /lib/i386-linux-gnu/libdbus-1.so.3 Title: cupsd crashed with SIGSEGV UpgradeStatus: Upgraded to raring on 2012-11-25 (79 days ago) UserGroups: dmi.bios.date: 01/15/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd01/15/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.cups.cupsd.conf: 2012-12-29T21:28:56.007627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1123121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1158868] Re: cupsd crashed with SIGSEGV
*** This bug is a duplicate of bug 1086019 *** https://bugs.launchpad.net/bugs/1086019 ** This bug is no longer a duplicate of bug 1075069 cupsd crashed with SIGSEGV in _dbus_list_unlink ** This bug has been marked a duplicate of bug 1086019 cupsd crashes regularly (daily) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1158868 Title: cupsd crashed with SIGSEGV Status in “cups” package in Ubuntu: New Bug description: happens on update ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: cups-daemon 1.6.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Fri Mar 22 17:33:57 2013 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2012-03-31 (355 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331) Lpstat: device for Kyocera-Mita-FS-1350DN-KPDL: ipp://laser:631/ipp device for MP280-series: usb://Canon/MP280%20series?serial=71DACC&interface=1 device for SipgateFax: sipgatefax://sipgate.de MachineType: LENOVO 6474A46 MarkForUpload: True Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: SipgateFax: SipgateFax MP280-series: Canon PIXMA MP280 - CUPS+Gutenprint v5.2.9 Kyocera-Mita-FS-1350DN-KPDL: Kyocera FS-1350DN (KPDL) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7ffcd65c8ec0:mov0x8(%rsi),%rax PC (0x7ffcd65c8ec0) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cupsd crashed with SIGSEGV UpgradeStatus: Upgraded to raring on 2013-01-23 (58 days ago) UserGroups: dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474A46 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474A46:pvrThinkPadT400:rvnLENOVO:rn6474A46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474A46 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1158868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
Hi, It is now Tuesday and cupsd has not crashed since I replaced '/etc/logrotate.d/cups' , my machine was online all the week end. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: In Progress Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package these crash reports are suppressed. CUPS is still crashing once a day, but Upstart restarts it and no crash report appears. So the system appears to behave normally. The crash is of no harm, it is probably triggered by cron job action during the night and due to Upstart restarting CUPS CUPS is always present. Printing does not trigger the crash, so print jobs are always executed correctly. [Regression Potential] None. No change in any executable which could cause a regression. Only disadvantage is that not yet discovered crashes for other reasons do not get visible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bug
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
cupsd crashes nearly everyday on my machine. I just replaced /etc/logrotate.d/cups by your file and I will tell you Monday whether the crash still occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: In Progress Status in “cups-filters” source package in Quantal: Invalid Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). [IMPACT] For CUPS users who activate the "Show printers shared by other systems" in the server settings of system-config-printer or in the CUPS web interface, so that they automatically get shared remote CUPS printers listed in print dialogs CUPS crashes regularly, typically once a day, popping up an Apport dialog to upload the crash info to Launchpad. Otherwise all is working correctly, there is only the annoying crash report. [TESTCASE] Activate "Show printers shared by other systems" in the server settings of system-config-printer or run the command cupsctl --remote-printers I am not sure whether there must be actually a remote printer to trigger the crash. So on another computer in the same local network (or on a virtual machine if you do not have a second computer) create a CUPS queue and share it. Activate "Published shared printers connected to this system" in the server settings of system-config- printer or run the command cupsctl --share-printers on that computer. Now observe for some days. Probably you will get a crash report once a day. With the proposed package these crash reports are suppressed. CUPS is still crashing once a day, but Upstart restarts it and no crash report appears. So the system appears to behave normally. The crash is of no harm, it is probably triggered by cron job action during the night and due to Upstart restarting CUPS CUPS is always present. Printing does not trigger the crash, so print jobs are always executed correctly. [Regression Potential] None. No change in any executable which could cause a regression. Only disadvantage is that not yet discovered crashes for other reasons do not get visible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=15433 comm="apparmor_parser" Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=15433 comm="apparmor_parser" MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this
[Desktop-packages] [Bug 1075069] Re: cupsd crashed with SIGSEGV in _dbus_list_unlink
May be related to bug 1089523, cupsd regularly crashes on my machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1075069 Title: cupsd crashed with SIGSEGV in _dbus_list_unlink Status in D-Bus: New Status in “cups” package in Ubuntu: Confirmed Bug description: Crash on Resume ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 5 02:04:29 2012 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2012-03-31 (218 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331) Lpstat: device for Canon-MG5100-series: usb://Canon/MG5100%20series?serial=33CD93&interface=1 device for Generic-PCL-6-PCL-XL: socket://192.168.178.3:9100 device for Kyocera-Mita-FS-1350DN-KPDL: ipp://laser:631/ipp device for SipgateFax: sipgatefax://sipgate.de MachineType: LENOVO 6474A46 MarkForUpload: True Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: SipgateFax: SipgateFax Generic-PCL-6-PCL-XL: Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended) Canon-MG5100-series: Canon PIXMA MG5100 - CUPS+Gutenprint v5.2.9 Kyocera-Mita-FS-1350DN-KPDL: Kyocera FS-1350DN (KPDL) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f0aba9ede60:mov0x8(%rsi),%rax PC (0x7f0aba9ede60) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cupsd crashed with SIGSEGV UpgradeStatus: Upgraded to quantal on 2012-08-02 (94 days ago) UserGroups: dmi.bios.date: 04/19/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET86WW (3.16 ) dmi.board.name: 6474A46 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET86WW(3.16):bd04/19/2010:svnLENOVO:pn6474A46:pvrThinkPadT400:rvnLENOVO:rn6474A46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474A46 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO mtime.conffile..etc.cups.cupsd.conf: 2012-10-31T00:20:46.391143 To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1075069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1089523] Re: cupsd crashed with SIGSEGV in _dbus_header_get_byte_order()
May be related to bug 1075069, cupsd regularly crashes on my machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1089523 Title: cupsd crashed with SIGSEGV in _dbus_header_get_byte_order() Status in “cups” package in Ubuntu: Confirmed Bug description: This was reported when I reacted on update message to install upgrades. If this was coincidental, I don't know. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-20.31-generic 3.5.7.1 Uname: Linux 3.5.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CupsErrorLog: E [12/Dec/2012:18:27:38 +0100] Unknown directive SystemGroup on line 16 of /etc/cups/cupsd.conf. E [12/Dec/2012:18:57:03 +0100] Unknown directive SystemGroup on line 16 of /etc/cups/cupsd.conf. Date: Wed Dec 12 18:57:03 2012 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2010-10-14 (789 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Lpstat: device for hplaser@ws1: ipp://192.168.5.201:631/printers/hplaser device for lexmark@ws1: ipp://192.168.5.201:631/printers/lexmark Lsusb: Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 056d:0002 EIZO Corp. HID Monitor Controls MachineType: MSI MS-7366 MarkForUpload: True Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.5.0-20-generic root=UUID=680229a7-f19e-4afc-a959-88e7c07ebdc9 ro quiet splash ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-20-generic root=UUID=680229a7-f19e-4afc-a959-88e7c07ebdc9 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fe51a1577a3:movzbl (%rax),%eax PC (0x7fe51a1577a3) ok source "(%rax)" (0x00be) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cupsd crashed with SIGSEGV in dbus_message_get_reply_serial() UpgradeStatus: Upgraded to quantal on 2012-10-06 (67 days ago) UserGroups: dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7366 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd07/08/2008:svnMSI:pnMS-7366:pvr1.0:rvnMSI:rnMS-7366:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7366 dmi.product.version: 1.0 dmi.sys.vendor: MSI mtime.conffile..etc.cups.cupsd.conf: 2012-10-20T16:36:26.698540 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1089523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075069] Re: cupsd crashed with SIGSEGV
** Also affects: dbus Importance: Undecided Status: New ** Summary changed: - cupsd crashed with SIGSEGV + cupsd crashed with SIGSEGV in _dbus_list_unlink -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1075069 Title: cupsd crashed with SIGSEGV in _dbus_list_unlink Status in D-Bus: New Status in “cups” package in Ubuntu: Confirmed Bug description: Crash on Resume ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 5 02:04:29 2012 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2012-03-31 (218 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331) Lpstat: device for Canon-MG5100-series: usb://Canon/MG5100%20series?serial=33CD93&interface=1 device for Generic-PCL-6-PCL-XL: socket://192.168.178.3:9100 device for Kyocera-Mita-FS-1350DN-KPDL: ipp://laser:631/ipp device for SipgateFax: sipgatefax://sipgate.de MachineType: LENOVO 6474A46 MarkForUpload: True Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: SipgateFax: SipgateFax Generic-PCL-6-PCL-XL: Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended) Canon-MG5100-series: Canon PIXMA MG5100 - CUPS+Gutenprint v5.2.9 Kyocera-Mita-FS-1350DN-KPDL: Kyocera FS-1350DN (KPDL) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=b32d85c9-d1fb-49ca-8c94-c64d321221b3 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f0aba9ede60:mov0x8(%rsi),%rax PC (0x7f0aba9ede60) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cupsd crashed with SIGSEGV UpgradeStatus: Upgraded to quantal on 2012-08-02 (94 days ago) UserGroups: dmi.bios.date: 04/19/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET86WW (3.16 ) dmi.board.name: 6474A46 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET86WW(3.16):bd04/19/2010:svnLENOVO:pn6474A46:pvrThinkPadT400:rvnLENOVO:rn6474A46:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6474A46 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO mtime.conffile..etc.cups.cupsd.conf: 2012-10-31T00:20:46.391143 To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1075069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
