[Bug 2063099] Re: Stopping container signal blocked by AppArmor on Ubuntu
containerd seems to have similar issues from Kubernetes... (I need to check if a bug exists for that as well) kubelet.go:2049] [failed to "KillContainer" for "ceph-exporter" with KillContainerError: "rpc error: code = Unknown desc = failed to kill container \"373f6f3fc02b903a49b6d5e330366944e9cec71b697047807a2d1aa9a3362f97\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown", failed to "KillPodSandbox" for "5d1942f2-81f0-4f8c-a970-e5b81a2869f7" with KillPodSandboxError: "rpc error: code = Unknown desc = failed to stop container \"373f6f3fc02b903a49b6d5e330366944e9cec71b697047807a2d1aa9a3362f97\": failed to kill container \"373f6f3fc02b903a49b6d5e330366944e9cec71b697047807a2d1aa9a3362f97\": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown"] (It seems like it might be a runc level issue, not just Docker) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063099 Title: Stopping container signal blocked by AppArmor on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/2063099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077401] [NEW] virtualbox-dkms 6.1.50-dfsg-1~ubuntu1.22.04.1: virtualbox kernel module failed to build
Public bug reported: Update failed to install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: virtualbox-dkms 6.1.50-dfsg-1~ubuntu1.22.04.3 ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 6.8.0-40-generic Date: Wed Aug 14 18:46:36 2024 InstallationDate: Installed on 2023-07-27 (389 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageVersion: 6.1.50-dfsg-1~ubuntu1.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: virtualbox Title: virtualbox-dkms 6.1.50-dfsg-1~ubuntu1.22.04.1: virtualbox kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077401 Title: virtualbox-dkms 6.1.50-dfsg-1~ubuntu1.22.04.1: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2077401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
Still happens on my Lenovo Thinkpad P50. When shutting down, I have to hold down the power button for five seconds to get it to shut down completely, even though the external red LED (the dot of the "i" in "Thinkpad" on the lid) has turned off. I cannot restart the machine, same story as when trying to shut it down. If I close the lid, the power button will start pulsing after opening again. However, nothing can make it wake up again. Pressing keys, mouse or even the power button does nothing. The only thing that works is holding down the power button for five seconds to shut it down completely. As far as I can tell, this happens 100% of the time. My computer: https://linux-hardware.org/?probe=848e7fb28d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
Still happens on my Lenovo Thinkpad P50. When shutting down, I have to hold down the power button for five seconds to get it to shut down completely, even though the external red LED (the dot of the "i" in "Thinkpad" on the lid) has turned off. I cannot restart the machine, same story as when trying to shut it down. If I close the lid, the power button will start pulsing after opening again. However, nothing can make it wake up again. Pressing keys, mouse or even the power button does nothing. The only thing that works is holding down the power button for five seconds to shut it down completely. As far as I can tell, this happens 100% of the time. My computer: https://linux-hardware.org/?probe=848e7fb28d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564317] Re: Successful return code on encoding error
Some issue on 24.04: root@noble ~ # curl -s https://launchpadlibrarian.net/250515419/test.html | html2text; echo $? Input recoding failed due to invalid input sequence. Unconverted part of text follows. “Test�?) 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564317 Title: Successful return code on encoding error To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1564317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066030] [NEW] Package "diffuse" has a dependency on package "python3-distutils-extra" which is not automatically installed.
Public bug reported: I ran "sudo apt install diffuse" and expected diffuse to be installed and working. However, diffuse was installed but not working. When running diffuse from command-line, I noticed it was missing "distutils". Manual installation of python3-distutils-extra solved the problem. Hopefully someone can make it so this package is included as a requirement in the diffuse package. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: diffuse 0.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:00:44 2024 InstallationDate: Installed on 2024-05-01 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageArchitecture: all SourcePackage: diffuse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: diffuse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2066030 Title: Package "diffuse" has a dependency on package "python3-distutils- extra" which is not automatically installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffuse/+bug/2066030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548206]
Hello, which Info are you waiting for? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548206 Title: Kate spellcheck not working To manage notifications about this bug go to: https://bugs.launchpad.net/hunspell/+bug/1548206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548206]
root# find / -iname *hspell* find: ‘/run/user/1000/doc’: Permission denied /usr/lib/x86_64-linux-gnu/enchant-2/enchant_hspell.so /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/sonnet/sonnet_hspell.so /snap/gnome-3-28-1804/161/usr/lib/x86_64-linux-gnu/enchant/libenchant_hspell.so This is all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548206 Title: Kate spellcheck not working To manage notifications about this bug go to: https://bugs.launchpad.net/hunspell/+bug/1548206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548206]
Hello Waqar,
at least I do not have an "hspell" package installed. Maybe it comes in
another package name? Here are all installed packages with "spell" in
their name or description title:
$ dpkg -l | grep spell
ii aspell0.60.8-3
amd64GNU Aspell spell-checker
ii aspell-en 2018.04.16-0-1
all English dictionary for GNU Aspell
ii dictionaries-common 1.28.4
all spelling dictionaries - common utilities
ii enchant-2 2.3.1-1
amd64Wrapper for various spell checker engines (binary
programs)
ii hunspell-de-at-frami 1:7.1.0~rc3-3
all German (Austria) dictionary for hunspell ("frami"
version)
ii hunspell-de-ch-frami 1:7.1.0~rc3-3
all German (Switzerland) dictionary for hunspell
("frami" version)
ii hunspell-de-de-frami 1:7.1.0~rc3-3
all German dictionary for hunspell ("frami" version)
ii hunspell-en-us1:2019.10.06-1
all English_american dictionary for hunspell
ii libaspell15:amd64 0.60.8-3
amd64GNU Aspell spell-checker runtime library
ii libenchant-2-2:amd64 2.3.1-1
amd64Wrapper library for various spell checker engines
(runtime libs)
ii libhfstospell11:amd64 0.5.2-1build2
amd64HFST spell checker runtime libraries
ii libhunspell-1.7-0:amd64 1.7.0-3
amd64spell checker and morphological analyzer (shared
library)
ii libkf5sonnet5-data
5.89.0-0ubuntu1~ubuntu21.10~ppa1all spell checking library
for Qt, data files
ii libkf5sonnetcore5:amd64
5.89.0-0ubuntu1~ubuntu21.10~ppa1amd64spell checking library
for Qt, core lib
ii libkf5sonnetui5:amd64
5.89.0-0ubuntu1~ubuntu21.10~ppa1amd64spell checking library
for Qt, ui lib
ii libqt5hunspellinputmethod5:amd64 5.15.2+dfsg-2
amd64Qt virtual keyboard - helper library for Hunspell
input method
ii python3-enchant 3.2.0-1
all spellchecking library for Python 3
ii qml-module-org-kde-sonnet:amd64
5.89.0-0ubuntu1~ubuntu21.10~ppa1amd64spell checking library
for Qt, plugins
ii sonnet-plugins:amd64
5.89.0-0ubuntu1~ubuntu21.10~ppa1amd64spell checking library
for Qt, plugins
The whole /usr/share/hspell directory is not present:
$ ls -l /usr/share/hspell
ls: cannot access '/usr/share/hspell': No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548206
Title:
Kate spellcheck not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/hunspell/+bug/1548206/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548206]
Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-22-generic (64-bit) Graphics Platform: X11 I still get the warning when starting e.g. kwrite Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed I do not have hspell installed. Also I do not need hebrew spell checking on my system. So why is this warning given? (And why not other languages, too?) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kate in Ubuntu. https://bugs.launchpad.net/bugs/1548206 Title: Kate spellcheck not working To manage notifications about this bug go to: https://bugs.launchpad.net/hunspell/+bug/1548206/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1905064] Re: "+" suffix in 3.9.0+ breaks pip
It seems this version string was introduced in a upstream Debian patch indeed, when it was based on a prerelease version of Python 3.9. The patch (git-updates.diff) was dropped later. Introduced (erroneously): https://salsa.debian.org/cpython-team/python3/-/commit/5334a0144db8e35afa8ae898d0dbd06afa426ccb Removed: https://salsa.debian.org/cpython-team/python3/-/commit/7952d9ce65aa51d6a23107ce1e30d0d92b1e15c7 Please backport the updated Debian-packaged Python 3.9 to Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905064 Title: "+" suffix in 3.9.0+ breaks pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.9/+bug/1905064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon
This also took Docker down on 18.04 with the update for USN-4653-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895155] [NEW] ubuntu 20 crash on install
Public bug reported: I was busy filling out my persona details just after I chose ZFS for the HD. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./dists/focal/main/binary-amd64/Packages.gz CasperMD5CheckResult: skip CasperVersion: 1.445.1 Date: Thu Sep 10 16:04:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895155 Title: ubuntu 20 crash on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1895155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings
As a new chromium version came in I have tested this again: gert@flupp:~$ rm -rf ~/snap/chromium/current/.config/ gert@flupp:~$ chromium [10090:10090:1109/162748.523398:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process. [10090:10090:1109/162748.862772:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command [10155:1:1109/162749.902762:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [10155:1:1109/162749.903262:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. gert@flupp:~$ Again the config was not transfered. gert@flupp:~$ sed -e 's/.*"last_chrome_version":"\([0-9\.]\+\)".*/\1\n/' ~/.config/chromium/Default/Preferences sed: can't read /home/gert/.config/chromium/Default/Preferences: No such file or directory Should there be a Link "Default" to the "Profile 1" directory? Here is the content of my former .config/chromium directory: gert@flupp:~$ ls -l ~/.config/chromium/ total 4232 drwx-- 2 gert gert4096 Aug 22 2015 Avatars -rw--- 1 gert gert 4194304 Okt 24 11:13 BrowserMetrics-spare.pma drwx-- 4 gert gert 4096 Okt 24 11:17 CertificateRevocation drwx-- 3 gert gert 4096 Aug 2 23:09 CertificateTransparency -rw--- 1 gert gert 22 Jun 18 2016 Channels -rw-rw 1 gert gert 4 Okt 24 13:47 chrome_shutdown_ms.txt drwx-- 2 gert gert 4096 Jan 31 2014 'Crash Reports' drwx-- 2 gert gert4096 Feb 8 2018 Dictionaries drwx-- 3 gert gert4096 Sep 3 2015 EVWhitelist drwx-- 3 gert gert4096 Mai 19 12:46 FileTypePolicies -rw-rw---- 1 gert gert 0 Jun 3 2010 'First Run' drwx-- 3 gert gert4096 Sep 13 2018 InterventionPolicyDatabase -rw--- 1 gert gert 23284 Okt 24 13:47 'Local State' drwx-- 2 gert gert4096 Aug 5 18:41 MEIPreload drwx-- 2 gert gert4096 Sep 10 2016 OriginTrials drwx-- 2 gert gert4096 Feb 23 2012 PepperFlash drwx-- 4 gert gert4096 Nov 12 2014 pnacl drwx-- 32 gert gert4096 Okt 24 13:47 'Profile 1' drwx-- 2 gert gert4096 Okt 24 13:44 'Safe Browsing' -rw-r- 1 gert gert5120 Okt 31 2017 'Safe Browsing Channel IDs' -rw-r- 1 gert gert 0 Okt 31 2017 'Safe Browsing Channel IDs-journal' -rw-r- 1 gert gert9216 Okt 12 19:05 'Safe Browsing Cookies' -rw-r- 1 gert gert 0 Okt 12 19:05 'Safe Browsing Cookies-journal' -rw--- 1 gert gert 50 Dez 16 2011 'Service State' drwx-- 3 gert gert4096 Dez 23 2015 ShaderCache drwx-- 3 gert gert4096 Dez 22 2018 SSLErrorAssistant drwx-- 4 gert gert4096 Mai 13 2018 'Subresource Filter' drwx-- 2 gert gert4096 Feb 1 2013 Temp drwx-- 2 gert gert4096 Jan 18 2018 'Webstore Downloads' drwx-- 2 gert gert4096 Okt 14 2016 WidevineCdm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings
After creating the Symlink inside of the .config/chromium/ directory, my config was transfered fine on the next chromium restart. So I have found a workaround for my situation. Thank you. gert@flupp:~/.config/chromium$ ln -s Profile\ 1/ Default gert@flupp:~/.config/chromium$ cd gert@flupp:~$ rm -rf ~/snap/chromium/current/.config/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings
Hello Olivier, please see the end of my last comment #22. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium settings
Occurrences if chromium in the dpkg.log: root@flupp:/var/log# grep chromium dpkg.log 2019-10-24 16:15:45 upgrade chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:15:45 status half-configured chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status unpacked chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status half-installed chromium-browser-l10n:all 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status unpacked chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:15:45 upgrade chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:15:45 status half-configured chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:45 status unpacked chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:15:46 status half-installed chromium-browser:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:17:26 status unpacked chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:18:43 upgrade chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:18:43 status half-configured chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:18:43 status unpacked chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:18:43 status half-installed chromium-codecs-ffmpeg-extra:amd64 76.0.3809.100-0ubuntu0.19.04.1 2019-10-24 16:18:43 status unpacked chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 configure chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 status unpacked chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 status half-configured chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:22:23 status installed chromium-codecs-ffmpeg-extra:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 configure chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status unpacked chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status half-configured chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status installed chromium-browser:amd64 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 configure chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status unpacked chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status half-configured chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:44:26 status installed chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:12 status installed chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 remove chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status half-configured chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status half-installed chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status config-files chromium-browser-l10n:all 77.0.3865.120-0ubuntu1~snap1 2019-10-24 16:47:13 status not-installed chromium-browser-l10n:all After starting the PC and logging into KDE without starting chromium: gert@flupp:~$ snap connections chromium | grep password password-manager-service chromium:password-manager-service :password-manager-service manual I remember that after the upgrade when the configs have not been transfered, that last "manual" was not printed. I think it was a "-" instead. After starting up the connection manually as mentioned in the bug 1849160 the "manual" was printed. After removing the ~/snap/chromium/current/.config/ directory and starting chromium the following was printed to konsole. (And the settings were not transfered.) gert@flupp:~$ which chromium /snap/bin/chromium gert@flupp:~$ chromium [4498:4498:1026/104128.629497:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process. [4498:4498:1026/104128.968059:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command [4560:1:1026/104130.143320:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [4560:1:1026/104130.143846:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [4573:1:1026/104132.869494:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. [4573:1:1026/104132.869978:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. If I can test and report something e
[Bug 1849693] Snap.Info.chromium.txt
apport information ** Attachment added: "Snap.Info.chromium.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299959/+files/Snap.Info.chromium.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299953/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299952/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299956/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299949/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299950/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299963/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Snap.Connections.txt
apport information ** Attachment added: "Snap.Connections.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299958/+files/Snap.Connections.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299951/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Snap.Info.core18.txt
apport information ** Attachment added: "Snap.Info.core18.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299961/+files/Snap.Info.core18.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Snap.Info.gtk-common-themes.txt
apport information ** Attachment added: "Snap.Info.gtk-common-themes.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299962/+files/Snap.Info.gtk-common-themes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299954/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299955/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings
Will the transfer of the .config/chromium files start again when removing the snap/chromium files? So I could test if it works with a second try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings
apport information
** Tags added: apport-collected eoan snap
** Description changed:
I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed
from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser
for the first time, it should have imported all former settings. But it
did not. E.g. all bookmarks and saved passwords are gone.
Is there a way to start the config import afterwards?
The workaround mentioned under the following link did not help in my case:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DRM.card0-DP-1:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-DP-2:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-DP-3:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-HDMI-A-1:
+ enabled: enabled
+ dpms: On
+ status: connected
+ edid-base64:
AP///wAVw4UjAQEBAQIXAQOANCF46vkVo1RQnicSUFShCACpQIGAgUCzAIHAAQEBAQEBKDyAoHCwI0AwIDYAB0QhAAAa/wA0NTE3NDAxMwogICAg/QA7PR9MEQAKICAgICAg/ABFVjI0MzZXCiAgICAgALk=
+ modes: 1920x1200 1600x1200 1680x1050 1280x1024 1280x960 1280x720 1024x768
800x600 640x480 720x400
+ DRM.card0-HDMI-A-2:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-HDMI-A-3:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DRM.card0-VGA-1:
+ enabled: disabled
+ dpms: Off
+ status: disconnected
+ edid-base64:
+ modes:
+ DiskUsage:
+ Filesystem Type Size Used Avail Use% Mounted on
+ /dev/sda5 ext4 394G 48G 327G 13% /home
+ tmpfs tmpfs 3,9G 19M 3,9G 1% /dev/shm
+ /dev/sda5 ext4 394G 48G 327G 13% /home
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2018-11-24 (334 days ago)
+ InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.2)
+ MachineType: Gigabyte Technology Co., Ltd. Z68X-UD3H-B3
+ Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=c2336ec0-2c4e-4cf0-a475-ea8727cc3ac8 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
+ Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
+ Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
+ Tags: eoan snap
+ Uname: Linux 5.3.0-19-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-10-24 (0 days ago)
+ UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers
video
+ _MarkForUpload: True
+ dmi.bios.date: 05/02/2011
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: F2
+ dmi.board.name: Z68X-UD3H-B3
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd05/02/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68X-UD3H-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3H-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
+ dmi.product.name: Z68X-UD3H-B3
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1849693/+attachment/5299948/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849693
Title:
Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Re: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings
Hello Olivier, No, I don't think that chromium was installed as snap before. I have never installed snap things myself, only maybe such packages that were installed by the system, AFAIK. I did the apport-collect and attached the history.log Regards Gert ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+attachment/5299964/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Snap.Info.core.txt
apport information ** Attachment added: "Snap.Info.core.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299960/+files/Snap.Info.core.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] Snap.ChromiumPrefs.txt
apport information ** Attachment added: "Snap.ChromiumPrefs.txt" https://bugs.launchpad.net/bugs/1849693/+attachment/5299957/+files/Snap.ChromiumPrefs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849693] [NEW] Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings
Public bug reported: I just have upgraded from kubuntu 19.04 to 19.10. chromium was changed from deb to snap 77.0.3865.120-0ubuntu1~snap1. When starting the browser for the first time, it should have imported all former settings. But it did not. E.g. all bookmarks and saved passwords are gone. Is there a way to start the config import afterwards? The workaround mentioned under the following link did not help in my case: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160 ** Affects: chromium-browser (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/1849693 Title: Upgrading from kubuntu 19.04 to 19.10 lost all chhromium settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844049] [NEW] Other Software checkboxes don't always open the privilege elevations window
Public bug reported: Disabling repos under Other Software usually doesn't open up the password window like it should. The window just turns grey but I can use it when I click on it as if nothing happened. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.11 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 15 13:57:03 2019 InstallationDate: Installed on 2019-07-26 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (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/1844049 Title: Other Software checkboxes don't always open the privilege elevations window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1844049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843693] [NEW] Segfault in mod_md.so when adding new MDomain section
Public bug reported: After adding a new domain with MDomain and rebooting apache2, apache2 crashes: $ dmesg ... apache2[1241]: segfault at 0 ip 7f288669a86d sp 7ffc76b935a0 error 4 in mod_md.so.0.0.0[7f2886682000+31000] Updating mod_md to 1.1.17 would solve it: https://github.com/icing/mod_md/releases/tag/v1.1.17 ** Affects: libapache2-mod-md (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/1843693 Title: Segfault in mod_md.so when adding new MDomain section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-md/+bug/1843693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882]
I am currently using Debian 10 Buster with Wayland. This problem is not existing anymore at this release. Wayland no longer uses an extra fence register if dual monitor is used. The wrong reservation of fence registers at intel_blit.c still exists, but does not harm, because the limit of 14 usable fence registers is very safe. A limit of 15 might be possible, if reservation at intel_blit.c is unbugged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Unfortunatelu no new flavor of Ubuntu is supporting 32 bits anymore. Therefore I had to install Debian 10 (Buster). Wayland at Debian is running without severe problems. This problem also is not existing anymore, because Wyland is no longer using an extra fence register if a dual monitor is used. I suppose this means also at some release of Ubuntu the problem will disappear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835188] Re: firewalld attempts to use parameter that requires a newer iptables version
That code path fails to detect that neither --wait or -w is supported, since iptables-restore returns a successful return code on invalid parameters and firewalld uses the return code to detect whether it works: # echo "#foo" | /sbin/iptables-restore --wadit=2; echo $? /sbin/iptables-restore: unrecognized option '--wadit=2' 0 The current version of firewalld fixed that, by looking for the error message as well: https://github.com/firewalld/firewalld/commit/2e929389eb15b12e96f18e5fe3dc5ae31639e8dd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835188 Title: firewalld attempts to use parameter that requires a newer iptables version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835188] [NEW] firewalld attempts to use parameter that requires a newer iptables version
Public bug reported: firewalld from Ubuntu 18.04 LTS sometimes attempts to use the `--wait` option to iptables-restore, which is only valid on iptables 1.8.x and newer and not on 1.6.1, as bundled with bionic. (At least according to the man page, the comments in the firewalld code implies that it was supported on an older version, but that might be with Fedora patches) This seems to originate from firewalld-0.4.4.6/src/firewall/core/ipXtables.py, line 337. If this runs firewalld fails to create the rules when starting, resulting in wither no rules loaded, or the policies loaded, without any rules, which blocks SSH. It is not clear when this gets triggered, with several servers deployed with the same Ansible script, some have this issue, some work fine. The unit file was overwriten as per this to get it to start in the first place: https://github.com/firewalld/firewalld/issues/414 The warning that accompanies the failed rule loading is: ``` WARNING: '/sbin/iptables-restore --wait=2 -n' failed: /sbin/iptables-restore: unrecognized option '--wait=2'#012iptables-restore: line 93 failed ``` iptables version: 1.6.1-2ubuntu2 firewalld version: 0.4.4.6-1 ** Affects: firewalld (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/1835188 Title: firewalld attempts to use parameter that requires a newer iptables version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835188] Re: firewalld attempts to use parameter that requires a newer iptables version
Mostly when firewalld fails with that error, a restart will fix it (It seems to only hit that code path sometimes), however if it is a headless box, that restart might be tricky. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835188 Title: firewalld attempts to use parameter that requires a newer iptables version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1835188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
I experienced the same problem when I tried to install Ubuntu 19.04 with the initial option to install third party drivers. After installation and the first reboot, the system will not start up. I will see if I can reproduce this and post the log report. I have a Dell Vostro 3670 PC with the following deatils: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz; Motherboard: Dell Ince OV8F20; 12 GB RAM; NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]); -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824670] Re: Boot to black screen after Kubuntu 19.04 install
I have not tried running SDDM rather than the normal Ubuntu Desktop. Will try that tomorrow. I still get the same error with Ubuntu 19.04 when I try to install the Nvidia driver. Anyone with a solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824670 Title: Boot to black screen after Kubuntu 19.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1824670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
I have a NVIDIA Corporation GP107 [GeForce GTX 1050] card and ubuntu 19.04 installed. After installing the lastest Nvidia driver-430, the dektop GUI is lost when you reboot (18.10 gave the same issue). I tried many proposed solutions, including the one above. Nothing worked. I finally found a solution for this Nvidia driver issue (on ubuntu 18 and 19). See instructions at the top at https://ubuntuforums.org/showthread.php?t=2419319&highlight=nvidia+drivers, it worked for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
I did at #14 again, set verification-done-bionic for this fix, as requested. Again it disappears. I now tested the fix 3 times (once for cosmic and twice for bionic). This time I did the same test as at #8. Whatever you do it was the last time I test this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
Problem could not be reproduced, because it was hidden by bug #1795774. After installation from proposed, the problem was solved: root@gert-laptop:/etc/apt# dpkg -s libmutter-2-0 | grep Version Version: 3.28.3+git20190124-0ubuntu18.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Problem reproduced with old version: gert@gert-laptop:~$ dpkg -s libmutter-2-0 | grep Version Version: 3.28.3-2~ubuntu18.04.2 Apr 19 14:41:11 gert-laptop gnome-shell[991]: CoglError set over the top of a previous CoglError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Apr 19 14:41:11 gert-laptop org.gnome.Shell.desktop[991]: double free or corruption (fasttop) Apr 19 14:41:11 gert-laptop org.gnome.Shell.desktop[991]: == Stack trace for context 0x1ab5838 == Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: Fatal server error: Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) failed to read Wayland events: Broken pipe Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) Apr 19 14:41:47 gert-laptop gnome-session-binary[983]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 After installation from proposed, the problem was solved: root@gert-laptop:/etc/apt# dpkg -s libmutter-2-0 | grep Version Version: 3.28.3+git20190124-0ubuntu18.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
To reproduce the problem at bionic I had to uninstall the cryptsetup-package and use DeviceTimeout 1 at /etc/plymouth/plymouthd.cfg. After installing plymouth:i386 0.9.3-1ubuntu7.18.04.2, the problem disappeared. Problem solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Installed packages plymouth and libplymouth4 from cosmic-proposed. e.g: Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 plymouth i386 0.9.3-1ubuntu10.1 To test the fix I verified plymouth and drm-modules are not present at initramfs. This causes intel drm to be initiated after startup of plymouth and previously caused the problem. Verified at plymouth:debug log, that fb driver first was loaded and later replaced by drm-driver. Problem was solved now! Remark: the default delivered initramfs hook /usr/share/initramfs-tools/hooks/plymouth still contains the line: OPTION=FRAMEBUFFER At my PC the variable FRAMEBUFFER is not set by any file at /usr/share/initramfs-tools/conf-hooks.d, causing plymouth and drm-files not loaded at initramfs. This gives an annoying late appearing of the plymouth-screen at startup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
Verification succeeded. Problem solved ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Verification succeeded. Problem solved. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Sorry, I missed the previous request to verify at bionic. Bionic is my basic Ubuntu. I only use cosmic for test. At the past I installed cosmic only to verify the wayland-patch for old Intel-graphics. This worked but I got a lot of other problems with unstable starting of ubuntu, caused by wayland and plymouth. At bionic I recently have installed the same (proposed by me) patches as at cosmic, which worked. I will verify the official proposed fix at bionic as requested and report here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882]
Created attachment 143414 fix intel_blit.c fix error_patch2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882]
Created attachment 143415 libdrm_ignore_deadlock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882]
Some more investigation, understanding and adding 2 other possible fixes for the problem. The problem occurs at Ubuntu 18.10 only at gdm3 with wayland using dual monitor. It is not occuring with wayland at single monitor. It totally doesnot occur if gdm3 is not using wayland. At ubuntu 18.04 the same problem exists with wayland, but is not occurring so often. At ubuntu 18.10 with wayland and dual monitor the user session immediately aborts, if 16 or more favorites are allocated at the dock. For some reason wayland seems to use one extra fence register at dual monitor. It is noticed at dual monitor, that gdm3 with wayland uses 2 calls to clutter_stage_cogl_redraw_view for 2 logical screens for every call to clutter_stage_cogl_redraw; gdm3 without wayland does only one call to clutter_stage_cogl_redraw_view for 1 logical screen. The crash occurs at intel_batchbuffer_flush. Always the last batch at such a flush is coming from function emit_copy_blit and intelClearWithBlit at src/mesa/drivers/dri/i915/intel_blit.c. At the call to dri_bufmgr_check_aperture_space they indicate to use zero fence registers, but in fact they use one. This violates the limit of 14, causing a crash at dual monitor. So the call to dri_bufmgr_check_aperture_space must be postponed, until the needed fence register is added in the middle of the batch-generation and then the batch-actions must be undone, a flush is called and batch is regenerated again. For this function intel_batchbuffer_emit_reset is added. This also is done for function intel_miptree_set_alpha_to_one, although I never saw a call of this function. See fix error3_patch2.txt. Another (dirty) solution is to decrement the availablity and just continue. This gives somewhere a failure, but I could not see a failing layout. See fix error3_patch3.txt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
Reinstalled current libmutter. With dual monitor horizontal aside this problem could not be reproduced because logon-session crashes before showing logon-screen, (caused by bug #1790525). Installed proposed version: apt list libmutter-3-0 Listing... Done libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed] No crash anymore when trying to suspend at logon-screen. Problem is solved by proposed package. No new other problems detected. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
** Tags removed: cosmic verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Reinstalled current libmutter. With dual monitor horizontal aside this gives Feb 1 22:26:58 Gert2 gnome-shell[1038]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints Feb 1 22:26:58 Gert2 gnome-shell[1038]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Logon-session crashes before showing logon-screen. Installed proposed version: apt list libmutter-3-0 Listing... Done libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed] Problem is solved by proposed package. No new other problems detected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/form
Issue https://gitlab.gnome.org/GNOME/mutter/issues/453 is added to
mutter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from ... from
FatalError("wl_surface@429: error 2: Failed to create a texture for
surface 429: Failed to create texture 2d due to size/format
constraints\n")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/form
Because this bug no longer is marked as duplicate of #1745799, I now add
the bug-fix (tested by me for a long time) to this bug.
** Attachment added: "Patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+attachment/5231631/+files/error9_patch.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from ... from
FatalError("wl_surface@429: error 2: Failed to create a texture for
surface 429: Failed to create texture 2d due to size/format
constraints\n")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"]
I created bug #1795760, which describes a Xwayland-abort and got the status duplicate of 1745799. Below is a part of the symbolic trace of the abort. #7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n", args=0xbf9c7994 "\027uܷ\255\001") at ../../../../../hw/xwayland/xwayland.c:1137 msg = "wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/format constraints\n", '\000' #8 0xb7dc5fef in wl_log (fmt=0xb7dc71ea "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 Problem can be solved by using slicing at shm_buffer_attach() at src/wayland/meta-wayland-buffer.c, if size of texture is too large for graphics card. I attach a bug-fix to this bug, which is tested during a long time. ** Attachment added: "error9_patch.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+attachment/5231177/+files/error9_patch.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745799 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450763] Re: Syntax error: ")" unexpected
Wow, probably not. The ticket stems from 2015. As far as I am concerned this ticket may be closed. I'm not sure if I acted correctly, but I changed the status to Fix Released (as I don't see an option for 'Close'. ** Changed in: needrestart (Ubuntu) Status: Incomplete => 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/1450763 Title: Syntax error: ")" unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1450763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Mesa-bug: https://bugs.freedesktop.org/show_bug.cgi?id=109102 ** Bug watch added: freedesktop.org Bugzilla #109102 https://bugs.freedesktop.org/show_bug.cgi?id=109102 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Without solving this problem, wayland cannot be used after logon, when using dual monitor. The sesssion stops very easy and often. Work is lost; you have to logon again. E.g. the simple switching between 2 overlapping windows causes the end of the session. I changed src/mesa/drivers/dri/i915/intel_batchbuffer.c to force a coredump in this case. The stacktrace is added to this bug-report. Linenumbers might deviate a little bit because of extra coding of tracing. The deadlock always occurs at cogl_onscreen_swap_buffers calling cogl_flush(), at the first journal-batch-flush for the offscreen-framebuffer. The deadlock disappeared as soon as cogl is compiled with disabled batching! To minimize this disabling of batching, I made a very dirty but working patch, which is attached to this bug. At program clutter_stage_cogl_redraw_view routine paint_stage is called for the "Unclipped stage paint". This call is manipulated to flush immedately the first journal-entry of the default onscreen framebuffer. This is done by misusing and changing program cogl_framebuffer_set_viewport and by changing _cogl_journal_flush. Apparenly this early flushing causes a lock to be set which avoids the deadlock. I do not know how to see which locks are held and by which process, so I cannot solve the root-cause of thhe problem, but I assume some extra lock must be set in this case to avoid deadlock. With this dirty patch combined with other suggested (simple) patches at #1790525, #1795774 and #1795760 wayland can be run without any problems on dual monitor and "old" intel graphic card. It performs better than lightdm, specially if the monitors are positioned aside of each other. ** Attachment added: "dirty_patch.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223253/+files/dirty_patch.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Trace ** Attachment added: "trace at forced coredump" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223254/+files/wayland_stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 *** https://bugs.launchpad.net/bugs/1745799 This is not a duplicate. It is a crash at OsAbort, but that is the only coincidence with #1745799. The cause is different. It contains a working solution. PLease do something with it and do not mark it 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/1795760 Title: Xwayland crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_f
Mathieu, I have to decline. I do not think the Ubuntu-world is waiting for my newbie Mail-address. Gert On 12/6/18 5:25 PM, Mathieu Trudel-Lapierre wrote: > Sorry, we don't see it there. The emails are re-jiggled by Launchpad. > > If you prefer, you can send it to me directly (cyphermox AT ubuntu.com), > or decline to provide one (since it would show up in the commit logs for > plymouth) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_f
Hello Mathieu, I hope you can see the sender mail-address. Thanks for your cooperation. It is nice to be able to contribute a little bit to Ubuntu/Linux. Gert On 12/4/18 8:43 PM, Mathieu Trudel-Lapierre wrote: > Gert, could you provide us with an email address so we can correctly > attribute the changes to you, given that you contributed the major part > of the patches that will go in plymouth? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close
I have the same problem on a fresh installed 18.10 for 32-bits, but only if external monitor is connected. Indeed this is a well known peoblem at internet. sudo journalctl -b -u systemd-logind with debugging on (systemd.log-level=debug) without external monitor shows succeeding suspend: Nov 29 16:56:04 Gert2 systemd-logind[438]: Lid closed Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scan all dirs Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scanning /sys/bus Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scanning /sys/class Nov 29 16:56:04 Gert2 systemd-logind[438]: Failed to open configuration file '/etc/systemd/sleep.conf': No such file or directory Nov 29 16:56:04 Gert2 systemd-logind[438]: Suspending... sudo journalctl -b -u systemd-logind with debugging on (systemd.log-level=debug) with connected external monitor shows refusing suspend: Nov 29 15:05:58 Gert2 systemd-logind[426]: Lid closed. Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning /sys/bus Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning /sys/class Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected. Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned off. Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning /sys/bus Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scanning /sys/class Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected. Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned off. Nov 29 15:05:59 Gert2 systemd-logind[426]: Got message type=method_call sender=:1.238 destination=:1.3 path=/org/freedesktop/login1/session/_32 interface=org.freedesktop.login1.Session member=ReleaseDevice cookie=154 reply_cookie=0 signature=uu error-name=n/a error-message=n/a Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=signal sender=n/a destination=:1.238 path=/org/freedesktop/login1/session/_32 interface=org.freedesktop.login1.Session member=PauseDevice cookie=227 reply_cookie=0 signature=uus error-name=n/a error-message=n/a Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got notification message from PID 426 (FDSTOREREMOVE=1, FDNAME=session-2-device-13-71) Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got explicit request to remove fd 174 (session-2-device-13-71), closing. Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=method_return sender=n/a destination=:1.238 path=n/a interface=n/a member=n/a cookie=228 reply_cookie=154 signature=n/a error-name=n/a error-message=n/a Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scan all dirs Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scanning /sys/bus Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scanning /sys/class Nov 29 15:05:59 Gert2 systemd-logind[426]: External (1) displays connected. Nov 29 15:05:59 Gert2 systemd-logind[426]: Refusing operation, as it is turned off. Nov 29 15:06:10 Gert2 systemd-logind[426]: Lid opened. The command systemd-inhibit --list shows next entry as soon as an external monitor is attached to the laptop. Who: gert (UID 1000/gert, PID 2342/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block So program gsd-power is responsible for inhibiting the handling of the lid-switch. The suspend-action will not occcur. This is not configurable and I think that is ridiculous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799038 Title: Ubuntu 18.10 does not suspend on lid close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Sorry, previous information wrong. At upgraded 18.04 I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs. At fresh 18.10 I have no package from cryptsetup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
No. I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs. For checking a fix for gnome-wayland I did a fresh install of 32-bits 18.10 from a "mini" (because no image available for 32-bits). Apparently this does not automatically install cryptsetup-initramfs. It is rather strange, correct working of plymouth is dependent of this package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
The patch I described before solves the problem, but for some reason plymouth does not attach the second renderer to the keyboard. Therefore switching to text-mode by pressing escape-key does not work. To make this work variable manager->local_console_managed must be set to false. This causes text-displays to be initialized twice for a terminal. So also code is added to avoid this. The complete patch including 2 smaller corrections described before is available at attached patchGK.txt. Note: default theme spinner is ugly and only a small time (partially) visible. Theme ubuntu-logo is very slow and causes regularly gdm-aborts, because drmMaster is not disabled soon enough by plymouth. Theme fade-in is a better default. ** Attachment added: "patchGK.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5214040/+files/patchGK.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
I do not have access to upstream and also have no idea what to add there. I have the impression the root cause of the plymouth crash is a configuration problem. I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10. At 18.10 file /usr/share/initramfs-tools/conf-hooks.d/cryptsetup is missing, which contains at 18.04 : # and for systems using plymouth instead, use the new option FRAMEBUFFER=y File /usr/share/initramfs-tools/hooks/framebuffer only loads kernel-module i915 and firmware for Intel-graphics-card into initramfs if FRAMEBUFFER=y. THerefore at 18.10 i915 is not loaded into initramfs. At 18.04 with i915 loaded, drm is initialized within 3 seconds kernel elapsed time, so before plymouth needs it. At 18.10 drm takes 20 seconds, so after plymouth needs it. By default plymouth waits max. 5 sec. for drm and then will use device fb0 with vesa. Later at initialization of drm this device fb0 with vesa will give a remove event. Plymouth does not handle this situation properly, because it refers memory of a renderer, which is already freed. I see no reason why this module i915 no longer is loaded at initramfs. Startup time is almost the same. The splash-screen can be shown earlier if present in initramfs. I think it simply is a bug in ubuntu or upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802993] Re: /sbin/plymouthd:plymouthd: ./plugin.c:1244: set_handler_for_input_source: Assertion `has_input_source (backend, input_source)' failed.
I do not have access to upstream and also have no idea what to add there. I have the impression the root cause of the plymouth crash is a configuration problem. I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10. At 18.10 file /usr/share/initramfs-tools/conf-hooks.d/cryptsetup is missing, which contains at 18.04 : # and for systems using plymouth instead, use the new option FRAMEBUFFER=y File /usr/share/initramfs-tools/hooks/framebuffer only loads kernel-module i915 and firmware for Intel-graphics-card into initramfs if FRAMEBUFFER=y. THerefore at 18.10 i915 is not loaded into initramfs. At 18.04 with i915 loaded, drm is initialized within 3 seconds kernel elapsed time, so before plymouth needs it. At 18.10 drm takes 20 seconds, so after plymouth needs it. By default plymouth waits max. 5 sec. for drm and then will use device fb0 with vesa. Later at initialization of drm this device fb0 with vesa will give a remove event. Plymouth does not handle this situation properly, because it refers memory of a renderer, which is already freed. I see no reason why this module i915 no longer is loaded at initramfs. Startup time is almost the same. The splash-screen can be shown earlier if present in initramfs. I think it simply is a bug in ubuntu or upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802993 Title: /sbin/plymouthd:plymouthd: ./plugin.c:1244: set_handler_for_input_source: Assertion `has_input_source (backend, input_source)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1802993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793309] Re: Backport netplan.io 0.40 to bionic
This change seems to be reverted somehow!? Briefly saw 0.40.x, installed the update, now the latest in repositories is 0.36.3: $ apt policy netplan.io netplan.io: Installed: 0.40.1~18.04.2 Candidate: 0.40.1~18.04.2 Version table: *** 0.40.1~18.04.2 100 100 /var/lib/dpkg/status 0.36.3 500 500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 0.36.1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793309 Title: Backport netplan.io 0.40 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1793309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Same problem as described before.
To force I use timeout 1 and theme fade-in. But same problem also occurred at
my PC with the default timeout 5, as was on the trace.
I will upload the crashdump (which by default was ignored by apport).
Routine ply_renderer_free does a hard free of renderer. So renderer cannot be
referenced later at deactivation of keyboard, because the memory might be
overwritten.
I wrote a routine which shlould be called before ply_renderer_free:
void
ply_device_manager_deactivate_keyboard (ply_device_manager_t *manager,
ply_renderer_t *renderer)
{
ply_list_node_t *node;
node = ply_list_get_first_node (manager->keyboards);
while (node != NULL) {
ply_keyboard_t *keyboard;
ply_list_node_t *next_node;
keyboard = ply_list_node_get_data (node);
next_node = ply_list_get_next_node (manager->keyboards, node);
if (ply_keyboard_get_renderer (keyboard) == renderer) {
ply_trace ("deactivating keyboard");
ply_keyboard_stop_watching_for_input (keyboard);
ply_list_remove_node (manager->keyboards, node);
break;
}
node = next_node;
}
}
At ply-keyboard.c:
c
ply_renderer_t *
ply_keyboard_get_renderer (ply_keyboard_t *keyboard)
{
assert (keyboard != NULL);
return keyboard->provider.if_renderer->renderer;
}
** Attachment added: "_sbin_plymouthd.0_33.crash.gz"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5210569/+files/_sbin_plymouthd.0_33.crash.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
ply_renderer_set_handler_for_input_source ->
ply_keyboard_stop_watching_for_renderer_input ->
ply_keyboard_stop_watching_for_input ->
ply_device_manager_deactivate_keyboards -> on_deactivate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
I think, I still get old stuff from 15-10 gert@Gert2:/var/cache/apt/archives$ dpkg -c libplymouth4_0.9.3-1ubuntu11~mtrudel4_i386.deb drwxr-xr-x root/root 0 2018-10-15 16:36 ./ drwxr-xr-x root/root 0 2018-10-15 16:36 ./lib/ drwxr-xr-x root/root 0 2018-10-15 16:36 ./lib/i386-linux-gnu/ -rw-r--r-- root/root 26056 2018-10-15 16:36 ./lib/i386-linux-gnu/libply-boot-client.so.4.0.0 -rw-r--r-- root/root112424 2018-10-15 16:36 ./lib/i386-linux-gnu/libply-splash-core.so.4.0.0 -rw-r--r-- root/root 46684 2018-10-15 16:36 ./lib/i386-linux-gnu/libply-splash-graphics.so.4.0.0 -rw-r--r-- root/root108160 2018-10-15 16:36 ./lib/i386-linux-gnu/libply.so.4.0.0 drwxr-xr-x root/root 0 2018-10-15 16:36 ./usr/ drwxr-xr-x root/root 0 2018-10-15 16:36 ./usr/share/ drwxr-xr-x root/root 0 2018-10-15 16:36 ./usr/share/doc/ drwxr-xr-x root/root 0 2018-10-15 16:36 ./usr/share/doc/libplymouth4/ -rw-r--r-- root/root 13853 2018-10-15 16:36 ./usr/share/doc/libplymouth4/changelog.Debian.gz -rw-r--r-- root/root 2523 2018-01-17 14:37 ./usr/share/doc/libplymouth4/copyright drwxr-xr-x root/root 0 2018-10-15 16:36 ./usr/share/lintian/ drwxr-xr-x root/root 0 2018-10-15 16:36 ./usr/share/lintian/overrides/ -rw-r--r-- root/root48 2018-01-17 14:37 ./usr/share/lintian/overrides/libplymouth4 lrwxrwxrwx root/root 0 2018-10-15 16:36 ./lib/i386-linux-gnu/libply-boot-client.so.4 -> libply-boot-client.so.4.0.0 lrwxrwxrwx root/root 0 2018-10-15 16:36 ./lib/i386-linux-gnu/libply-splash-core.so.4 -> libply-splash-core.so.4.0.0 lrwxrwxrwx root/root 0 2018-10-15 16:36 ./lib/i386-linux-gnu/libply-splash-graphics.so.4 -> libply-splash-graphics.so.4.0.0 lrwxrwxrwx root/root 0 2018-10-15 16:36 ./lib/i386-linux-gnu/libply.so.4 -> libply.so.4.0.0 gert@Gert2:/var/cache/apt/archives$ apt-cache policy plymouth plymouth: Installed: 0.9.3-1ubuntu11~mtrudel4 Candidate: 0.9.3-1ubuntu11~mtrudel4 Version table: *** 0.9.3-1ubuntu11~mtrudel4 500 500 http://ppa.launchpad.net/cyphermox/ppa/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status 0.9.3-1ubuntu10 500 500 http://nl.archive.ubuntu.com/ubuntu cosmic/main i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Problem not solved. I think I got 4 problems: 1) I think the second ppa (*mtrudel2*) has exacly same contents as the first one. At least the binaries and shared loadlibraries have the same time stamp (15 october). So this will not contain the last version. 2) I have the idea the shared loadlibs are not overwritten at the install. 3) The file /etc/plymouth/plymouthd.cfg, containing local settings was overwritten. I do not know if this is caused by "apt-get install" or by "make install" on localcode. According to contents of this file, this should not occur. 4) My proposed fix solves a bug, but probably not the problem. To verify updating of the loadlibs I did "make install" with my own local code including an extra tracing message. This crashed again with the usual stacktrace. I include the plymouth trace plymouth-debug_GK91.log. After the 5 seconds device timeout (caused by the missing setting to 10 seconds at /etc/plymouth/plymouthd.cfg) the frame buffer device /dev/fb0 is activated, because drm still not initialized. Also keyboard is activated for fb0. Later on the is en event: got remove event for device fb0, causing "ply_renderer_free:Unloading renderer backend plugin". At the end the keyboards are deactivated including the one for fb0, which is pointing to a non-existing backend. So I think also the keyboard should be removed (if present) if a device is removed. This should avoid the crash. but I doubt the splash will be displayed correctly. At my slow PC the problem is always reproducable by setting the timeout to 1. ** Attachment added: "plymouth-debug_GK91.log" https://bugs.launchpad.net/ubuntu/cosmic/+source/plymouth/+bug/1794292/+attachment/5209295/+files/plymouth-debug_GK91.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 *** https://bugs.launchpad.net/bugs/1745799 As stated above this bug report is not a duplicate and contains working code to solve the bug. Using this code doesn ot give any risk to the main stream of the code, it only handles an exception. I thought it might be a pleasure to get a solution for a problem. PLease do something with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795760 Title: Xwayland crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Proposing next improved code At src/libply-splash-core/ply-device-manager.c 1) at create_devices_for_subsystem (ply_device_manager_t *manager, const char *subsystem) change found_device = create_devices_for_udev_device (manager, device); into found_device = found_device || create_devices_for_udev_device (manager, device); 2) at create_devices_for_terminal_and_renderer_type (ply_device_manager_t *manager, const char *device_path, ply_terminal_t *terminal, ply_renderer_type_t renderer_type) change return; into return false; Notes at 1); As can be seen at the downloaded grub-trace, the graphical splash with keyboard is activated on 2 screens, before the device-timeout (which is set to 10.0). After the device-timeout routine create_devices_from_udev will call create_devices_for_subsystem (manager, SUBSYSTEM_DRM). This routine should return true if any drm-device is found. Because of the wrong code it returns only true if the last device is coorect. As can be seen at the downloaded grub-trace the last device /dev/dri/renderD128 is not usable. This causes at the trace-message: create_devices_from_udev:Creating non-graphical devices, since there's no suitable graphics hardware. This causes the second unwanted call to create_devices_for_terminal_and_renderer_type for non-graphical /dev/tty1, also listening to keyboard. Notes at 2) This is the solution for a compiler warning. It is just wrong coding, do not know if it will ever harm. Remark: For some reason at my PC the drm-devices are comimg up very slow at 18.10 (22 sec) compared to 18.04 (3 sec). To avoid the ugly text splash I had to enlarge DeviceTimeout from default 5 to 10. This does not slow down startuptime. cat /etc/plymouth/plymouthd.conf # Administrator customizations go in this file [Daemon] Theme=solar ShowDelay=0 DeviceTimeout=10 ** Attachment added: "plymouth-debug_GK7.log" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5207296/+files/plymouth-debug_GK7.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450763] Re: Syntax error: ")" unexpected
Wow, you replied to a report from 2015. ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450763 Title: Syntax error: ")" unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/1450763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799534] [NEW] Category view kicks scrolling upward on tile click
Public bug reported: When I click on an application tile that is above the horizontal center line of the window in one of the category views it kicks the scrolling up to some point. Clicking a tile again will not kick the scroll up a second time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 20:09:05 2018 InstallationDate: Installed on 2018-10-19 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799534 Title: Category view kicks scrolling upward on tile click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798952] [NEW] Ubuntu Software back button does not work
Public bug reported: Ubuntu Software back button generally does not operate. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 14:01:51 2018 InstallationDate: Installed on 2018-10-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu5 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798952 Title: Ubuntu Software back button does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Unfortunately again it crashes, logging on with gdm3, both with and without wayland. The crash seems to be at the same place. Syslog: Oct 16 16:04:13 Gert2 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV Oct 16 16:04:13 Gert2 gdm3[710]: error: unexpectedly disconnected from boot status daemon Oct 16 16:04:13 Gert2 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. Oct 16 16:04:14 Gert2 systemd[1]: Started Hold until boot process finishes up. Oct 16 16:04:14 Gert2 systemd[1]: Starting Set console scheme... Oct 16 16:04:14 Gert2 systemd-networkd[392]: wlan0: Gained IPv6LL Oct 16 16:04:14 Gert2 systemd-timesyncd[393]: Network configuration changed, trying to establish connection. Oct 16 16:04:14 Gert2 dhclient[795]: DHCPACK of 192.168.178.20 from 192.168.178.1 Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3397] dhcp4 (wlan0): address 192.168.178.20 Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3398] dhcp4 (wlan0): plen 24 (255.255.255.0) Oct 16 16:04:14 Gert2 avahi-daemon[525]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.20. Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3398] dhcp4 (wlan0): gateway 192.168.178.1 Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3398] dhcp4 (wlan0): lease time 3600 Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3399] dhcp4 (wlan0): nameserver '89.101.251.228' Oct 16 16:04:14 Gert2 avahi-daemon[525]: New relevant interface wlan0.IPv4 for mDNS. Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3399] dhcp4 (wlan0): nameserver '89.101.251.229' Oct 16 16:04:14 Gert2 avahi-daemon[525]: Registering new address record for 192.168.178.20 on wlan0.IPv4. Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3399] dhcp4 (wlan0): domain name 'dynamic.ziggo.nl' Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3400] dhcp4 (wlan0): state changed unknown -> bound Oct 16 16:04:14 Gert2 systemd-timesyncd[393]: Network configuration changed, trying to establish connection. Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3537] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3640] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3663] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Oct 16 16:04:14 Gert2 NetworkManager[529]: [1539698654.3690] manager: NetworkManager state is now CONNECTED_LOCAL Oct 16 16:04:14 Gert2 systemd[1]: Started Set console scheme. Syslog, if plymouth not crashes: Oct 16 15:54:10 Gert2 systemd[1]: Received SIGRTMIN+21 from PID 353 (plymouthd). Oct 16 15:54:10 Gert2 systemd[1]: Started Hold until boot process finishes up. Oct 16 15:54:10 Gert2 systemd[1]: Starting Set console scheme... Oct 16 15:54:10 Gert2 systemd[1]: Started Set console scheme. ProblemType: Crash Architecture: i386 Date: Tue Oct 16 16:04:11 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /sbin/plymouthd ExecutableTimestamp: 1539614166 I tried to make a symbolic stackdump, but that failed SegvAnalysis: Segfault happened at: 0xb7f80d29 : mov0x3c(%edx),%eax PC (0xb7f80d29) ok source "0x3c(%edx)" (0x3833696b) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA SourcePackage: plymouth Stacktrace: #0 0xb7f80d29 in ply_renderer_set_handler_for_input_source () at /lib/i386-linux-gnu/libply-splash-core.so.4 #1 0xb7f79ccd in ply_keyboard_stop_watching_for_input () at /lib/i386-linux-gnu/libply-splash-core.so.4 #2 0xb7f78fa0 in ply_device_manager_deactivate_keyboards () at /lib/i386-linux-gnu/libply-splash-core.so.4 #3 0x0043bccf in () #4 0x00434d23 in _start () StacktraceAddressSignature: /sbin/plymouthd:11:/lib/i386-linux-gnu/libply-splash-core.so.4.0.0+ad29:/lib/i386-linux-gnu/libply-splash-core.so.4.0.0+3ccd:/lib/i386-linux-gnu/libply-splash-core.so.4.0.0+2fa0:/sbin/plymouthd+accf:/sbin/plymouthd+3d23 StacktraceTop: ply_renderer_set_handler_for_input_source () at /lib/i386-linux-gnu/libply-splash-core.so.4 ply_keyboard_stop_watching_for_input () at /lib/i386-linux-gnu/libply-splash-core.so.4 ply_device_manager_deactivate_keyboards () at /lib/i386-linux-gnu/libply-splash-core.so.4 () _start () Tags: cosmic third-party-packages TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth ThreadStacktrace: . Thread 1 (Thread 0xb7c33f00 (LWP 348)): #0 0xb7f80d29 in ply_renderer_set_handler_for_input_source () at /lib/i386-linux-gnu/libply-splash-core.so.4 #1 0xb7f79ccd in ply_keyboard_stop_watching_for_input () at /lib/i386-linux-gnu/libply-splash-core.so.4 #2 0xb7f78fa0 in ply_device_manager_deactivate_keyboards () at /lib/i386-l
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
** Description changed: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. + No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: + Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. + Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor + Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw + + glxinfo: + OpenGL vendor string: VMware, Inc. + OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) + OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 + OpenGL core profile shading language version string: 3.30 + OpenGL core profile context flags: (none) + OpenGL core profile profile mask: core profile + OpenGL core profile extensions: + OpenGL version string: 3.1 Mesa 18.2.2 + OpenGL shading language version string: 1.40 + OpenGL context flags: (none) + OpenGL extensions: + OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 + OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 + OpenGL ES profile extensions: + ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: - b'org.gnome.shell' b'command-history' redacted by apport - b'org.gnome.shell' b'app-picker-view' b'uint32 1' - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'command-history' redacted by apport + b'org.gnome.shell' b'app-picker-view' b'uint32 1' + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797882] [NEW] At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Public bug reported: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cosmic i386 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
Sorry,
Code was not quite complete.
It misses freeing the error.
New version:
texture = COGL_TEXTURE (cogl_texture_2d_new_from_bitmap (bitmap));
cogl_texture_set_components (COGL_TEXTURE (texture), components);
if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
{
g_clear_pointer (&texture, cogl_object_unref);
cogl_error_free (*error);
*error = NULL;
texture = COGL_TEXTURE (cogl_texture_2d_sliced_new_from_bitmap (bitmap,
COGL_TEXTURE_MAX_WASTE));
cogl_texture_set_components (COGL_TEXTURE (texture), components);
if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
g_clear_pointer (&texture, cogl_object_unref);
}
wl_shm_buffer_end_access (shm_buffer);
cogl_object_unref (bitmap);
buffer->texture = texture;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
I do not think this is a duplicate of bug #1745799.
At this comment I will try to give a code to solve this bug.
My symbol Xwaylnd-crash shows the next trace:
#6 0x0062b600 in FatalError (f=0x63704e "%s") at ../../../../os/log.c:1015
args = 0xbf9c7844 "\\x\234\277"
args2 = 0xbf9c7844 "\\x\234\277"
beenhere = 1
#7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n",
args=0xbf9c7994 "\027uܷ\255\001") at ../../../../../hw/xwayland/xwayland.c:1137
msg = "wl_surface@429: error 2: Failed to create a texture for surface
429: Failed to create texture 2d due to size/format constraints\n", '\000'
#8 0xb7dc5fef in wl_log (fmt=0xb7dc71ea "%s@%u: error %d: %s\n") at
../src/wayland-util.c:404
Problem can be solved by using slicing at shm_buffer_attach() at
src/wayland/meta-wayland-buffer.c, if size of texture is too large for
graphics card. Code for freeing the bitmap is now positioned after the
if.
This results into the following code:
texture = COGL_TEXTURE (cogl_texture_2d_new_from_bitmap (bitmap));
cogl_texture_set_components (COGL_TEXTURE (texture), components);
if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
{
g_clear_pointer (&texture, cogl_object_unref);
texture = COGL_TEXTURE (cogl_texture_2d_sliced_new_from_bitmap (bitmap,
COGL_TEXTURE_MAX_WASTE));
cogl_texture_set_components (COGL_TEXTURE (texture), components);
if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
g_clear_pointer (&texture, cogl_object_unref);
}
wl_shm_buffer_end_access (shm_buffer);
cogl_object_unref (bitmap);
buffer->texture = texture;
This code is working and makes it possible to login with wayland with
dual screen without any monitors.xml-config on small/old graphic cards.
Slicing is causing next message:
Oct 13 15:51:36 Gert2 gnome-shell[1994]: Skipping layers 1..n of your pipeline
since the first layer is sliced. We don't currently support any multi-texturing
with sliced textures but assume layer 0 is the most important to keep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height() from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_e
Problem can be solved at update_fbo() within clutter/clutter/clutter-
offscreen-effect.c
In this case at update_fbo a texture should be alocated with width 2560 which
is greater than maximal size 2048 of graphics cards.
Offscreen-effect does not support sliced textures, so this is impossible and
fails.
Crash occurs because no texture is allocated but a framebuffer is present at
priv->offscreen.
Code to free the framebuffer at priv->offscreen should be moved upwards at
update_fbo, because it also should be executed in case texture allocation fails.
This leads to the fillowing proposed code:
if (priv->texture != NULL)
{
cogl_handle_unref (priv->texture);
priv->texture = NULL;
}
if (priv->offscreen != NULL)
{
cogl_handle_unref (priv->offscreen);
priv->offscreen = NULL;
}
priv->texture =
clutter_offscreen_effect_create_texture (self, fbo_width, fbo_height);
if (priv->texture == NULL)
return FALSE;
cogl_pipeline_set_layer_texture (priv->target, 0, priv->texture);
priv->fbo_width = fbo_width;
priv->fbo_height = fbo_height;
priv->offscreen = cogl_offscreen_new_to_texture (priv->texture);
Remember bug 1790525 also should be solved (which often causes an earlier
crash), to make the solution complete.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795774
Title:
gnome-shell crashed with SIGSEGV in cogl_texture_get_height() from
clutter_offscreen_effect_real_paint_target() from
clutter_offscreen_effect_paint_texture() from
clutter_offscreen_effect_paint() from clutter_actor_continue_paint()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795774/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
At my laptop it happens at (almost) every start. FYI I attach a symbolic trace ** Attachment added: "symbolic trace of crash after released fix" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5197512/+files/stack1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794292] Re: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_i
Unfortunately the fix does not solve the problem and still crashes. ProblemType: Crash Architecture: i386 Date: Thu Oct 4 16:54:33 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /sbin/plymouthd ExecutableTimestamp: 1538408760 MachineType: Dell Inc. Latitude D620 Package: plymouth 0.9.3-1ubuntu9 PackageArchitecture: i386 SegvAnalysis: Segfault happened at: 0xb7f279f9 : mov0x3c(%edx),%eax PC (0xb7f279f9) ok source "0x3c(%edx)" (0x003d) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA SourcePackage: plymouth Stacktrace: #0 0xb7f279f9 in ply_renderer_set_handler_for_input_source () at /lib/i386-linux-gnu/libply-splash-core.so.4 #1 0xb7f209a9 in ply_keyboard_stop_watching_for_input () at /lib/i386-linux-gnu/libply-splash-core.so.4 #2 0xb7f1fe70 in ply_device_manager_deactivate_keyboards () at /lib/i386-linux-gnu/libply-splash-core.so.4 #3 0x00428c02 in () #4 0x00421cf3 in _start () StacktraceAddressSignature: /sbin/plymouthd:11:/lib/i386-linux-gnu/libply-splash-core.so.4.0.0+a9f9:/lib/i386-linux-gnu/libply-splash-core.so.4.0.0+39a9:/lib/i386-linux-gnu/libply-splash-core.so.4.0.0+2e70:/sbin/plymouthd+ac02:/sbin/plymouthd+3cf3 StacktraceTop: ply_renderer_set_handler_for_input_source () at /lib/i386-linux-gnu/libply-splash-core.so.4 ply_keyboard_stop_watching_for_input () at /lib/i386-linux-gnu/libply-splash-core.so.4 ply_device_manager_deactivate_keyboards () at /lib/i386-linux-gnu/libply-splash-core.so.4 () _start () Tags: cosmic TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth ThreadStacktrace: . Thread 1 (Thread 0xb7bdaf00 (LWP 334)): #0 0xb7f279f9 in ply_renderer_set_handler_for_input_source () at /lib/i386-linux-gnu/libply-splash-core.so.4 #1 0xb7f209a9 in ply_keyboard_stop_watching_for_input () at /lib/i386-linux-gnu/libply-splash-core.so.4 #2 0xb7f1fe70 in ply_device_manager_deactivate_keyboards () at /lib/i386-linux-gnu/libply-splash-core.so.4 #3 0x00428c02 in () #4 0x00421cf3 in _start () Title: plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794292 Title: plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795089] Re: Gnome-shell crashes if dual monitor connected
** Package changed: evince (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795089 Title: Gnome-shell crashes if dual monitor connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795089] [NEW] Gnome-shell crashes if dual monitor connected
Public bug reported:
THis contains a fresh install of Ubuntu 18.10 to verify the solution at bug
1727356, for Intel-graphic-cards,
which do not support OpenGL 2.1 or higher.
This solution works.
A fresh install does not contain any monitors.xml file, to describe the dual
monitor-configuration.
I try to connect an internal laptop-monitor LVDS1 with maximal density 1280 x
800 and an external monitor VGA1
with density 1280 x 1024.
Display-manager gdm3 by default configures the external monitor at the right
side of the laptop-monitor.
This results into a logical screen of 2560 x 1024.
THe graphics card only supports a maximal width and height of 2048.
Therefore textures, that are too large, are splitted into multiple slices,
that fit.
Unfortunately this is not always done, causing textures of size 2560 x 1024 not
being allocated and crashing.
A quick and dirty hardcoded solution limiting the width to 2048
eliminates the crashes:
At cogl/cogl/cogl-texture-2d-sliced.c module setup_spans:
/* Negative number means no slicing forced by the user */
if (max_waste <= -1)
{
CoglSpan span;
if (max_width > 2048)
max_width = 2048;
At cogl/cogl/driver/gl/cogl-texture-2d-gl.c routine allocate_from_bitmap:
internal_format =
_cogl_texture_determine_internal_format (tex, cogl_bitmap_get_format (bmp));
if (width > 2048)
width = 2048;
In fact the external monitor is physically positioned above the laptop-monitor
and this is the configuration we want.
This results into a logical screen of 1280 x 1824 within the limits of the
graphics card.
To get this configuration the file monitors.xml was copied to $HOME/.config and
to /var/lib/gdm3/.config (to configure login screen).
By default Ubuntu 18.10 uses gdm3 with wayland at the login-screen and gdm3
without wayland after login.
Display-manager gdm3 with wayland ignores this monitors.xml file. To make the
file also usable for wayland the
must be copied with VGA-1 i.s.o.
VGA1 and
LVDS-1 i.s.o. LVDS1 .
Curious!@#$#.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic i686
ApportVersion: 2.20.10-0ubuntu11
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 29 01:41:55 2018
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug cosmic i386
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795089
Title:
Gnome-shell crashes if dual monitor connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795089/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Proposed solution:
As the stacktrace below shows the problem is caused by module
cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by
default is configured by gdm3 with wayland for 2 monitors.
This is not supported by graphics-card, causing error "Failed to create texture
2d due to size/format constraints".
The error is freed by cogl_texture_new_with_size, but the variable skip_error
is not set to NULL by the call to cogl_error_free (because the parameter is a
copy).
Then module tries to allocate a slice with max_waste -1. This also fails,
causing error "Sliced texture size of 2560 x 1024 not possible with max waste
set to -1".
Module cogl_set_error complains about the skip_error not being NULL with
message "CoglError set...", but does not set a new value to skip_error.
Also the second error is programmed to be freed by cogl_error_free at
cogl_texture_new_with_size, that in this way tries to free the same memory
twice. This causes the crash "double free or corruption (fasttop)", unless by
accident the same memory-address is allocated again.
To solve, the statement skip_error = NULL; should be added:
cogl_texture_new_with_size (unsigned int width,
unsigned int height,
CoglTextureFlags flags,
CoglPixelFormat internal_format)
{
CoglTexture *tex;
CoglError *skip_error = NULL;
_COGL_GET_CONTEXT (ctx, NULL);
if ((_cogl_util_is_pot (width) && _cogl_util_is_pot (height)) ||
(cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_BASIC) &&
cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_MIPMAP)))
{
/* First try creating a fast-path non-sliced texture */
tex = COGL_TEXTURE (cogl_texture_2d_new_with_size (ctx, width, height));
_cogl_texture_set_internal_format (tex, internal_format);
if (!cogl_texture_allocate (tex, &skip_error))
{
cogl_error_free (skip_error);
skip_error = NULL;
This solution is tested and solves the problem during startup and for right
corner click.
Stacktrace with modulenames/linenumbers:
Package: gnome-shell 3.30.0-1ubuntu2
Stacktrace:
#0 0xb7ef9d41 in __kernel_vsyscall ()
#1 0xb6a4e512 in __libc_signal_restore_set (set=0xbfcb8a0c) at
../sysdeps/unix/sysv/linux/internal-signals.h:84
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#2 0xb6a4e512 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#3 0xb6a382b6 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb7996077 ,
sa_sigaction = 0xb7996077 }, sa_mask = {__val = {3080956952,
3060745084, 3080120357, 3217787880, 3060745084, 3217788000, 32868, 20347328, 0,
28984448, 2237142784, 3060745084, 3080120310, 3080956952, 3080956952,
3217788408, 1024, 31097824, 3080018485, 3060691022, 16, 3060756628, 0, 3, 4096,
3065078356, 2, 3066019840, 4096, 3217788168, 3064530671, 0}}, sa_flags = 4096,
sa_restorer = 0x3}
sigs = {__val = {32, 0 }}
#4 0xb6a9074c in __libc_message (action=do_abort, fmt=) at
../sysdeps/posix/libc_fatal.c:181
ap =
fd = 2
list =
nlist =
cp =
written =
#5 0xb6a975dd in malloc_printerr (str=str@entry=0xb6ba525c "double free or
corruption (fasttop)") at malloc.c:5336
#6 0xb6a98e6f in _int_free (av=, p=,
have_lock=) at malloc.c:4216
idx = 6
old =
old2 =
size =
fb =
nextchunk =
nextsize =
nextinuse =
prevsize =
bck =
fwd =
__PRETTY_FUNCTION__ = "_int_free"
#7 0xb7954290 in g_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#8 0xb7938c53 in g_error_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#9 0xb66d7058 in cogl_error_free (error=0x16cba70) at cogl-error.c:45
#10 0xb66db62c in cogl_texture_new_with_size (width=2560, height=1024,
flags=COGL_TEXTURE_NO_SLICING, internal_format=COGL_PIXEL_FORMAT_RGBA__PRE)
at deprecated/cogl-auto-texture.c:121
tex = 0x1da83e0
skip_error = 0x16cba70
ctx =
#11 0xb6e9a618 in clutter_offscreen_effect_real_create_texture
(effect=0x23c3b00
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Extra info: 1.The syslog at a crash shows next error. Probably memory management at an errormemssage is not correct. Also look at the size 2560 x 1024 Sep 08 00:18:35 Gert2 gnome-shell[2141]: CoglError set over the top of a previous CoglError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: double free or corruption (fasttop) Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: GNOME Shell crashed with signal 6 2.It looks like the problem in an older problem. At least at Ubuntu 18.04 with display manager lightdm the same crash occurs if no monitors.xml is present and dual monitor is present. 3.It looks like the problem is caused by the different sizes of the monitors. At startup gdm3 detects next sizes for laptop-monitor and external monitor: Sep 9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output LVDS1 using initial mode 1280x800 on pipe 1 Sep 9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output VGA1 using initial mode 1280x1024 on pipe 0 If at logon there is no monitors.xml file for the user, gdm3 by default tries to configure the external VGA1-monitor at the right of the laptop LVDS1-monitor. This fails, probably because the vertical size 800 of LVDS1 is smaller than 1024 for VGA1. gdm3 retries, which is causing a loop until VDA1-monitor is disconnected (see next log): Sep 9 20:23:05 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800 Sep 9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024 Sep 9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none Sep 9 20:23:18 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800 Sep 9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024 Sep 9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none 4.If monitors.xml is present with configuration of VGA1 above LVDS1, dual monitors can be used. Also in this case it is not possible to graphically configure via the displays arrangement the configuration with above sizes and VGA1 right of LVDS1. 5. A correct monitors.xml-file does not totally solve the problem. Frequently the start if Ubuntu hangs completely before showing the logon-screen. It is showing a character screen with next last line. [ OK ] Started GNOME Display Manager. Syslog gives next lines then: Sep 9 00:40:47 Gert2 gnome-shell[1309]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1573]: reference to undefined property "MetaWindowXwayland" Sep 9 00:40:47 Gert2 gnome-shell[1309]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints Sep 9 00:40:47 Gert2 gnome-shell[1309]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Sep 9 00:40:47 Gert2 org.gnome.Shell.desktop[1309]: double free or corruption (fasttop) Sep 9 00:40:48 Gert2 org.gnome.Shell.desktop[1309]: (EE) failed to read Wayland events: Connection reset by peer Sep 9 00:40:48 Gert2 gnome-session[1290]: gnome-session-binary[1290]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Sep 9 00:40:48 Gert2 gnome-session-binary[1290]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Sep 9 00:40:48 Gert2 gnome-session-binary[1290]: Unrecoverable failure in required component org.gnome.Shell.desktop 6. If at the logon-screen the arrow at upper right corner is clicked (to exit), also the system hangs with character-screen and same kind of error at syslog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
