[Desktop-packages] [Bug 2028006] [NEW] ps2ascii man page is wrong about PDFs on standard input
Public bug reported: The ps2ascii man page says: "PDF input must come from an explicitly- named file, not standard input." This is incorrect. ps2ascii is perfectly happy to read a PDF from standard input: cat file.pdf | ps2ascii ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ghostscript 9.55.0~dfsg1-0ubuntu5.3 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 17 13:52:48 2023 InstallationDate: Installed on 2020-02-29 (1234 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ghostscript UpgradeStatus: Upgraded to jammy on 2022-12-03 (225 days ago) ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/2028006 Title: ps2ascii man page is wrong about PDFs on standard input Status in ghostscript package in Ubuntu: New Bug description: The ps2ascii man page says: "PDF input must come from an explicitly- named file, not standard input." This is incorrect. ps2ascii is perfectly happy to read a PDF from standard input: cat file.pdf | ps2ascii ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ghostscript 9.55.0~dfsg1-0ubuntu5.3 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 17 13:52:48 2023 InstallationDate: Installed on 2020-02-29 (1234 days ago) InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ghostscript UpgradeStatus: Upgraded to jammy on 2022-12-03 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/2028006/+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 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display
I switched from nouveau to the proprietary nvidia driver (nvidia-375), and the crashes have stopped. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: A few hours after upgrading to the latest kernel and plasma (using apt upgrade) in Xenial 16.04LTS, my computer display hung with: Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] on channel 2 [007f9a3000 Xorg[1501]] Feb 2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: gr engine fault on channel 2, recovering... Feb 2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed to get session [pid 27934]: No such device or address Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: sw engine fault on channel 8, recovering... Feb 2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: runlist 0 update timeout Feb 2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] ...repeats many times... I could still log in via SSH but could not unhang the system, so I rebooted. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 2 23:20:22 2017 InstallationDate: Installed on 2016-09-25 (131 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+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 1658185] Re: nouveau occasionally won't come back from DPMS suspend/off
David, by any chance, are you running VMware Workstation when these problems happen? My computer has similar symptoms, and when I ssh in, VMware Workstation seems to be in an odd state. I can't suspend my VMs from the command line (in preparation for a reboot of the host). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1658185 Title: nouveau occasionally won't come back from DPMS suspend/off Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: On several occasions over the past few months, I've moved my mouse or pressed a key to wake my monitor from power saving, but the monitor never leaves power saving. I can still ssh into the machine. The GPU is GK104 [GeForce GTX 770] (as reported by lshw). On this occasion, at least, the syslog contained the following errors: kernel: [53037.908926] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] kernel: [53037.908932] nouveau :01:00.0: fifo: gr engine fault on channel 7, recovering... kernel: [53037.909454] nouveau :01:00.0: fifo: write fault at 001e444000 engine 00 [GR] client 0f [GPC2/PROP_0] reason 02 [PTE] on channel 5 [00ff534000 compiz[5762]] kernel: [53037.909457] nouveau :01:00.0: fifo: gr engine fault on channel 5, recovering... Xorg.0.log.old ends with these un-timestamped errors that may or may not be related: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x55919392a9fa] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55919390c4b3] (EE) 2: /usr/lib/xorg/Xorg (QueueKeyboardEvents+0x52) [0x5591937dc902] (EE) 3: /usr/lib/xorg/Xorg (xf86PostKeyboardEvent+0x3b) [0x5591938162db] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x63cf) [0x7f3a1e4043cf] (EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x6a8d) [0x7f3a1e404a8d] (EE) 6: /usr/lib/xorg/Xorg (0x559193771000+0x95438) [0x559193806438] (EE) 7: /usr/lib/xorg/Xorg (0x559193771000+0xba8f2) [0x55919382b8f2] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3a278b8000+0x35860) [0x7f3a278ed860] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f3a279b58b5] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f3a28c990f8] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f3a28c9bdbb] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) [0x7f3a237c403c] (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xc839) [0x7f3a239d5839] (EE) 14: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xd25d) [0x7f3a239d625d] (EE) 15: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x5591938fd398] (EE) 16: /usr/lib/xorg/Xorg (0x559193771000+0x18dc6d) [0x5591938fec6d] (EE) 17: /usr/lib/xorg/Xorg (0x559193771000+0x533bf) [0x5591937c43bf] (EE) 18: /usr/lib/xorg/Xorg (0x559193771000+0x57413) [0x5591937c8413] (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f3a278d83f1] (EE) 20: /usr/lib/xorg/Xorg (_start+0x2a) [0x5591937b233a] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x55919392a9fa] (EE) 1: /usr/lib/xorg/Xorg (QueueKeyboardEvents+0x52) [0x5591937dc902] (EE) 2: /usr/lib/xorg/Xorg (xf86PostKeyboardEvent+0x3b) [0x5591938162db] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x63cf) [0x7f3a1e4043cf] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f3a1e3fe000+0x6a8d) [0x7f3a1e404a8d] (EE) 5: /usr/lib/xorg/Xorg (0x559193771000+0x95438) [0x559193806438] (EE) 6: /usr/lib/xorg/Xorg (0x559193771000+0xba8f2) [0x55919382b8f2] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3a278b8000+0x35860) [0x7f3a278ed860] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f3a279b58b5] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f3a28c990f8] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f3a28c9bdbb] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) [0x7f3a237c403c] (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xc839) [0x7f3a239d5839] (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f3a239c9000+0xd25d) [0x7f3a239d625d] (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x5591938fd398] (EE) 15: /usr/lib/xorg/Xorg (0x559193771000+0x18dc6d) [0x5591938fec6d] (EE) 16: /usr/lib/xorg/Xorg (0x559193771000+0x533bf) [0x5591937c43bf] (EE) 17: /usr/lib/xorg/Xorg (0x559193771000+0x57413) [0x5591937c8413] (EE)
[Desktop-packages] [Bug 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display
This crash is now happening daily, ever since the latest plasma upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: A few hours after upgrading to the latest kernel and plasma (using apt upgrade) in Xenial 16.04LTS, my computer display hung with: Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] on channel 2 [007f9a3000 Xorg[1501]] Feb 2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: gr engine fault on channel 2, recovering... Feb 2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed to get session [pid 27934]: No such device or address Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: sw engine fault on channel 8, recovering... Feb 2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: runlist 0 update timeout Feb 2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] ...repeats many times... I could still log in via SSH but could not unhang the system, so I rebooted. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 2 23:20:22 2017 InstallationDate: Installed on 2016-09-25 (131 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+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 1661486] [NEW] nouveau write fault, CTXSW_TIMEOUT, hangs the display
Public bug reported: A few hours after upgrading to the latest kernel and plasma (using apt upgrade) in Xenial 16.04LTS, my computer display hung with: Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] on channel 2 [007f9a3000 Xorg[1501]] Feb 2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: gr engine fault on channel 2, recovering... Feb 2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed to get session [pid 27934]: No such device or address Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: sw engine fault on channel 8, recovering... Feb 2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: runlist 0 update timeout Feb 2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] ...repeats many times... I could still log in via SSH but could not unhang the system, so I rebooted. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 2 23:20:22 2017 InstallationDate: Installed on 2016-09-25 (131 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: A few hours after upgrading to the latest kernel and plasma (using apt upgrade) in Xenial 16.04LTS, my computer display hung with: Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] on channel 2 [007f9a3000 Xorg[1501]] Feb 2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: gr engine fault on channel 2, recovering... Feb 2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed to get session [pid 27934]: No such device or address Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: sw engine fault on channel 8, recovering... Feb 2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: runlist 0 update timeout Feb 2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] ...repeats many times... I could still log in via SSH but could not unhang the system, so I rebooted. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 2 23:20:22 2017 InstallationDate: Installed on 2016-09-25 (131 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus"
[Desktop-packages] [Bug 1628707] Re: Highlighting a region in emacs is invisible because region color equals window color
It's possible that some X resource hidden in my account is setting the background color. Can someone please tell me where to look for these resource settings? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1628707 Title: Highlighting a region in emacs is invisible because region color equals window color Status in emacs24 package in Ubuntu: New Bug description: If you open an Emacs window in Plasma/KDE, and you try to highlight a region of text by dragging the mouse, no highlighting appears. This is because the color for highlighting a region is identical to the color for the window background. I believe this color clash occurs between Ubuntu's emacs24 package and Ubuntu's X resource settings. To reproduce, log into Plasma, remove your $HOME/.emacs init file (so you have no personal customizations), and run emacs in an X window: $ emacs The window's background color is a light gray. Then type any text, click and drag the mouse over the text (or use keystroke commands to define a region). No highlighting appears, because the "region" color is also light gray. You can see this by running the emacs command: M-x list-faces-display I'll attach a screenshot so you can see that the "region" highlighting doesn't show up. The problem goes away if you disable the Ubuntu-supplied emacs init files: $ emacs -Q This is why I suspect the color is set badly in the Ubuntu emacs24 package. You can see the X background color by running the "appres" command in a shell window, which proves a light gray background is set, the same color as region highlighting: *background:#eff0f1 I tried to find the file where this background color is set, but I was not successful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 28 18:07:25 2016 InstallationDate: Installed on 2016-09-25 (3 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1628707/+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 1628707] [NEW] Highlighting a region in emacs is invisible because region color equals window color
Public bug reported: If you open an Emacs window in Plasma/KDE, and you try to highlight a region of text by dragging the mouse, no highlighting appears. This is because the color for highlighting a region is identical to the color for the window background. I believe this color clash occurs between Ubuntu's emacs24 package and Ubuntu's X resource settings. To reproduce, log into Plasma, remove your $HOME/.emacs init file (so you have no personal customizations), and run emacs in an X window: $ emacs The window's background color is a light gray. Then type any text, click and drag the mouse over the text (or use keystroke commands to define a region). No highlighting appears, because the "region" color is also light gray. You can see this by running the emacs command: M-x list-faces-display I'll attach a screenshot so you can see that the "region" highlighting doesn't show up. The problem goes away if you disable the Ubuntu-supplied emacs init files: $ emacs -Q This is why I suspect the color is set badly in the Ubuntu emacs24 package. You can see the X background color by running the "appres" command in a shell window, which proves a light gray background is set, the same color as region highlighting: *background:#eff0f1 I tried to find the file where this background color is set, but I was not successful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 28 18:07:25 2016 InstallationDate: Installed on 2016-09-25 (3 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs24 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "The "region" face shows no highlighting" https://bugs.launchpad.net/bugs/1628707/+attachment/4750558/+files/region.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1628707 Title: Highlighting a region in emacs is invisible because region color equals window color Status in emacs24 package in Ubuntu: New Bug description: If you open an Emacs window in Plasma/KDE, and you try to highlight a region of text by dragging the mouse, no highlighting appears. This is because the color for highlighting a region is identical to the color for the window background. I believe this color clash occurs between Ubuntu's emacs24 package and Ubuntu's X resource settings. To reproduce, log into Plasma, remove your $HOME/.emacs init file (so you have no personal customizations), and run emacs in an X window: $ emacs The window's background color is a light gray. Then type any text, click and drag the mouse over the text (or use keystroke commands to define a region). No highlighting appears, because the "region" color is also light gray. You can see this by running the emacs command: M-x list-faces-display I'll attach a screenshot so you can see that the "region" highlighting doesn't show up. The problem goes away if you disable the Ubuntu-supplied emacs init files: $ emacs -Q This is why I suspect the color is set badly in the Ubuntu emacs24 package. You can see the X background color by running the "appres" command in a shell window, which proves a light gray background is set, the same color as region highlighting: *background:#eff0f1 I tried to find the file where this background color is set, but I was not successful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 28 18:07:25 2016 InstallationDate: Installed on 2016-09-25 (3 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1628707/+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 1223291] Re: "sudo emacs" cannot be backgrounded afterward by shell
This appears to be fixed as of Ubuntu 15.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell Status in emacs23 package in Ubuntu: New Bug description: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as "^Z". This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+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 1223291] Re: "sudo emacs" cannot be backgrounded afterward by shell
I would close this if I could. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell Status in emacs23 package in Ubuntu: New Bug description: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as "^Z". This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+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 1515829] Re: Gimp tooltip text color is white on white
Thank you, antonio -- your workaround in comment #3 fixed the problem for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1515829 Title: Gimp tooltip text color is white on white Status in gimp package in Ubuntu: New Bug description: In the gimp toolbox, when I hover my mouse over a tool, the tooltip that pops up has white text on a white background. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gimp 2.8.14-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 20:18:16 2015 InstallationDate: Installed on 2013-08-31 (803 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gimp UpgradeStatus: Upgraded to wily on 2015-11-08 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1515829/+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 1517030] [NEW] ubuntu-bug (apport-kde) crashes every time I submit a problem report
Public bug reported: Every time I run the "ubuntu-bug" program, I get a crash report about it. 1. I run (say) "ubuntu-bug muon-updater" 2. Apport window appears, "Send problem report to developers?" with info about the bug. 3. Click Send. 4. "Uploading problem information" dialog appears and disappears. 5. Launchpad website appears. I start filing in details. 6. Sometime soon, Plasma reports a crash in its system tray. A dialog appears. See my screenshot. 7. I click the "Continue" button to submit a crash bug report. The dialog disappears, but nothing else happens that I can see. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 17 07:51:26 2015 InstallationDate: Installed on 2013-08-31 (807 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-11-08 (8 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Dialog that appears after apport-kde crash" https://bugs.launchpad.net/bugs/1517030/+attachment/4520579/+files/dialog.png ** Summary changed: - ubuntu-bug crashes every time I submit a problem report + ubuntu-bug (apport-kde) crashes every time I submit a problem report -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report Status in apport package in Ubuntu: New Bug description: Every time I run the "ubuntu-bug" program, I get a crash report about it. 1. I run (say) "ubuntu-bug muon-updater" 2. Apport window appears, "Send problem report to developers?" with info about the bug. 3. Click Send. 4. "Uploading problem information" dialog appears and disappears. 5. Launchpad website appears. I start filing in details. 6. Sometime soon, Plasma reports a crash in its system tray. A dialog appears. See my screenshot. 7. I click the "Continue" button to submit a crash bug report. The dialog disappears, but nothing else happens that I can see. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 17 07:51:26 2015 InstallationDate: Installed on 2013-08-31 (807 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-11-08 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+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 1515829] [NEW] Gimp tooltip text color is white on white
Public bug reported: In the gimp toolbox, when I hover my mouse over a tool, the tooltip that pops up has white text on a white background. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gimp 2.8.14-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 20:18:16 2015 InstallationDate: Installed on 2013-08-31 (803 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gimp UpgradeStatus: Upgraded to wily on 2015-11-08 (4 days ago) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Demonstrating the text color problem" https://bugs.launchpad.net/bugs/1515829/+attachment/4517907/+files/bug2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1515829 Title: Gimp tooltip text color is white on white Status in gimp package in Ubuntu: New Bug description: In the gimp toolbox, when I hover my mouse over a tool, the tooltip that pops up has white text on a white background. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gimp 2.8.14-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 20:18:16 2015 InstallationDate: Installed on 2013-08-31 (803 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gimp UpgradeStatus: Upgraded to wily on 2015-11-08 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1515829/+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 1223291] Re: sudo emacs cannot be backgrounded afterward by shell
Confirming that this is still broken in Saucy Salamander. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: sudo emacs cannot be backgrounded afterward by shell Status in “emacs23” package in Ubuntu: New Bug description: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as ^Z. This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP pid of emacs but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+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 1223291] Re: sudo emacs cannot be backgrounded afterward by shell
Sorry, I made a typo in my report. The command: $ sudo emacs gnome-terminal should be: $ sudo gnome-terminal ** Description changed: When I run: - $ sudo emacs /etc/myfile + $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as ^Z. This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: - $ sudo emacs -nw /etc/myfile(which runs emacs in the existing gnome-terminal window) - $ sudo emacs gnome-terminal (a different program that also opens a window) + $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) + $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: - $ sudo kill -TSTP pid of emacs + $ sudo kill -TSTP pid of emacs but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: sudo emacs cannot be backgrounded afterward by shell Status in “emacs23” package in Ubuntu: New Bug description: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as ^Z. This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP pid of emacs but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+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 1223291] [NEW] sudo emacs cannot be backgrounded afterward by shell
Public bug reported: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as ^Z. This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP pid of emacs but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs23 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: sudo emacs cannot be backgrounded afterward by shell Status in “emacs23” package in Ubuntu: New Bug description: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as ^Z. This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP pid of emacs but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+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 1222137] [NEW] gnome-screensaver emits repeated error, gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed
Public bug reported: I found this 20+ times in .xsession-errors after leaving the screensaver running overnight. (gnome-screensaver:5633): Gtk-CRITICAL **: gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Sep 7 08:24:38 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-08-31 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1222137 Title: gnome-screensaver emits repeated error, gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed Status in “gnome-screensaver” package in Ubuntu: New Bug description: I found this 20+ times in .xsession-errors after leaving the screensaver running overnight. (gnome-screensaver:5633): Gtk-CRITICAL **: gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Sep 7 08:24:38 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-08-31 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1222137/+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 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
I can confirm this error message occurs in Ubuntu 13.04 64-bit while running VMware Workstation 10, each time that the mouse pointer crosses onto, or off of, the VMware window. (gnome-settings-daemon:5101): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed However, my CPU does not spike to 100%, at least as far as I can tell. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) Status in Gnome Settings Daemon: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “gnome-settings-daemon” package in Fedora: Unknown Bug description: Impact: gnome-settings-daemon uses 100% cpu for ever in some cases Test Case: Seems to happen sometimes after docking or connecting with vnc, try to connect to the machine using a vnc client a few times and check there is no numlock cycle and cpu usage loop starting Regression potential: The numlock state could be wrongly set,restored on login in some cases - Original message: - I don't know how to reproduce this bug, but after varying amounts of normal usage of my laptop, I notice gnome-settings-daemon is consuming 100% (approx) CPU. I am not sure how to restart gnome-settings-daemon, I tried opening a terminal and running gnome-settings-daemon again but this crashes my system - my external monitor switches off and my laptop locks up. I am able to reboot with SysRq+REISUB. Sorry I cannot provide more information - it happens twice now, maybe someone can tell me how to get more information for the next time this happens. $ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 $ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.4.0-0ubuntu2 Candidate: 3.4.0-0ubuntu2 Version table: *** 3.4.0-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 17:16:02 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+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
