[Touch-packages] [Bug 1627564] Re: Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494]
Tracking upstream in https://gitlab.gnome.org/GNOME/gtk/-/issues/3077 ** Summary changed: - Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) + Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494] ** Changed in: gtk+3.0 (Ubuntu) Status: Invalid => Confirmed ** Tags added: hirsute ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Description changed: https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689 https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383 + https://errors.ubuntu.com/problem/519aee3ed0c68efc5b754ee3e783103e59361d46 --- bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #3077 https://gitlab.gnome.org/GNOME/gtk/-/issues/3077 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/3077 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1627564 Title: Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494] Status in GTK+: Unknown Status in debconf package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in debconf source package in Focal: Confirmed Status in gtk+3.0 source package in Focal: Invalid Bug description: https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689 https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383 https://errors.ubuntu.com/problem/519aee3ed0c68efc5b754ee3e783103e59361d46 --- bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1627564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627564] Re: Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494]
It sounds like it arises with specific (broken?) icon themes so one potential workaround is to change icon theme. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1627564 Title: Various apps crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493/494] Status in GTK+: Unknown Status in debconf package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in debconf source package in Focal: Confirmed Status in gtk+3.0 source package in Focal: Invalid Bug description: https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689 https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383 https://errors.ubuntu.com/problem/519aee3ed0c68efc5b754ee3e783103e59361d46 --- bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1627564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922340] Re: GNOME lock screen wallpaper turns black on main display
** No longer affects: wayland (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3206 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1922340 Title: GNOME lock screen wallpaper turns black on main display Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) gnome-shell: Installed: 3.38.4-1ubuntu1 Candidate: 3.38.4-1ubuntu1 Version table: *** 3.38.4-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg. After the screen stays off and locked for some time the wallpaper on the main display turns black. It never happens on the secondary display. The issue is also reported, here on gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:50:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1908818] Re: pure packaging of libnss3
@paelzer - we just got another duplicate of this filed for nss in groovy
- is the server team working on a fix for this for groovy?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
Fix Released
Status in nss source package in Groovy:
Triaged
Status in nss source package in Hirsute:
Fix Released
Bug description:
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to
x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922553] Re: libnss3 package contains invalid library paths
*** This bug is a duplicate of bug 1908818 ***
https://bugs.launchpad.net/bugs/1908818
** This bug has been marked a duplicate of bug 1908818
pure packaging of libnss3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1922553
Title:
libnss3 package contains invalid library paths
Status in nss package in Ubuntu:
New
Bug description:
libnss3 package installs these files:
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}
Here, ${DEB_HOST_MULTIARCH} is the literal name of the directory
created in the filesystem. Presumably, this is caused by incorrect
syntax of the variable used in the packaging scripts.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-48.54-lowlatency 5.8.18
Uname: Linux 5.8.0-48-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 5 14:19:22 2021
InstallationDate: Installed on 2015-05-01 (2165 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: nss
UpgradeStatus: Upgraded to groovy on 2020-11-22 (134 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1922553/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922640] [NEW] Long String crash libreadline in built-in function input() of Python
Public bug reported: In input() of Python(CPython), it calls rl_callback_handler_install (prompt, rlhandler) in libreadline. If prompt is a byte string of 60,000 bytes, it will cause crash. e.g. input([1,2]*1) System: Ubuntu 16.04 Step to Reproduce: Python 3.9.2 (default, Mar 12 2021, 15:08:35) [GCC 7.5.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> input([1,2]*1) *** Error in `/home/xxm/Desktop/apifuzz/Python-3.9.2/python': realloc(): invalid next size: 0x0135fd40 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x777f5)[0x7f714431b7f5] /lib/x86_64-linux-gnu/libc.so.6(+0x834da)[0x7f71443274da] /lib/x86_64-linux-gnu/libc.so.6(realloc+0x199)[0x7f71443288a9] /lib/x86_64-linux-gnu/libreadline.so.6(xrealloc+0xe)[0x7f71446a1ffe] /lib/x86_64-linux-gnu/libreadline.so.6(rl_redisplay+0x125f)[0x7f714469451f] /lib/x86_64-linux-gnu/libreadline.so.6(readline_internal_setup+0xb0)[0x7f7144681340] /lib/x86_64-linux-gnu/libreadline.so.6(+0x2a4ac)[0x7f71446984ac] /home/xxm/Desktop/apifuzz/Python-3.9.2/python[0x5d60b2] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(PyOS_Readline+0x116)[0x5da536] /home/xxm/Desktop/apifuzz/Python-3.9.2/python[0x648495] /home/xxm/Desktop/apifuzz/Python-3.9.2/python[0x613f26] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(_PyEval_EvalFrameDefault+0x54e2)[0x4267a2] /home/xxm/Desktop/apifuzz/Python-3.9.2/python[0x4fa3e9] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(PyEval_EvalCode+0x36)[0x4fa746] /home/xxm/Desktop/apifuzz/Python-3.9.2/python[0x543adf] /home/xxm/Desktop/apifuzz/Python-3.9.2/python[0x546d82] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(PyRun_InteractiveLoopFlags+0x8e)[0x54704e] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(PyRun_AnyFileExFlags+0x3c)[0x5478fc] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(Py_RunMain+0x8d7)[0x42b1e7] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(Py_BytesMain+0x56)[0x42b586] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f71442c4840] /home/xxm/Desktop/apifuzz/Python-3.9.2/python(_start+0x29)[0x42a289] === Memory map: 0040-00762000 r-xp 08:07 7740578 /home/xxm/Desktop/apifuzz/Python-3.9.2/python 00961000-00962000 r--p 00361000 08:07 7740578 /home/xxm/Desktop/apifuzz/Python-3.9.2/python 00962000-0099a000 rw-p 00362000 08:07 7740578 /home/xxm/Desktop/apifuzz/Python-3.9.2/python 0099a000-009be000 rw-p 00:00 0 012dc000-013ce000 rw-p 00:00 0 [heap] 7f713c00-7f713c021000 rw-p 00:00 0 7f713c021000-7f714000 ---p 00:00 0 7f71439b5000-7f71439cc000 r-xp 08:07 1966109 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f71439cc000-7f7143bcb000 ---p 00017000 08:07 1966109 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f7143bcb000-7f7143bcc000 r--p 00016000 08:07 1966109 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f7143bcc000-7f7143bcd000 rw-p 00017000 08:07 1966109 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f7143bf-7f714407b000 r--p 08:07 4326136 /usr/lib/locale/locale-archive 7f714407b000-7f71440a r-xp 08:07 1970777 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f71440a-7f714429f000 ---p 00025000 08:07 1970777 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f714429f000-7f71442a3000 r--p 00024000 08:07 1970777 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f71442a3000-7f71442a4000 rw-p 00028000 08:07 1970777 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f71442a4000-7f7144464000 r-xp 08:07 1966308 /lib/x86_64-linux-gnu/libc-2.23.so 7f7144464000-7f7144664000 ---p 001c 08:07 1966308 /lib/x86_64-linux-gnu/libc-2.23.so 7f7144664000-7f7144668000 r--p 001c 08:07 1966308 /lib/x86_64-linux-gnu/libc-2.23.so 7f7144668000-7f714466a000 rw-p 001c4000 08:07 1966308 /lib/x86_64-linux-gnu/libc-2.23.so 7f714466a000-7f714466e000 rw-p 00:00 0 7f714466e000-7f71446ab000 r-xp 08:07 1970756 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f71446ab000-7f71448ab000 ---p 0003d000 08:07 1970756 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f71448ab000-7f71448ad000 r--p 0003d000 08:07 1970756 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f71448ad000-7f71448b3000 rw-p 0003f000 08:07 1970756 /lib/x86_64-linux-gnu/libreadline.so.6.3 7f71448b3000-7f71448b4000 rw-p 00:00 0 7f71448b4000-7f71449bc000 r-xp 08:07 1966312 /lib/x86_64-linux-gnu/libm-2.23.so 7f71449bc000-7f7144bbb000 ---p 00108000 08:07 1966312 /lib/x86_64-linux-gnu/libm-2.23.so 7f7144bbb000-7f7144bbc000 r--p 00107000 08:07 1966312 /lib/x86_64-linux-gnu/libm-2.23.so 7f7144bbc000-7f7144bbd000 rw-p 00108000 08:07 1966312 /lib/x86_64-linux-gnu/libm-2.23.so 7f7144bbd000-7f7144bbf000 r-xp 08:07 1966307 /lib/x86_64-linux-gnu/libutil-2.23.so 7f7144bbf000-7f7144dbe000 ---p 2000 08:07 1966307 /lib/x86_64-linux-gnu/libutil-2.23.so 7f7144dbe000-7f7144dbf000 r--p 1000 08:07 1966307 /lib/x86_64-linux-gnu/libutil-2.23.so 7f7144dbf000-7f7144dc rw-p 00
[Touch-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)
Reopened (like the upstream bug) to avoid confusion about the fix not being enabled by default. You just need to run: gsettings set org.gnome.mutter experimental-features "['kms- modifiers']" But we can close this again after that's been done automatically in a future release. ** Changed in: mutter (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1896171 Title: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in Mutter: Unknown Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Triaged Bug description: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
The fix looks simple enough. We probably want to patch it ASAP: https://gitlab.freedesktop.org/mesa/mesa/-/commit/58e43594fc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922621] [NEW] PulseAudio Assertion 'section' in pa_alsa_element_get() when laptop in docking station
Public bug reported: PulseAudio 1:13.99.1-1ubuntu3.10, Ubuntu 20.04.2 Laptop: Lenovo ThinkPad X1 Carbon 7th Soundcards: 0 [sofhdadsp ]: sof-hda-dsp - sof-hda-dsp LENOVO-20QES01L00-ThinkPadX1Carbon7th 1 [Audio ]: USB-Audio - ThinkPad Dock USB Audio Generic ThinkPad Dock USB Audio at usb-:00:14.0-5.4.4, high speed When the laptop is not docked, everything works fine. Sound is played using the laptop internal speakers. When the laptop is in the docking station, the sound in KDE is not working (no sound devices are shown). Pulseaudio is crashing with an Assertion. D: [pulseaudio] alsa-mixer.c: Profile output:analog-stereo supported. D: [pulseaudio] conf-parser.c: Parsing configuration file '/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf' D: [pulseaudio] conf-parser.c: Parsing configuration file '/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common' E: [pulseaudio] alsa-mixer.c: Assertion 'section' failed at modules/alsa/alsa-mixer.c:1954, function pa_alsa_element_get(). Aborting. Prime suspect for the change is an "Embedded Controller Update" by fwupdmgr, which was installed a while ago, and applied during last reboot. This cannot be downgraded (Lenovo does not support that). More details from "pulseaudio -", docked: I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: ""). D: [pulseaudio] database-tdb.c: Opened TDB database '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database.tdb' I: [pulseaudio] module-card-restore.c: Successfully opened database file '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database'. I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: ""). I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; argument: ""). I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: #4; argument: ""). D: [pulseaudio] module.c: Checking for existence of '/usr/lib/pulse-13.99.1/modules/module-switch-on-connect.so': success I: [pulseaudio] module.c: Loaded "module-switch-on-connect" (index: #5; argument: ""). D: [pulseaudio] module.c: Checking for existence of '/usr/lib/pulse-13.99.1/modules/module-udev-detect.so': success D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC1 is accessible: yes D: [pulseaudio] module-udev-detect.c: /devices/pci:00/:00:14.0/usb1/1-5/1-5.4/1-5.4.4/1-5.4.4:1.0/sound/card1 is busy: no D: [pulseaudio] module-udev-detect.c: Loading module-alsa-card with arguments 'device_id="1" name="usb-Generic_ThinkPad_Dock_USB_Audio-00" card_name="alsa_card.usb-Generic_ThinkPad_Dock_USB_Audio-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1"' D: [pulseaudio] dbus-util.c: Successfully connected to D-Bus session bus 0dd0d23e5ac302eec692d2b2606b9c78 as :1.81 D: [pulseaudio] reserve-wrap.c: Successfully acquired reservation lock on device 'Audio1' I: [pulseaudio] (alsa-lib)main.c: error: failed to import hw:1 use case configuration -2 I: [pulseaudio] (alsa-lib)main.c: error: failed to import ThinkPad Dock USB Audio use case configuration -2 I: [pulseaudio] alsa-ucm.c: UCM not available for card ThinkPad Dock USB Audio D: [pulseaudio] conf-parser.c: Parsing configuration file '/usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf' D: [pulseaudio] alsa-mixer.c: Looking at profile input:analog-stereo D: [pulseaudio] alsa-mixer.c: Checking for recording on Analog Stereo (analog-stereo) D: [pulseaudio] alsa-util.c: Trying front:1 with SND_PCM_NO_AUTO_FORMAT ... Not docked: I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: ""). D: [pulseaudio] database-tdb.c: Opened TDB database '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database.tdb' I: [pulseaudio] module-card-restore.c: Successfully opened database file '/home/ads/.pulse/8815a710d4ce4667b8c98403eec58bed-card-database'. I: [pulseaudio] module.c: Loaded "module-card-restore" (index: #2; argument: ""). I: [pulseaudio] module.c: Loaded "module-augment-properties" (index: #3; argument: ""). I: [pulseaudio] module.c: Loaded "module-switch-on-port-available" (index: #4; argument: ""). D: [pulseaudio] module.c: Checking for existence of '/usr/lib/pulse-13.99.1/modules/module-switch-on-connect.so': success I: [pulseaudio] module.c: Loaded "module-switch-on-connect" (index: #5; argument: ""). D: [pulseaudio] module.c: Checking for existence of '/usr/lib/pulse-13.99.1/modules/module-udev-detect.so': success D: [pulseaudio] module-udev-detect.c: /dev/snd/controlC0 is accessible: yes D: [pulseaudio] module-udev-detect.c: /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0 is busy: no D: [pulseaudio] module-udev-detect.c: Loading module-alsa-card with arguments 'device_id="0" name="pci-_00_1f.3-platform-skl_hda_dsp_generic"
[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
** Description changed: + [Impact] + + * This issue affects AMD graphics on Xfwm4 4.14.1. + + * Windows are displayed staggered with a multi-window layout + + [Test Plan] + + * Use AMD graphics drivers + + * Connect a second display at a different resolution + + * Open multiple windows + + * While the issue is present, the windows and desktop will appeared + staggered + + * Once fixed, they display normally. + + [Where problems could occur] + + * Regression potential should be relatively low, as the release between + 4.14.1 and 4.14.5 are bug releases. + + * With window managers, some changes could lead to different behavior + and other broken displays. Non-AMD graphics users should also test for + regressions. + + [Other Info] + + * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 + + [Original Report] + Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification beca
[Touch-packages] [Bug 1922615] Re: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1922615 Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Crash during update. Running as a virtual machine under FreeBSD/Bhyve. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 5 17:41:20 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-15 (265 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1922615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922615] [NEW] package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Crash during update. Running as a virtual machine under FreeBSD/Bhyve. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 5 17:41:20 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-15 (265 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1922615 Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Crash during update. Running as a virtual machine under FreeBSD/Bhyve. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.4 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 5 17:41:20 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-15 (265 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1922615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922331] Re: Gdebi quitting on installing deb files
Yes only happens when I try from Firefox and Chrome -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921552] Re: xscreensavers
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment to this bug report it seems that there may be a problem with your hardware. I'd recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! ** Changed in: xorg (Ubuntu) Status: Fix Released => Invalid ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Tags added: hardware-error ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1921552 Title: xscreensavers Status in xorg package in Ubuntu: Invalid Bug description: Something about 'daemon' or 'run demo' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 26 16:31:19 2021 DistUpgraded: 2021-01-08 14:56:49,798 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 6310] [17aa:397f] InstallationDate: Installed on 2020-12-18 (98 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 2181 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=c44a1ac5-9dee-4bf8-a246-6303f68e5c24 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-01-08 (77 days ago) dmi.bios.date: 10/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6CCN93WW(V8.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G585 dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G585 dmi.modalias: dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:svnLENOVO:pn2181:pvrLenovoG585:rvnLENOVO:rnLenovoG585:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG585: dmi.product.family: IDEAPAD dmi.product.name: 2181 dmi.product.sku: LENOVO_MT_2181 dmi.product.version: Lenovo G585 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Feb 9 06:34:08 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1921552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922598] [NEW] The applications installed on Ubuntu
Public bug reported: The apps displayed on Ubuntu are displayed as many times as appearing desktops and text gets on top of one another. I am well aware this is development stage, so raising this issue and making sure it is taken care of, to provide a far better experience for testers and finally users is beyond important. Thank you for reading. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 13:52:26 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:82bd] InstallationDate: Installed on 2021-04-05 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210404) MachineType: HP HP Stream Laptop 14-ax0XX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=f9ea68d0-3734-4d2e-8acd-55bb453cee54 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.release: 15.7 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82BD dmi.board.vendor: HP dmi.board.version: 11.10 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 11.10 dmi.modalias: dmi:bvnInsyde:bvrF.07:bd09/06/2016:br15.7:efr11.10:svnHP:pnHPStreamLaptop14-ax0XX:pvrType1ProductConfigId:rvnHP:rn82BD:rvr11.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=STR X=Null dmi.product.name: HP Stream Laptop 14-ax0XX dmi.product.sku: X7S46UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922598 Title: The applications installed on Ubuntu Status in xorg package in Ubuntu: New Bug description: The apps displayed on Ubuntu are displayed as many times as appearing desktops and text gets on top of one another. I am well aware this is development stage, so raising this issue and making sure it is taken care of, to provide a far better experience for testers and finally users is beyond important. Thank you for reading. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 13:52:26 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:82bd] InstallationDate: Installed on 2021-04-05 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210404) MachineType: HP HP Stream Laptop 14-ax0XX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=f9ea68d0-3734-4d2e-8acd-55bb453cee54 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade
[Touch-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386
** Tags added: sru-20210315 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869368 Title: ubuntu_qrt_apparmor fails on ADT bionic/linux i386 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz Kernel version: bionic/linux 4.15.0-94.95 The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on bionic/linux i386 ADT tests. It has failed some releases in the past and I'm seeing the failure in the current release as well. I have not seen this failure on other architectures. These are the last messages on the test log: 20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... ok 20:12:39 ERROR| [stderr] test_libapparmor_testsuite (__main__.ApparmorTestsuites) 20:14:18 DEBUG| [stdout] unconfined_user can access confined_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access default_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access unconfined_group's file 20:14:18 DEBUG| [stdout] 20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 (__main__.ApparmorTestsuites) 20:15:52 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:15:52 DEBUG| [stdout] 20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite (__main__.ApparmorTestsuites) 20:17:10 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite (__main__.ApparmorTestsuites) 20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 20:17:19 DEBUG| [stdout] 20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:52:35 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 20:52:42 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:52:42 DEBUG| [stdout] 21:01:56 INFO | ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 26 21:01:56 Test subprocess failed rc=9 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1869368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
** Tags added: focal groovy hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922589] [NEW] Color profiles are not loaded in Hirsute (on both X11 and Wayland)
Public bug reported: 1. There is a laptop. 2. Laptops matrices usually have very skewed colors, i.e. #D9DAC6 looks like bluish-gray instead of orangish-brown without loading a correct icc profile. So this issue is of high importance. 3. Usually the issue was solved by extracting an icc from edid, and uskng it. The file is attached. 4. After upgrading to Hirsute the profile has stopped being applied. 5. Tried to apply manually. * `xcalib` "succeeds", but there is no effect * `colord-kde` - in GUI looks like success, but no effect * `Dispwin: Error - File '/edid-97542261df88ff2134c8e0630e62c43b.icc' is not a valid ICC profile or Argyll .cal file` ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: edid ** Attachment added: "The icc file generated from EDID" https://bugs.launchpad.net/bugs/1922589/+attachment/5484346/+files/edid-97542261df88ff2134c8e0630e62c43b.icc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1922589 Title: Color profiles are not loaded in Hirsute (on both X11 and Wayland) Status in colord package in Ubuntu: New Bug description: 1. There is a laptop. 2. Laptops matrices usually have very skewed colors, i.e. #D9DAC6 looks like bluish-gray instead of orangish-brown without loading a correct icc profile. So this issue is of high importance. 3. Usually the issue was solved by extracting an icc from edid, and uskng it. The file is attached. 4. After upgrading to Hirsute the profile has stopped being applied. 5. Tried to apply manually. * `xcalib` "succeeds", but there is no effect * `colord-kde` - in GUI looks like success, but no effect * `Dispwin: Error - File '/edid-97542261df88ff2134c8e0630e62c43b.icc' is not a valid ICC profile or Argyll .cal file` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1922589/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899749] Re: Please add DCCP to rarely used protocols
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915945] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1
Hi, thanks for answering. The output of the command lsattr -l /etc/sudoers is Extents. By the way, I appreciate your help but I got the problem solved by the commands: chattr -i /etc/sudoers and then chmod!! Best regards!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915945 Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1 Status in sudo package in Ubuntu: Incomplete Bug description: I've put the system to upgrade and this error occured!! I tried many ways to correct it but all attempts were unsuccesfull. Best regards, ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: software-properties-common:amd64: Install software-properties-gtk:amd64: Install python3-software-properties:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 17 13:43:57 2021 DuplicateSignature: package:sudo:1.8.31-1ubuntu1.2 Setting up sudo (1.8.31-1ubuntu1.2) ... chown: alterando o dono de '/etc/sudoers': Operação não permitida dpkg: error processing package sudo (--configure): installed sudo package post-installation script subprocess returned error exit status 1 ErrorMessage: installed sudo package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-12 (797 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (139 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921423] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1
Hi, Thanks for your reply!! Your solution was effective. I worked, unlocked the file and then I chmoded it!! Best regards, Alex Leandro Rosa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1921423 Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 Status in sudo package in Ubuntu: Incomplete Bug description: The privileges of my /etc/sudoers file is 220. I don't have any idea on how it was changed, and I tried many different ways to chmod it and I didn't get to do it, even booting from another media and trying to chmod the file didn't work. It's the main reason of the many errors that started happening when updating this machine. I can't stop this machine now, and I don't want to run the risk of trying to use the installation software to try to repair it. If you have any idea on how to chmod the file, I'll be grateful. Best regards, Alex Leandro Rosa ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Mar 25 15:00:47 2021 ErrorMessage: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2018-12-12 (833 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-09-30 (175 days ago) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1921423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922331] Re: Gdebi quitting on installing deb files
Confirm observations from @nrbrtx. @brettwstevens69, if you can confirm that you see this issue only when launching .deb files from within firefox/chrome and not when launched from inside Caja, we could mark this as duplicate of bug #1854588 and track progress there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1922331 Title: Gdebi quitting on installing deb files Status in Ubuntu MATE: New Status in gdebi package in Ubuntu: New Bug description: Gdebi quitting on installing .deb files. Double clicking on a .deb file caused gdebi to open and check the file for installation. Then when you click on install the program terminates. Have tried it on multiple .deb files and it does the same thing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-02 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gdebi 0.9.5.7+nmu4 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1922331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
A good idea, but it made no difference for me. I even went a little further and tried [Service] RestrictAddressFamilies=AF_INET IPAddressAllow=any SystemCallFilter= ProtectSystem=off CapabilityBoundingSet= but still no change, even after a reboot. Logins produce the pair of lines Apr 5 18:42:09 pc2 sshd[1368]: pam_unix(sshd:session): session opened for user mjr19 by (uid=0) Apr 5 18:42:09 pc2 sshd[1368]: pam_systemd(sshd:session): Failed to create session: No such process save that if sshd is not run under systemctl, but rather as "sshd -ddd" from the command line, the "failed to create session" line is not logged, either to stderr or syslog. Still no session is created though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to create session: No such process Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to /run/systemd/userdb/io.systemd.Multiplexer: No such file or directory Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state idle-client Feb 12 09:51:32 myhostname systemd-logind[903]: /run/systemd/userdb/io.systemd.Dynamic
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
** Patch added: "Groovy SRU" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484328/+files/lp1874824_groovy.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
** Patch added: "Focal SRU" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5484329/+files/lp1874824_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: In Progress Status in procps source package in Groovy: In Progress Status in procps source package in Hirsute: Fix Released Status in procps package in Debian: New Bug description: [Impact] - Users who have ulimit set high would see either slow or failed pgrep and pkill commands - Users who have ulimit set to unlimited would see failed pgrep and pkill commands - This bug occurs because the behavior of sysconf(_SC_ARG_MAX) changed with a newer version of the kernel. [Test Case] - set the ulimit to unlimited by running `ulimit -S -s unlimited` - run `pgrep bash` to see that the "cannot allocate" error is printed and the command has failed. [Where Problems Could Occur] - We have set upper and lower limits on the size of the malloc, but if further kernel versions break the call to sysconf in unexpected ways we could still see problems. [Original Description] If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922576] [NEW] No sound card driver for Creative Labs Sound Core3D after latest kernel update
Public bug reported: Ubuntu 20.04, sound card: 25:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01) On kernel 5.4.0.-67-generic, it loads correctly: snd_hda_codec_hdmi 61440 1 snd_hda_codec_ca0132 110592 1 snd_hda_intel 53248 10 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_ca0132 snd_hda_core 90112 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_ca0132 snd_hwdep 20480 1 snd_hda_codec snd_pcm 106496 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_ca0132 snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi36864 1 snd_seq_midi snd_seq69632 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_timer 36864 2 snd_seq,snd_pcm snd90112 30 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm,snd_hda_codec_ca0132,snd_rawmidi soundcore 16384 1 snd On kernel 5.4.0-70-generic, there's no snd modules loaded at all, and trying to modprobe snd_hda_codec_ca0132, returns that there's no such module ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1922576 Title: No sound card driver for Creative Labs Sound Core3D after latest kernel update Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 20.04, sound card: 25:00.0 Audio device: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] (rev 01) On kernel 5.4.0.-67-generic, it loads correctly: snd_hda_codec_hdmi 61440 1 snd_hda_codec_ca0132 110592 1 snd_hda_intel 53248 10 snd_intel_dspcfg 24576 1 snd_hda_intel snd_hda_codec 135168 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_ca0132 snd_hda_core 90112 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_ca0132 snd_hwdep 20480 1 snd_hda_codec snd_pcm 106496 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_ca0132 snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi36864 1 snd_seq_midi snd_seq69632 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_timer 36864 2 snd_seq,snd_pcm snd90112 30 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm,snd_hda_codec_ca0132,snd_rawmidi soundcore 16384 1 snd On kernel 5.4.0-70-generic, there's no snd modules loaded at all, and trying to modprobe snd_hda_codec_ca0132, returns that there's no such module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1922576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 388605] Re: [MIR] rsyslog
** Changed in: rsyslog (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: rsyslog (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: rsyslog (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/388605 Title: [MIR] rsyslog Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Fix Released Status in rsyslog source package in Focal: Fix Released Status in rsyslog source package in Groovy: Fix Released Status in rsyslog source package in Hirsute: Fix Released Bug description: Binary package hint: rsyslog We want to make rsyslog the new default syslogger. See https://wiki.ubuntu.com/MainInclusionReport/rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
no me instala version 20.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386
[Touch-packages] [Bug 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
Hello Vincent, Since the Debian version has these fixes incorporated, this would be fixed in Hirsute already (as it's in sync (with a minor delta)). For Focal, it will need somebody affected to commit to doing the necessary QA after the update is prepared (without that QA, we won't be able to land the update). The process is documented at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. I'll add this task to the server team's backlog. If you'd like to do it sooner, you are welcome to prepare the update yourself following the documented process. Thanks! ** Also affects: openldap (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: openldap (Ubuntu) Status: Confirmed => Fix Released ** Changed in: openldap (Ubuntu Focal) Status: New => Triaged ** Tags added: bitesize server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: Triaged Bug description: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
> Maybe this script can help to debug: oh my, no. please just attach the systemd-networkd config from your failing server. If you are using netplan (looks like you are from your ansible config) please include all files in /etc/netplan/ as well. ** Changed in: systemd (Ubuntu) Status: Fix Released => Incomplete ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Groovy) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
@fabceolin your zip shows you have no systemd-networkd config files at all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" Status in systemd: Fix Released Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915502] Re: "systemd --user" fails to start for non-local users
I suspect this is a dup of bug 1916235 (or it a dup of this); have you
tried the workaround (shown below) of allowing systemd-logind network
access?
$ sudo systemctl edit systemd-logind
(opens an editor, put in the text below and save it, then reboot and retest)
[Service]
RestrictAddressFamilies=AF_INET
IPAddressAllow=any
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1915502
Title:
"systemd --user" fails to start for non-local users
Status in systemd package in Ubuntu:
Incomplete
Bug description:
systemd-logind fails to start the systemd --user process for non-local
users on Ubuntu 20.04. This is a reproducible problem; all our
systems are displaying the same symptoms.
The systems are using Kerberos (Active Directory) for authentication,
and NIS for account meta-data and authorisation (groups)
A base installation is performed using the server 20.04 ISO image. No
additional packages are selected. Post-install, I run:
apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd
I set up the NIS client (supply the default domain name, check ypbind
is running and ypcat passwd is working)
I then set up /etc/krb5.conf for kerberos authentication to a domain
controller, confirm that kinit works and a kerberos ticket is issued.
I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to
the end of each.
/etc/nsswitch.conf is modified to support compat mode, as well as
systemd:
passwd: compat systemd
group: compat systemd
shadow: compat
I can log in remotely via ssh using my NIS account and Kerberos
credentials. MY NIS meta-data looks like:
amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh
(where UID and GID are replaced with values unique to the
organisation)
On login, the following occurs:
hostname:~> systemctl --user
Failed to connect to bus: No such file or directory
I put pam-systemd and systemd-logind into debug mode to get more
information:
Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from
[redact] port 58849 ssh2: RSA SHA256:[redact]
Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened
for user amcvey by (uid=0)
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call
sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CreateSession cookie=2
reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd
initializing
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking
logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user
desktop= seat= vtnr=0 tty= display= remote=yes remote_user=
remote_host=10.105.121.110
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session
limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a
runtime_max_sec=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus
interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41
reply_cookie=0 signature=s error-name=n/a error-message=n/a
Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to
create session: No such process
Feb 12 09:51:32 myhostname systemd-logind[903]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a
interface=n/a member=n/a cookie=14 reply_cookie=41 signature=u error-name=n/a
error-message=n/a
Feb 12 09:51:32 myhostname systemd-logind[903]: Unable to connect to
/run/systemd/userdb/io.systemd.Multiplexer: No such file or directory
Feb 12 09:51:32 myhostname systemd-logind[903]: n/a: varlink: setting state
idle-client
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: Sending message:
{"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"uid":198083,"service":"io.systemd.DynamicUser"}}
Feb 12 09:51:32 myhostname systemd-logind[903]:
/run/systemd/userdb/io.systemd.DynamicUser: varlink: changing state idle-client
→ awaiting-reply
Feb 12
[Touch-packages] [Bug 1916235] Re: systemd generates errors when using NSS and LDAP
possibly same as bug 1915502
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1916235
Title:
systemd generates errors when using NSS and LDAP
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Ubuntu 20.04.2 LTS
systemd 245.4-4ubuntu3.4
The system is configured to use LDAP via nsswitch.conf:
passwd: files systemd ldap
group: files systemd ldap
shadow: files ldap
gshadow:files
Using libnss-ldap 265-5ubuntu1. When logging in with ssh there is a
slight delay, and in the logs I see:
Feb 19 12:49:54 myserver sshd[105417]: Accepted publickey for mylogin from
1.2.3.4 port 60796 ssh2: RSA SHA256:somekey
Feb 19 12:49:54 myserver sshd[105417]: pam_unix(sshd:session): session opened
for user mylogin by (uid=0)
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: reconnecting to LDAP
server...
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: reconnecting to LDAP
server (sleeping 1 seconds)...
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: could not search LDAP
server - Server is unavailable
Feb 19 12:49:55 myserver systemd-logind[105119]: New session 331 of user
mylogin.
With debugging for the systemd-logind process I can see the additional
information:
Feb 19 12:55:22 myserver systemd-logind[106567]: Failed to do shadow
lookup for UID 12345, ignoring: Bad file descriptor
And with strace I see:
stat("/etc/ldap.conf", {st_mode=S_IFREG|0644, st_size=9102, ...}) = 0
geteuid() = 0
socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family
not supported by protocol)
fcntl(-1, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file descriptor)
sendto(33, "<83>Feb 19 12:56:59 systemd-logind: nss_ldap: could not connect
to any LDAP server as (null) - Can't contact LDAP server", 120, MSG_NOSIGNAL,
NULL, 0) = 120
sendto(33, "<86>Feb 19 12:56:59 systemd-logind: nss_ldap: failed to bind to
LDAP server ldaps://myldapserver.mydomain/: Can't contact LDAP server", 131,
MSG_NOSIGNAL, NULL, 0) = 131
sendto(33, "<86>Feb 19 12:56:59 systemd-logind: nss_ldap: reconnecting to
LDAP server...", 76, MSG_NOSIGNAL, NULL, 0) = 76
Looking in /usr/lib/systemd/system/systemd-logind.service we see:
RestrictAddressFamilies=AF_UNIX AF_NETLINK
IPAddressDeny=any
So the problem is that systemd-logind can't open an AF_INET socket.
And additionally, it can't make any network connections.
This only occurs in 20.04. In 20.10 this is fixed by a newer systemd,
and it doesn't appear to be present in older systemd versions (at
least, I don't have an issue on 18.04).
The fix, from systemd 246, which is included in 20.10, is:
https://github.com/systemd/systemd/pull/15377
I have applied this change (which patches cleanly to the systemd
source package in 20.04) and the problem is resolved.
A temporary workaround for others experiencing this issue would be to
run "systemctl edit systemd-logind" and enter the following:
[Service]
RestrictAddressFamilies=AF_INET
IPAddressAllow=any
Then restart the systemd-login service, or reboot. Obviously this
could have other implications for the security of the system - I'm not
sure if processes launched by systemd-logind also have more relaxed
permissions.
It'd be great if the above patch could be applied to the package in
20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1916235/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types
** Also affects: shared-mime-info via https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/136 Importance: Unknown Status: Unknown ** Also affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in shared-mime-info: Unknown Status in mime-support package in Ubuntu: New Status in shared-mime-info package in Ubuntu: New Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
@Bob Your crash log confirms it is the same issue. It crashes the installer at the try/install stage (what you are reporting, and what results in the message you see) AND when the installer is manually launched from a live session. At the moment all anyone can do is wait for the result of the mesa uploaders git bisect, to find the commit/cause in the new mesa that landed in the release pocket @ around the 17th of March. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.ne
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Opinion Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Opinion Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
To verify runc I am launching a docker container and calling "test -x" like was done for systemd. Groovy == ubuntu@docker-groovy:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy ubuntu@docker-groovy:~$ dpkg -l | grep runc ii runc 1.0.0~rc93-0ubuntu1~20.10.1 amd64Open Container Project - runtime ubuntu@docker-groovy:~$ docker run -it ubuntu:focal /bin/bash Unable to find image 'ubuntu:focal' locally focal: Pulling from library/ubuntu a70d879fa598: Pull complete c4394a92d1f8: Pull complete 10e6159c56c0: Pull complete Digest: sha256:3c9c713e0979e9bd6061ed52ac1e9e1f246c9495aa063619d9d695fb8039aa1f Status: Downloaded newer image for ubuntu:focal root@7fa381c4877b:/# which ls /usr/bin/ls root@7fa381c4877b:/# ls -l /usr/bin/ls -rwxr-xr-x 1 root root 142144 Sep 5 2019 /usr/bin/ls root@7fa381c4877b:/# test -x /usr/bin/ls || echo "fail" root@7fa381c4877b:/# Focal = ubuntu@docker-focal:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ubuntu@docker-focal:~$ dpkg -l | grep runc ii runc 1.0.0~rc93-0ubuntu1~20.04.1 amd64 Open Container Project - runtime ubuntu@docker-focal:~$ sudo docker run -it ubuntu:focal /bin/bash Unable to find image 'ubuntu:focal' locally focal: Pulling from library/ubuntu a70d879fa598: Pull complete c4394a92d1f8: Pull complete 10e6159c56c0: Pull complete Digest: sha256:3c9c713e0979e9bd6061ed52ac1e9e1f246c9495aa063619d9d695fb8039aa1f Status: Downloaded newer image for ubuntu:focal root@bf6b6e1534e5:/# which ls /usr/bin/ls root@bf6b6e1534e5:/# test -x /usr/bin/ls || echo "fail" root@bf6b6e1534e5:/# Bionic == ubuntu@docker-bionic:~$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.5 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.5 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ubuntu@docker-bionic:~$ dpkg -l | grep runc ii runc 1.0.0~rc93-0ubuntu1~18.04.1 amd64Open Container Project - runtime ubuntu@docker-bionic:~$ sudo docker run -it ubuntu:focal /bin/bash Unable to find image 'ubuntu:focal' locally focal: Pulling from library/ubuntu a70d879fa598: Pull complete c4394a92d1f8: Pull complete 10e6159c56c0: Pull complete Digest: sha256:3c9c713e0979e9bd6061ed52ac1e9e1f246c9495aa063619d9d695fb8039aa1f Status: Downloaded newer image for ubuntu:focal root@1979a3f523dc:/# which ls /usr/bin/ls root@1979a3f523dc:/# test -x /usr/bin/ls || echo "fail" root@1979a3f523dc:/# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Committed Status in systemd source package in Focal: Fix Committed Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Committed Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Rel
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately what Rik is experiencing on a "live session" in his virtual machine with intel graphics using an unnecessary 'safe graphics' mode is slightly different to my necessary use of 'safe graphics' to unsuccessfully boot from a thumbdrive containing the iso. I'm sorry I am not a bug hunter, I am not aware of the protocols. All I can repeat is that a thumb drive containing either a current daily build or the recent beta does not boot correctly. I would guess in my untutored way that some change to the boot process occurred during March. Up until then I had performed test installs without a hitch. I would be happy to give any assistance/info I can but my programming experience is severely limited. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other compute
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
"malloc(): unaligned tcache chunk detected" does not appear on my PC. I am trying to install from an iso of hippo on a thumb drive. The boot fails before any 'live session' appears. I am not trying to install from a live session, boot fails before that point. I do not think this is the same as the bug reported here. Rik it appears is attemptig to boot from a live session of some sort. My installation breaks down before reaching this point. The iso in the daily build was not failing until some time in March. It has not been right since. There were a number of updates on a regular basis in March. The change is in the boot process rather than in actual installation as the installation has not been begun at the point the bug occurs. I'm no programmer but I can see that installation has not been offered, let alone begun when things go astray. Please review any conclusions so far. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can
[Touch-packages] [Bug 1922553] [NEW] libnss3 package contains invalid library paths
Public bug reported:
libnss3 package installs these files:
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}
Here, ${DEB_HOST_MULTIARCH} is the literal name of the directory created
in the filesystem. Presumably, this is caused by incorrect syntax of the
variable used in the packaging scripts.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-48.54-lowlatency 5.8.18
Uname: Linux 5.8.0-48-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 5 14:19:22 2021
InstallationDate: Installed on 2015-05-01 (2165 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: nss
UpgradeStatus: Upgraded to groovy on 2020-11-22 (134 days ago)
** Affects: nss (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1922553
Title:
libnss3 package contains invalid library paths
Status in nss package in Ubuntu:
New
Bug description:
libnss3 package installs these files:
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3:amd64, libnss3:i386: /usr/lib/${DEB_HOST_MULTIARCH}
Here, ${DEB_HOST_MULTIARCH} is the literal name of the directory
created in the filesystem. Presumably, this is caused by incorrect
syntax of the variable used in the packaging scripts.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-48.54-lowlatency 5.8.18
Uname: Linux 5.8.0-48-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 5 14:19:22 2021
InstallationDate: Installed on 2015-05-01 (2165 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: nss
UpgradeStatus: Upgraded to groovy on 2020-11-22 (134 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1922553/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922543] Re: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog)
Also i tried to do this https://wiki.ubuntu.com/PulseAudio/Log to make a pulseaudio log from startup, but it doesn't work. Where are the actual right instructions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1922543 Title: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog) Status in pulseaudio package in Ubuntu: New Bug description: Hello. Since i installed KUbuntu 20.10 i have an issue with the audio system. Every time i boot the system, the system audio profiles and devices are not recognized correctly, and normally there isn't an output audio at all and no sound. However, if i do a "killall pulseaudio", suddenly everything appears in the KDE audio profiles and the sound becomes available. My laptop (Asus Zenbook UM431DA, ALC294 Analog) have 4 speakers: 2 in front (in both sides of the keyboard) and 2 in the back. It have also a HDMI Audio output which is not recognized. But like i said, if i do a "killall pulseaudio" everything appears, including the HDMI audio, and all the expected audio profiles (Stereo, Stereo Duplex, 2.1, 4.0... all with variants with and without input). If i don't do that, all i have is "Off" and "Input Analog". With the KUbuntu 20.10 LiveUSB (Kernel 5.8.0-25) i didn't have the issue (every boot brings all profiles) but since i installed in the laptop (early installed Kernel was 5.8.0-31) i have the issue. Actually i have kernel 5.8.0-44, the last official one from Ubuntu, and everything is exactly the same. I tried too using kernels via Ubuntu Mainline Kernel Installer, and i had some differences with newer kernels. I was updating once in a while from there, and at some point, i can be sure, the kernel could bring at boot a different list of available profiles (sometimes only input, other only Stereo, or Stereo + 2.1, or Stereo + 2.1 + 4.0... each one with the input option) and sometimes the HDMI audio appears and sometimes don't. But in all cases, if i do "killall pulseaudio", all profiles come back. However, Kernel 5.11.4 from mainline was the last one with that behaviour. 5.11.5 do the same as 5.8.0-44, every time at boot the only profiles are "Off" and "Input Analog". Actually i have 5.12.0-051200rc5 with exact the same results. Using "pasuspender -- aplay -Dplughw:1 example.wav" to bypass PulseAudio gives me sound in every case. Also i have an issue (maybe related) with ALSA about i can't adjust the volume from back speakers (between 1%~100% are always 100%, between 100%~150% works) and front speakers have a low volume. But it's directly related to ALSA because with pasuspender the behaviour is the same. I reported that here https://bugzilla.kernel.org/show_bug.cgi?id=212547. I can provide alsa-info and dmesg from 5.8.0-44 (last official one from Ubuntu), but also from 5.8.0-25 (from KUbuntu LiveUSB), and a complete collection of alsa-info, dmesg and image of KDE audio profiles from 5.11.0 (A kernel with the behaviour of different options with every boot). Further, i can add alsa-info before and after "killall pulseaudio", and data from 5.11.4 and 5.11.5, or 5.12.0-051200rc5, which is the last one available in mainline. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922543] Re: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog)
** Attachment added: "alsa-info & dmesg from 5.12.0-051200rc5 (before and after "killall pulseaudio")" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922543/+attachment/5484205/+files/alsa-info_dmesg%205_12_0-051200rc5.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1922543 Title: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog) Status in pulseaudio package in Ubuntu: New Bug description: Hello. Since i installed KUbuntu 20.10 i have an issue with the audio system. Every time i boot the system, the system audio profiles and devices are not recognized correctly, and normally there isn't an output audio at all and no sound. However, if i do a "killall pulseaudio", suddenly everything appears in the KDE audio profiles and the sound becomes available. My laptop (Asus Zenbook UM431DA, ALC294 Analog) have 4 speakers: 2 in front (in both sides of the keyboard) and 2 in the back. It have also a HDMI Audio output which is not recognized. But like i said, if i do a "killall pulseaudio" everything appears, including the HDMI audio, and all the expected audio profiles (Stereo, Stereo Duplex, 2.1, 4.0... all with variants with and without input). If i don't do that, all i have is "Off" and "Input Analog". With the KUbuntu 20.10 LiveUSB (Kernel 5.8.0-25) i didn't have the issue (every boot brings all profiles) but since i installed in the laptop (early installed Kernel was 5.8.0-31) i have the issue. Actually i have kernel 5.8.0-44, the last official one from Ubuntu, and everything is exactly the same. I tried too using kernels via Ubuntu Mainline Kernel Installer, and i had some differences with newer kernels. I was updating once in a while from there, and at some point, i can be sure, the kernel could bring at boot a different list of available profiles (sometimes only input, other only Stereo, or Stereo + 2.1, or Stereo + 2.1 + 4.0... each one with the input option) and sometimes the HDMI audio appears and sometimes don't. But in all cases, if i do "killall pulseaudio", all profiles come back. However, Kernel 5.11.4 from mainline was the last one with that behaviour. 5.11.5 do the same as 5.8.0-44, every time at boot the only profiles are "Off" and "Input Analog". Actually i have 5.12.0-051200rc5 with exact the same results. Using "pasuspender -- aplay -Dplughw:1 example.wav" to bypass PulseAudio gives me sound in every case. Also i have an issue (maybe related) with ALSA about i can't adjust the volume from back speakers (between 1%~100% are always 100%, between 100%~150% works) and front speakers have a low volume. But it's directly related to ALSA because with pasuspender the behaviour is the same. I reported that here https://bugzilla.kernel.org/show_bug.cgi?id=212547. I can provide alsa-info and dmesg from 5.8.0-44 (last official one from Ubuntu), but also from 5.8.0-25 (from KUbuntu LiveUSB), and a complete collection of alsa-info, dmesg and image of KDE audio profiles from 5.11.0 (A kernel with the behaviour of different options with every boot). Further, i can add alsa-info before and after "killall pulseaudio", and data from 5.11.4 and 5.11.5, or 5.12.0-051200rc5, which is the last one available in mainline. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922543] [NEW] No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog)
Public bug reported: Hello. Since i installed KUbuntu 20.10 i have an issue with the audio system. Every time i boot the system, the system audio profiles and devices are not recognized correctly, and normally there isn't an output audio at all and no sound. However, if i do a "killall pulseaudio", suddenly everything appears in the KDE audio profiles and the sound becomes available. My laptop (Asus Zenbook UM431DA, ALC294 Analog) have 4 speakers: 2 in front (in both sides of the keyboard) and 2 in the back. It have also a HDMI Audio output which is not recognized. But like i said, if i do a "killall pulseaudio" everything appears, including the HDMI audio, and all the expected audio profiles (Stereo, Stereo Duplex, 2.1, 4.0... all with variants with and without input). If i don't do that, all i have is "Off" and "Input Analog". With the KUbuntu 20.10 LiveUSB (Kernel 5.8.0-25) i didn't have the issue (every boot brings all profiles) but since i installed in the laptop (early installed Kernel was 5.8.0-31) i have the issue. Actually i have kernel 5.8.0-44, the last official one from Ubuntu, and everything is exactly the same. I tried too using kernels via Ubuntu Mainline Kernel Installer, and i had some differences with newer kernels. I was updating once in a while from there, and at some point, i can be sure, the kernel could bring at boot a different list of available profiles (sometimes only input, other only Stereo, or Stereo + 2.1, or Stereo + 2.1 + 4.0... each one with the input option) and sometimes the HDMI audio appears and sometimes don't. But in all cases, if i do "killall pulseaudio", all profiles come back. However, Kernel 5.11.4 from mainline was the last one with that behaviour. 5.11.5 do the same as 5.8.0-44, every time at boot the only profiles are "Off" and "Input Analog". Actually i have 5.12.0-051200rc5 with exact the same results. Using "pasuspender -- aplay -Dplughw:1 example.wav" to bypass PulseAudio gives me sound in every case. Also i have an issue (maybe related) with ALSA about i can't adjust the volume from back speakers (between 1%~100% are always 100%, between 100%~150% works) and front speakers have a low volume. But it's directly related to ALSA because with pasuspender the behaviour is the same. I reported that here https://bugzilla.kernel.org/show_bug.cgi?id=212547. I can provide alsa-info and dmesg from 5.8.0-44 (last official one from Ubuntu), but also from 5.8.0-25 (from KUbuntu LiveUSB), and a complete collection of alsa-info, dmesg and image of KDE audio profiles from 5.11.0 (A kernel with the behaviour of different options with every boot). Further, i can add alsa-info before and after "killall pulseaudio", and data from 5.11.4 and 5.11.5, or 5.12.0-051200rc5, which is the last one available in mainline. Thanks ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info & dmesg from 5.8.0-44 (before and after "killall pulseaudio")" https://bugs.launchpad.net/bugs/1922543/+attachment/5484204/+files/alsa-info_dmesg%205.8.0-44.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1922543 Title: No sound, no audio profiles, until i do 'killall pulseaudio' (Asus Zenbook 14 UM431D, ALC294 Analog) Status in pulseaudio package in Ubuntu: New Bug description: Hello. Since i installed KUbuntu 20.10 i have an issue with the audio system. Every time i boot the system, the system audio profiles and devices are not recognized correctly, and normally there isn't an output audio at all and no sound. However, if i do a "killall pulseaudio", suddenly everything appears in the KDE audio profiles and the sound becomes available. My laptop (Asus Zenbook UM431DA, ALC294 Analog) have 4 speakers: 2 in front (in both sides of the keyboard) and 2 in the back. It have also a HDMI Audio output which is not recognized. But like i said, if i do a "killall pulseaudio" everything appears, including the HDMI audio, and all the expected audio profiles (Stereo, Stereo Duplex, 2.1, 4.0... all with variants with and without input). If i don't do that, all i have is "Off" and "Input Analog". With the KUbuntu 20.10 LiveUSB (Kernel 5.8.0-25) i didn't have the issue (every boot brings all profiles) but since i installed in the laptop (early installed Kernel was 5.8.0-31) i have the issue. Actually i have kernel 5.8.0-44, the last official one from Ubuntu, and everything is exactly the same. I tried too using kernels via Ubuntu Mainline Kernel Installer, and i had some differences with newer kernels. I was updating once in a while from there, and at some point, i can be sure, the kernel could bring at boot a different list of available profiles (sometimes only input, other only Stereo, or Stereo + 2.1, or Stereo + 2.1 + 4.0... each one with the input o
[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Description changed: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. + The crash is most commonly "malloc(): unaligned tcache chunk detected", + but inevitably from this sort of memory issue can be something like + "realloc(): invalid next size" + An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) Source
[Touch-packages] [Bug 1922533] Re: Problem with identifying the graphics card even after driver installation
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. xserver-xorg-video-intel is an old 'intel' driver that is no longer maintained being depreciated. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922533 Title: Problem with identifying the graphics card even after driver installation Status in xorg package in Ubuntu: New Bug description: I have installed my intel graphic card driver with: sudo apt-get install xserver-xorg-video-intel but the problem still exists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 11:23:15 2021 DistUpgraded: 2020-08-16 14:53:11,321 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ad] InstallationDate: Installed on 2020-08-01 (246 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0458:6001 KYE Systems Corp. (Mouse Systems) GF3000F Ethernet Adapter Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=4c5d2c1d-42c5-4c4e-bf34-5d502dde94e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-16 (231 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0J3C2F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0J3C2F:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103+git2011061830.fc479e~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2011161930.b479a1~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.0~git2011161930.b479a1~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922536] [NEW] bluetooth not working in gnome settings after reboot and requires systemctl restart bluetooth
Public bug reported: Selected logs: https://paste.ubuntu.com/p/gMbk2ntQyz/ https://paste.ubuntu.com/p/F8n72kCbJJ/ lshw: https://paste.ubuntu.com/p/3Z9jwBdyVt/ If I try and use the bluetooth toggle in gnome settings upon boot it won't do anything. If I have the bluetooth settings window open in gnome settings and manually restart the bluetooth service with: "sudo systemctl restart bluetooth" then it starts searching for devices and I was able to pair Samsung Galaxy Earbuds after multiple service restarts. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 00:35:34 2021 InstallationDate: Installed on 2021-04-05 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81Q9 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=dd9e8fc7-3c6a-462d-8cea-b37801ba586d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:br1.54:efr1.43:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: D8:3B:BF:4D:22:D0 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:302871 acl:36 sco:0 events:10305 errors:0 TX bytes:822111 acl:36 sco:0 commands:5384 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Summary changed: - bluetooth not working in gnome settings and wont pair if started manually with systemctl + bluetooth not working in gnome settings after reboot and requires systemctl restart bluetooth -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922536 Title: bluetooth not working in gnome settings after reboot and requires systemctl restart bluetooth Status in bluez package in Ubuntu: New Bug description: Selected logs: https://paste.ubuntu.com/p/gMbk2ntQyz/ https://paste.ubuntu.com/p/F8n72kCbJJ/ lshw: https://paste.ubuntu.com/p/3Z9jwBdyVt/ If I try and use the bluetooth toggle in gnome settings upon boot it won't do anything. If I have the bluetooth settings window open in gnome settings and manually restart the bluetooth service with: "sudo systemctl restart bluetooth" then it starts searching for devices and I was able to pair Samsung Galaxy Earbuds after multiple service restarts. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 00:35:34 2021 InstallationDate: Installed on 2021-04-05 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81Q9 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=dd9e8fc7-3c6a-462d-8cea-b37801ba586d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:br1.54:efr1.43:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.f
[Touch-packages] [Bug 1922533] [NEW] Problem with identifying the graphics card even after driver installation
Public bug reported: I have installed my intel graphic card driver with: sudo apt-get install xserver-xorg-video-intel but the problem still exists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 11:23:15 2021 DistUpgraded: 2020-08-16 14:53:11,321 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ad] InstallationDate: Installed on 2020-08-01 (246 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0458:6001 KYE Systems Corp. (Mouse Systems) GF3000F Ethernet Adapter Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=4c5d2c1d-42c5-4c4e-bf34-5d502dde94e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-08-16 (231 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0J3C2F dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0J3C2F:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103+git2011061830.fc479e~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2011161930.b479a1~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx 21.0~git2011161930.b479a1~oibaf~f version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922533 Title: Problem with identifying the graphics card even after driver installation Status in xorg package in Ubuntu: New Bug description: I have installed my intel graphic card driver with: sudo apt-get install xserver-xorg-video-intel but the problem still exists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 11:23:15 2021 DistUpgraded: 2020-08-16 14:53:11,321 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ad] InstallationDate: Installed on 2020-08-01 (246 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 0458:6001 KYE Systems Corp. (Mouse Systems) GF3000F Ethernet Adapter Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LAN
[Touch-packages] [Bug 1876068] Re: DeprecationWarning: an integer is required
** Tags added: groovy hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1876068 Title: DeprecationWarning: an integer is required Status in apport package in Ubuntu: Confirmed Bug description: Hi, when I use ubuntu-bug to report a bug, I see the following python deprecation warning: $ ubuntu-bug apport-kde /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 Uname: Linux 5.6.7-050607-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 30 11:16:12 2020 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
