[Bug 1823958] [NEW] xetex/xdvipdfmx produce invalid PDFs → update
Public bug reported:
Hi,
I ran into an issue similar to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=907784. I have a large document (a Beamer
presentation with more than 100 frames) that I compile using
XeLaTeX/latexmk.
The document compiles without issue, producing a valid PDF. However, if
I add only:
\begin{frame}{Frame title}
\end{frame}
at a certain point, the result is a PDF file that is malformed
(according to evince, pdfinfo, etc.)
Finding the above Debian bug report, I downloaded texlive-
binaries_2018.20181218.49446-1_amd64.deb (from debian testing), and
extracted only the xdvipdfmx executable into ~/.local/bin. With this
executable, my modified file also compiles without error.
I suppose the fix is to update the version of texlive-binaries, or at
least xdvipdfmx, in 18.10.
$ lsb_release -rd && apt-cache policy texlive-binaries
Description:Ubuntu 18.10
Release:18.10
texlive-binaries:
Installed: 2018.20180824.48463-1ubuntu0.1
Candidate: 2018.20180824.48463-1ubuntu0.1
Version table:
*** 2018.20180824.48463-1ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64
Packages
100 /var/lib/dpkg/status
2018.20180824.48463-1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: texlive-binaries 2018.20180824.48463-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 15:16:09 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-11 (544 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: texlive-bin
UpgradeStatus: Upgraded to cosmic on 2018-11-11 (148 days ago)
** Affects: texlive-bin (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823958
Title:
xetex/xdvipdfmx produce invalid PDFs → update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1823958/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
This sounds very much like what I tried to describe in #1826219; also on a Dell XPS 13. Subscribing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
@djcater this is a Dell XPS 13 9360 (not -80)—slightly older (2017 or 2018). Also seeing this third bug which echoes some of my symptoms: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888517] Re: gnome-shell segfaults on idle
** Attachment added: "journalctl-2.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+attachment/5394899/+files/journalctl-2.txt ** Description changed: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - - Setting "org.gnome.desktop.session idle-delay" set to a small value, like 30. + - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f - Despite the different symptoms, this occurs 100% of the time. - $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: - Installed: 3.36.2-1ubuntu1~20.04.1 - Candidate: 3.36.3-1ubuntu1~20.04.2 - Version table: - 3.36.3-1ubuntu1~20.04.2 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - *** 3.36.2-1ubuntu1~20.04.1 100 - 100 /var/lib/dpkg/status - 3.36.1-5ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 3.36.2-1ubuntu1~20.04.1 + Candidate: 3.36.3-1ubuntu1~20.04.2 + Version table: + 3.36.3-1ubuntu1~20.04.2 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + *** 3.36.2-1ubuntu1~20.04.1 100 + 100 /var/lib/dpkg/status + 3.36.1-5ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888517 Title: gnome-shell segfaults on idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888517] [NEW] gnome-shell segfaults on idle
Public bug reported: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f Despite the different symptoms, this occurs 100% of the time. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: 3.36.3-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.2-1ubuntu1~20.04.1 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1888517/+attachment/5394898/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888517 Title: gnome-shell segfaults on idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888517] Re: gnome-shell segfaults on idle
Ah, sorry—I just noticed & tried the version in focal-updates (3.36.3-1ubuntu1~20.04.2), and the issue is no longer reproducible. It must have been specific to 3.36.2-1ubuntu1~20.04.1. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888517 Title: gnome-shell segfaults on idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
** Attachment added: "lspci-k.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+attachment/5259336/+files/lspci-k.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+attachment/5259337/+files/glxinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826604] [NEW] Extension causes saving files to desktop to be slow
Public bug reported: To reproduce: 1. Create a text file (foo.txt) on the desktop and open in gedit. 2. Type a few lines in the file and save it. Expected: the file saves more or less instantly. Observed: - The file takes several seconds to save. - The following lines appear in the journal: Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: fileItem is null _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17 _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89 Notes: - Repeating #1 and #2 with a file that is in another folder (i.e., not on the desktop), the file saves instantly, and the log messages do not appear. - This might be a duplicate/alternate description of #1816205. - Discovered while trying to diagnose #1826219. $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons Description:Ubuntu 19.04 Release:19.04 gnome-shell-extension-desktop-icons: Installed: 19.01.1-1 Candidate: 19.01.1-1 Version table: *** 19.01.1-1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.1-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 22:24:04 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (562 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago) ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826604 Title: Extension causes saving files to desktop to be slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
Thanks! My searches before filing the bug suggested that the log messages were symptoms, but I was unable to find any guideline on how to diagnose further. I've uninstalled gsconnect (both the Gnome extension, and the accompanying Chrome extension), and fully rebooted. The locks still occur. Some extra information: 1. In trying to pin down the cause, I… - Uninstalled zeitgeist - Disabled tracker: https://gist.github.com/vancluever/d34b41eb77e6d077887c#non-invasive-disable-cheat-sheet Neither of these made a difference. 2. I also identified what seems to be a separate issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/+bug/1826604 3. Finally, I notice differences between the bug in the default 'Ubuntu' session and the 'Ubuntu on Wayland' session. The initial bug report, above, was from 'Ubuntu on Wayland'. In the default 'Ubuntu' session: - The display and keyboard input lock, but the mouse cursor can still be moved. - The 'Key repeat discarded' and 'libinput error' log messages do not occur. Other symptoms (e.g. CPU usage spike for gnome-shell) are the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826604] Re: Extension causes saving files to desktop to be slow
Done. ** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues #120 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/120 ** Also affects: gnome-shell-extension-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/120 Importance: Unknown Status: Unknown ** Description changed: To reproduce: 1. Create a text file (foo.txt) on the desktop and open in gedit. 2. Type a few lines in the file and save it. Expected: the file saves more or less instantly. Observed: - The file takes several seconds to save. - The following lines appear in the journal: Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: fileItem is null - _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17 - _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89 - + _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17 + _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89 Notes: - Repeating #1 and #2 with a file that is in another folder (i.e., not on the desktop), the file saves instantly, and the log messages do not appear. - - This might be a duplicate/alternate description of #1816205. - - Discovered while trying to diagnose #1826219. + - This might be a duplicate/alternate description of lp#1816205. + - Discovered while trying to diagnose lp#1826219. - - $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons + $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons Description:Ubuntu 19.04 Release:19.04 gnome-shell-extension-desktop-icons: - Installed: 19.01.1-1 - Candidate: 19.01.1-1 - Version table: - *** 19.01.1-1 500 - 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 19.01.1-1 + Candidate: 19.01.1-1 + Version table: + *** 19.01.1-1 500 + 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.1-1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 22:24:04 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (562 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826604 Title: Extension causes saving files to desktop to be slow To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
More information, as this continues to occur: - If I have audio playing (e.g. streaming music in Chrome) then the audio continues to play smoothly while the input and display lock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] [NEW] Input locks frequently/high CPU usage after 18.10->19.04 upgrade
Public bug reported: I recently upgraded from 18.10 to 19.04. What I expected to happen: same performance as before. What happens instead: - I experience frequent locks of input lasting from 0.5–5 seconds, during which: - The mouse cannot be moved or clicked. - Any pressed key is repeated for the duration of the lock. Various events seem to trigger the locks: - Typing this bug report in Google Chrome (locks for 0.5 s every ~20–30 s). - Changing tabs in Google Chrome (locks for 0.5 s). - Changing tabs in the Atom editor (locks for 1–5 s). - Typing in gedit with no other applications running (locks for ~0.5s). Accompanying symptoms: - CPU usage for gnome-shell is high: - Always around 20% - Appears to spike to 100% for longer locks (from eyeballing htop open in gnome-terminal) - The following appear in 'journalctl -f': Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: last_user_time (169670562) is greater than comparison timestamp (169670067). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: 0x181 appears to be one of the offending windows with a timestamp of 169670562. Working around... Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: W1369 appears to be one of the offending windows with a timestamp of 1798201456. Working around... - The following also appear: Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: client bug: timer event20 debounce: offset negative (-313ms) Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: client bug: timer event20 debounce short: offset negative (-326ms) $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 19.04 Release:19.04 gnome-shell: Installed: 3.32.0+git20190410-1ubuntu1 Candidate: 3.32.0+git20190410-1ubuntu1 Version table: *** 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:52:32 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (559 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (2 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
** Description changed: I recently upgraded from 18.10 to 19.04. What I expected to happen: same performance as before. What happens instead: - I experience frequent locks of input lasting from 0.5–5 seconds, during which: - - The mouse cannot be moved or clicked. - - Any pressed key is repeated for the duration of the lock. + - The mouse cannot be moved or clicked. + - Any pressed key is repeated for the duration of the lock. Various events seem to trigger the locks: - Typing this bug report in Google Chrome (locks for 0.5 s every ~20–30 s). - Changing tabs in Google Chrome (locks for 0.5 s). - Changing tabs in the Atom editor (locks for 1–5 s). - (I will test without other applications running after filing this bug and comment with more events.) - + - Typing in gedit with no other applications running (locks for ~0.5s). Accompanying symptoms: - CPU usage for gnome-shell is high: - - Always around 20% - - Appears to spike to 100% for longer locks (from eyeballing htop open in gnome-terminal) + - Always around 20% + - Appears to spike to 100% for longer locks (from eyeballing htop open in gnome-terminal) - The following appear in 'journalctl -f': - Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! + Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: last_user_time (169670562) is greater than comparison timestamp (169670067). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... - Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: 0x181 appears to be one of the offending windows with a timestamp of 169670562. Working around... - Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: W1369 appears to be one of the offending windows with a timestamp of 1798201456. Working around... + Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: 0x181 appears to be one of the offending windows with a timestamp of 169670562. Working around... + Apr 24 15:57:30 khaeru-laptop org.gnome.Shell.desktop[31679]: Window manager warning: W1369 appears to be one of the offending windows with a timestamp of 1798201456. Working around... - The following also appear: Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: client bug: timer event20 debounce: offset negative (-313ms) Apr 24 15:59:59 khaeru-laptop org.gnome.Shell.desktop[31679]: libinput error: client bug: timer event20 debounce short: offset negative (-326ms) - $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 19.04 Release:19.04 gnome-shell: - Installed: 3.32.0+git20190410-1ubuntu1 - Candidate: 3.32.0+git20190410-1ubuntu1 - Version table: - *** 3.32.0+git20190410-1ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.32.0+git20190410-1ubuntu1 + Candidate: 3.32.0+git20190410-1ubuntu1 + Version table: + *** 3.32.0+git20190410-1ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:52:32 2019 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (559 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826219] Re: Input locks frequently/high CPU usage after 18.10->19.04 upgrade
The lock also occurs when using claws-mail. I pressed [Delete] in a message list, and the lock caused that keypress to be repeated, deleting about a dozen messages that I then needed to retrieve from the trash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826219 Title: Input locks frequently/high CPU usage after 18.10->19.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary
I think this is a consequence of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499 — if so, please mark (also those others listed in #7) as duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650877 Title: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682499] Re: disable dnssec
Bug #1650877 and the others linked there (see comment #7) appear to be duplicates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682499 Title: disable dnssec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731130] [NEW] /run/resolvconf/resolv.conf contains invalid 'search' entries
Public bug reported: STEPS TO REPRODUCE: I connect to certain MIT networks via both wired and wireless connections. Afterwards, I connect to a home network. EXPECTED: Domains like http://web.mit.edu resolve. OBSERVED: They don't. The file /run/resolvconf/resolv.conf contains only these lines: nameserver 127.0.0.53 search mit.edu hsd1.ma.comcast.net It would seem hsd1.ma.comcast.net is correct, since that describes my ISP. But the mit.edu is erroneous and prevents applications from correctly resolving mit.edu domains. If I manually edit this file and remove "mit.edu" from the search line, the domains then resolve correctly. Shouldn't this be removed automatically? ~$ lsb_release -rd && apt-cache policy resolvconf Description:Ubuntu 17.10 Release:17.10 resolvconf: Installed: 1.79ubuntu8 Candidate: 1.79ubuntu8 Version table: *** 1.79ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 00:34:20 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (28 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (20 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731130 Title: /run/resolvconf/resolv.conf contains invalid 'search' entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1731130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731130] Re: /run/resolvconf/resolv.conf contains invalid 'search' entries
*** This bug is a duplicate of bug 1713457 *** https://bugs.launchpad.net/bugs/1713457 Hi—yes, it seems so. Sorry that I didn't search hard enough before reporting a duplicate! ** This bug has been marked a duplicate of bug 1713457 DNS search domain not removed from resolv.conf on disconnect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731130 Title: /run/resolvconf/resolv.conf contains invalid 'search' entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1731130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect
Is this reported upstream? Could be one of: https://bugzilla.gnome.org/show_bug.cgi?id=712818 https://bugzilla.gnome.org/show_bug.cgi?id=778004 https://bugzilla.gnome.org/show_bug.cgi?id=782469 I notice per the first one that "nmcli dev show" (not "… list", the report is old and I guess the semantics of nmcli have changed) will show me the search domain when I'm connected to a network that sets it: = $ nmcli -f IP4.ADDRESS,IP4.DOMAIN dev show IP4.ADDRESS[1]: 18.142.15.92/16 IP4.DOMAIN[1]: mit.edu IP4.ADDRESS[1]: 18.189.91.11/19 IP4.DOMAIN[1]: mit.edu IP4.ADDRESS[1]: 127.0.0.1/8 = So I guess if I try this the next time this bug crops up and nmcli disagrees with the contents of resolv.conf, I will mark the first URL as the upstream bug. Or if someone who understands this better wants to open a new upstream bug, please go ahead. ** Bug watch added: GNOME Bug Tracker #712818 https://bugzilla.gnome.org/show_bug.cgi?id=712818 ** Bug watch added: GNOME Bug Tracker #778004 https://bugzilla.gnome.org/show_bug.cgi?id=778004 ** Bug watch added: GNOME Bug Tracker #782469 https://bugzilla.gnome.org/show_bug.cgi?id=782469 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713457 Title: DNS search domain not removed from resolv.conf on disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1713457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730536] Re: "Unable to open external link" in Evince when google-chrome-unstable is the default browser
I can confirm that the changes from that merge request, when manually applied on my system, fix the problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730536 Title: "Unable to open external link" in Evince when google-chrome-unstable is the default browser To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1730536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713457] Re: DNS search domain not removed from resolv.conf on disconnect
So this has occurred again: = ~$ nmcli -f IP4.ADDRESS,IP4.DOMAIN dev show IP4.ADDRESS[1]: 10.0.0.156/24 IP4.DOMAIN[1]: hsd1.ma.comcast.net IP4.ADDRESS[1]: 127.0.0.1/8 ~$ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search hsd1.ma.comcast.net utopia.net mit.edu = Note the extra entries in the 'search' line of resolv.conf—these were from networks I was recently connected to. ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=712818 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713457 Title: DNS search domain not removed from resolv.conf on disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1713457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730536] [NEW] "Unable to open external link" in evince
Public bug reported: TO REPRODUCE: I attempt to open a URL from a PDF document in Evince. EXPECTED: The browser opens the URL. OBSERVED: I'm shown an error message: Unable to open external link Failed to execute child process “/usr/bin/google-chrome-unstable” (Permission denied) journalctl shows: Nov 06 19:19:18 khaeru-laptop audit[22110]: AVC apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 06 19:19:18 khaeru-laptop kernel: audit: type=1400 audit(1510013958.773:590): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/google/chrome-unstable/google-chrome-unstable" pid=22110 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 EXTRA INFORMATION: - As the messages imply, I'm using Google Chrome "unstable". - The file /usr/bin/google-chrome-unstable …is symlinked to: /opt/google/chrome-unstable/google-chrome-unstable - I note that previous bugs, eg. bug #964510, resulted in lines being added to /etc/apparmor.d/abstractions/ubuntu-helpers that refer to paths in /opt/google/chrome/. This directory does not exist on my system. $ lsb_release -rd && apt-cache policy apparmor evince google-chrome-unstable Description:Ubuntu 17.10 Release:17.10 apparmor: Installed: 2.11.0-2ubuntu17 Candidate: 2.11.0-2ubuntu17 Version table: *** 2.11.0-2ubuntu17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status evince: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status google-chrome-unstable: Installed: 64.0.3251.0-1 Candidate: 64.0.3253.3-1 Version table: 64.0.3253.3-1 500 500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages *** 64.0.3251.0-1 100 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor 2.11.0-2ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 19:20:34 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (26 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=39ca3c53-0313-4699-a5da-403522e2ff14 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to artful on 2017-10-19 (18 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730536 Title: "Unable to open external link" in evince To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1730536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724957] [NEW] gnome-shell crashes → unable to log in after artful upgrade
Public bug reported: CONTEXT I was running 17.04, and had manually installed gdm3, gnome-shell etc. to use the GNOME Shell. I had also installed some extensions (from both the respositories and through extensions.gnome.org). I used "sudo do-release-upgrade" to upgrade from 17.04 to 17.10. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 17.10 Release:17.10 gnome-shell: Installed: 3.26.1-0ubuntu4 Candidate: 3.26.1-0ubuntu4 Version table: *** 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status After rebooting, I tried to install in with all of the available sessions, including: - GNOME - GNOME Classic - GNOME on Xorg - Ubuntu - Ubuntu on Xorg Expected: I'm able to log in to the desktop. Observed: In every case, I would be kicked back to the GDM greeter. WORKAROUND Checking the output of `journalctl`, I noticed the following lines: Oct 19 15:51:17 khaeru-laptop gnome-shell[30363]: loading default theme (Adwaita) Oct 19 15:51:17 khaeru-laptop gnome-shell[30363]: Settings schema 'org.gnome.shell.extensions.dash-to-dock' does not contain a key named 'opaque-background' Oct 19 15:51:17 khaeru-laptop kernel: traps: gnome-shell[30363] trap int3 ip:7f194308c961 sp:7fff78248270 error:0 in libglib-2.0.so.0.5400.1[7f194303c000+111000] […more…] Oct 19 15:51:17 khaeru-laptop polkitd(authority=local)[1189]: Unregistered Authentication Agent for unix-session:20 (system bus name :1.473, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_CA.UTF-8) (disconnected from bus) Oct 19 15:51:17 khaeru-laptop gnome-session[30205]: gnome-session-binary[30205]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Oct 19 15:51:17 khaeru-laptop gnome-session-binary[30205]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 In particular, the complaint about the settings schema always appeared as the last message before the "kernel: traps: gnome-shell" message. On a hunch, I disabled all extensions: $ dconf reset /org/gnome/shell/enabled-extensions After this, I was able to log in. COMMENT I understand that my manual installation/use of Gnome Shell prior to the upgrade might have produced some unusual contents in that dconf key. The prior value was: enabled-extensions=['places-menu@gnome-shell- extensions.gcampax.github.com', 'user-theme@gnome-shell- extensions.gcampax.github.com', 'remove-dropdown-arr...@mpdeimos.com', 'workspace-indica...@gnome-shell-extensions.gcampax.github.com', 'suspend-button@laserb', 'pixel-s...@deadalnix.me', 'dash-to- d...@micxgx.gmail.com'] The bug, IMO, is that this caused gnome-shell to crash that left me unable to log in to any session. If particular extensions or dconf keys are erroneous or broken, I would expect them to be disregarded and perhaps some error message displayed while login continued. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 16:02:39 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (8 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash LC_PAPER=en_GB.UTF-8 SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724957 Title: gnome-shell crashes → unable to log in after artful upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724957] Re: gnome-shell crashes → unable to log in after artful upgrade
** Attachment added: "Full dump from 'journalctl' containing the kernel trap lines mentioned in the report" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724957/+attachment/4976708/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724957 Title: gnome-shell crashes → unable to log in after artful upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724999] [NEW] Claws Mail 'fancy' plugin missing in 17.10
Public bug reported: The package 'claws-mail-fancy-plugin', which allows display of HTML messages, is not available in the 17.10/artful archives. Consequently, it's no longer possible to view HTML messages in Claws Mail. $ lsb_release -rd && apt-cache policy claws-mail Description:Ubuntu 17.10 Release:17.10 claws-mail: Installed: 3.15.0-2build2 Candidate: 3.15.0-2build2 Version table: *** 3.15.0-2build2 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: claws-mail 3.15.0-2build2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 17:37:51 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-11 (8 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash LC_PAPER=en_GB.UTF-8 SourcePackage: claws-mail UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) ** Affects: claws-mail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724999 Title: Claws Mail 'fancy' plugin missing in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1724999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724999] Re: Claws Mail 'fancy' plugin missing in 17.10
Ah, thanks for the pointer. I found a related bug in the Claws Mail bugtracker and added the link. ** Bug watch added: Claws Mail bugzilla #3763 http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3763 ** Also affects: claws-mail via http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3763 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724999 Title: Claws Mail 'fancy' plugin missing in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/claws-mail/+bug/1724999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579181] Re: "pip3 list --outdated" raises TypeError
A workaround is: $ pip3 install --user --no-deps pip Collecting pip Downloading pip-8.1.1-py2.py3-none-any.whl (1.2MB) 100% || 1.2MB 612kB/s Installing collected packages: pip Successfully installed pip-8.1.1 …(i.e. exactly the same version of pip) and ensure ~/.local/bin is in my $PATH. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579181 Title: "pip3 list --outdated" raises TypeError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1579181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579181] [NEW] "pip3 list --outdated" raises TypeError
Public bug reported: Observed: $ pip3 list --outdated Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 209, in main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 118, in run self.run_outdated(options) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 128, in run_outdated if latest_version > dist.parsed_version: TypeError: unorderable types: Version() > SetuptoolsVersion() Expected: a list of outdated packages is displayed. This particular exception appears to be discussed upstream at: https://github.com/pypa/pip/issues/3057 where an upstream dev says, quote, "I don't think there's anything we can reasonably do here, you're running a patched or unsupported version of pip. You should file a bug with whomever gave you your copy of pip and ask them to stop patching it." $ lsb_release -rd && apt-cache policy python3-pip Description:Ubuntu 16.04 LTS Release:16.04 python3-pip: Installed: 8.1.1-2 Candidate: 8.1.1-2 Version table: *** 8.1.1-2 500 500 http://mirrors.mit.edu/ubuntu xenial/universe amd64 Packages 500 http://mirrors.mit.edu/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579181 Title: "pip3 list --outdated" raises TypeError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1579181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
