[Touch-packages] [Bug 1915784] Re: Permissions of executables pointing to "buildd"
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 ** Changed in: snap (Ubuntu) Status: New => Fix Released ** Changed in: wireshark (Ubuntu) Status: New => Fix Released -- 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/1915784 Title: Permissions of executables pointing to "buildd" Status in apport package in Ubuntu: New Status in ccache package in Ubuntu: New Status in fuse3 package in Ubuntu: New Status in lzma package in Ubuntu: New Status in netstat-nat package in Ubuntu: New Status in openssh package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in psensor package in Ubuntu: New Status in screen package in Ubuntu: New Status in snap package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Fix Released Status in wireshark package in Ubuntu: Fix Released Status in xz-utils package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915784/+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 1915784] Re: Permissions of executables pointing to "buildd"
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 Hint for others: You can downgrade the package using Synaptic or any other good package manager :) -- 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/1915784 Title: Permissions of executables pointing to "buildd" Status in apport package in Ubuntu: New Status in ccache package in Ubuntu: New Status in fuse3 package in Ubuntu: New Status in lzma package in Ubuntu: New Status in netstat-nat package in Ubuntu: New Status in openssh package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in psensor package in Ubuntu: New Status in screen package in Ubuntu: New Status in snap package in Ubuntu: New Status in sudo package in Ubuntu: Fix Released Status in wireshark package in Ubuntu: New Status in xz-utils package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915784/+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 1915784] Re: Permissions of executables pointing to "buildd"
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 Fixed as the faulty package has been removed from the proposed repo. ** Changed in: sudo (Ubuntu) Status: New => Fix Released -- 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/1915784 Title: Permissions of executables pointing to "buildd" Status in apport package in Ubuntu: New Status in ccache package in Ubuntu: New Status in fuse3 package in Ubuntu: New Status in lzma package in Ubuntu: New Status in netstat-nat package in Ubuntu: New Status in openssh package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in psensor package in Ubuntu: New Status in screen package in Ubuntu: New Status in snap package in Ubuntu: New Status in sudo package in Ubuntu: Fix Released Status in wireshark package in Ubuntu: New Status in xz-utils package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915784/+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 1915250] Re: buildd file owner/group for shared libraries
@xnox: To fill your list: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915784 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1915250 Title: buildd file owner/group for shared libraries Status in binutils package in Ubuntu: Confirmed Status in debhelper package in Ubuntu: Confirmed Status in fakeroot package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Confirmed Status in debhelper package in Debian: Unknown Bug description: the current state of -proposed creates deb packages with buildd file owner/group for shared libraries. reported at least for kwayland-integration. $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so -rw-r--r-- doko/doko 18984 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so -rw-r--r-- doko/doko 85392 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so -rw-r--r-- doko/doko 35536 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so - in a release pocket, rebuild binutils from proposed. correctly restores the file ownership - in a release pocket, update glibc from proposed. then rebuild binutils from proposed. shows the wrong ownership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915784] Re: Permissions of executables pointing to "buildd"
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 Thank you too for looking into this! Good luck! :) -- 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/1915784 Title: Permissions of executables pointing to "buildd" Status in apport package in Ubuntu: New Status in ccache package in Ubuntu: New Status in fuse3 package in Ubuntu: New Status in lzma package in Ubuntu: New Status in netstat-nat package in Ubuntu: New Status in openssh package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in psensor package in Ubuntu: New Status in screen package in Ubuntu: New Status in snap package in Ubuntu: New Status in sudo package in Ubuntu: New Status in wireshark package in Ubuntu: New Status in xz-utils package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915784/+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 1915784] Re: Permissions of executables pointing to "buildd"
** Also affects: xz-utils (Ubuntu) Importance: Undecided Status: New ** Also affects: wireshark (Ubuntu) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Also affects: snap (Ubuntu) Importance: Undecided Status: New ** Also affects: screen (Ubuntu) Importance: Undecided Status: New ** Also affects: psensor (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Also affects: netstat-nat (Ubuntu) Importance: Undecided Status: New ** Also affects: lzma (Ubuntu) Importance: Undecided Status: New ** Also affects: fuse3 (Ubuntu) Importance: Undecided Status: New ** Also affects: ccache (Ubuntu) Importance: Undecided Status: New ** Also affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1915784 Title: Permissions of executables pointing to "buildd" Status in apport package in Ubuntu: New Status in ccache package in Ubuntu: New Status in fuse3 package in Ubuntu: New Status in lzma package in Ubuntu: New Status in netstat-nat package in Ubuntu: New Status in openssh package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in psensor package in Ubuntu: New Status in screen package in Ubuntu: New Status in snap package in Ubuntu: New Status in sudo package in Ubuntu: New Status in wireshark package in Ubuntu: New Status in xz-utils package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1915784/+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 1915784] [NEW] Permissions of executables pointing to "buildd"
Public bug reported: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute package-from-proposed -- 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/1915784 Title: Permissions of executables pointing to "buildd" Status in sudo package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915784/+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 1653345] Re: Cura crashes on start probably caused by Qt5+DBus
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1653345 Title: Cura crashes on start probably caused by Qt5+DBus Status in Qt: New Status in unity package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: I installed Cura from the PPA (https://launchpad.net/~thopiekar/+archive/ubuntu/cura) When starting it it crashes. According to the issue on GitHub (https://github.com/Ultimaker/Cura/issues/1094) this is caused by a certain Qt version. To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1653345/+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 1325503] Re: gdb reports 'corrupt stack' on armhf without symbols
I also see a lot of these errors here on Wily at KDE Plasma: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 [Current thread is 1 (Thread 0xb2ad9000 (LWP 4363))] Thread 14 (Thread 0xb076a3e0 (LWP 4365)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 #1 0xb55706b0 in __pthread_cond_wait (cond=0xc0560, mutex=0xc0548) at pthread_cond_wait.c:186 #2 0xb2296592 in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 13 (Thread 0xaff6a3e0 (LWP 4366)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 #1 0xb55706b0 in __pthread_cond_wait (cond=0xc0668, mutex=0xc0650) at pthread_cond_wait.c:186 #2 0xb2296592 in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 12 (Thread 0xaf76a3e0 (LWP 4367)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 #1 0xb55706b0 in __pthread_cond_wait (cond=0xc0770, mutex=0xc0758) at pthread_cond_wait.c:186 #2 0xb2296592 in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 11 (Thread 0xaef6a3e0 (LWP 4368)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 #1 0xb55706b0 in __pthread_cond_wait (cond=0xc0878, mutex=0xc0860) at pthread_cond_wait.c:186 #2 0xb2296592 in ?? () from /usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 10 (Thread 0xae7143e0 (LWP 4369)): #0 0xb56904e0 in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0xb6bb4168 in ?? () from /usr/lib/arm-linux-gnueabihf/libxcb.so.1 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 9 (Thread 0xad1c43e0 (LWP 4377)): #0 0xb5a03d80 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #1 0xb5a04c52 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #2 0xb4fb0c54 in g_main_context_prepare () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #3 0xb4fb12ee in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 8 (Thread 0xaad3d3e0 (LWP 4378)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 #1 0xb56a011a in __GI___clock_gettime (clock_id=0, tp=0xaad3cbec) at ../sysdeps/unix/clock_gettime.c:99 #2 0xb59095b2 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 7 (Thread 0xa8fe23e0 (LWP 4386)): #0 0xb4fb13c2 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 6 (Thread 0xa7dff3e0 (LWP 4387)): #0 0xb56904e2 in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0xb4fb137a in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 5 (Thread 0xa6a3e3e0 (LWP 4388)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 #1 0xb55706b0 in __pthread_cond_wait (cond=0xb6f23dd0, mutex=0xb6f23db8) at pthread_cond_wait.c:186 #2 0xb6ebfe76 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Script.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 4 (Thread 0xa4eff3e0 (LWP 4389)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 #1 0xb56a011a in __GI___clock_gettime (clock_id=0, tp=0xa4efebb4) at ../sysdeps/unix/clock_gettime.c:99 #2 0xb59095b2 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 3 (Thread 0xa40633e0 (LWP 4391)): #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 #1 0xb55706b0 in __pthread_cond_wait (cond=0x32e118, mutex=0x32e100) at pthread_cond_wait.c:186 #2 0xb58a52f8 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #3 0xb69b710a in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (Thread 0x9c9723e0 (LWP 4393)): #0 0xb56744e0 in nanosleep () at ../sysdeps/unix/syscall-template.S:81 #1 0xb56742bc in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:138 #2 0xb6f77864 in ?? () from /usr/lib/arm-linux-gnueabihf/libKF5Crash.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0xb2ad9000 (LWP 4363)): #0 __libc_do_syscall ()
[Touch-packages] [Bug 1528379] [NEW] libGLESv2 can not be found
Public bug reported: I don't know whether it is really releated to "qtbase-opensource-src", but I noticed here on my Odroid U3+ problems in Qt5 applications finding libGLES2. Additionally KDE Plasma 5 isn't running at all. I found that problem using "strace " were I saw that /lib/*/mesa-egl/ wasn't checked, just /lib/*/. Installing the debug package of libgles2 of course adds the missing file by linking /lib/*/libGLESv2.so to /lib/*/mesa-egl/libGLESv2.so. Can someone at least confirm this? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libqt5opengl5 5.4.2+dfsg-2ubuntu9 Uname: Linux 4.4.0-rc4-stable armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf CurrentDesktop: KDE Date: Tue Dec 22 00:07:03 2015 SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1528379 Title: libGLESv2 can not be found Status in qtbase-opensource-src package in Ubuntu: New Bug description: I don't know whether it is really releated to "qtbase-opensource-src", but I noticed here on my Odroid U3+ problems in Qt5 applications finding libGLES2. Additionally KDE Plasma 5 isn't running at all. I found that problem using "strace " were I saw that /lib/*/mesa-egl/ wasn't checked, just /lib/*/. Installing the debug package of libgles2 of course adds the missing file by linking /lib/*/libGLESv2.so to /lib/*/mesa-egl/libGLESv2.so. Can someone at least confirm this? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libqt5opengl5 5.4.2+dfsg-2ubuntu9 Uname: Linux 4.4.0-rc4-stable armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf CurrentDesktop: KDE Date: Tue Dec 22 00:07:03 2015 SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1528379/+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 1513802] [NEW] [Wily] [armhf] Could not import PyQt5.QtCore
Public bug reported: When trying to start apport from the iconbar or here via terminal, I get this: $ apport-collect ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore But PyQt5.QtCore is definitly there, because running the python3 interpreter and doing the import PyQt5.QtCore manually works well! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Uname: Linux 3.8.13.30-hardkernel armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf CurrentDesktop: KDE Date: Fri Nov 6 11:55:13 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf package-from-proposed wily -- 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/1513802 Title: [Wily] [armhf] Could not import PyQt5.QtCore Status in apport package in Ubuntu: New Bug description: When trying to start apport from the iconbar or here via terminal, I get this: $ apport-collect ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore But PyQt5.QtCore is definitly there, because running the python3 interpreter and doing the import PyQt5.QtCore manually works well! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Uname: Linux 3.8.13.30-hardkernel armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf CurrentDesktop: KDE Date: Fri Nov 6 11:55:13 2015 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/1513802/+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 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia
Still here on Wily
--
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/941826
Title:
dlopen(libGL.so) resolves to mesa rather than nvidia
Status in NVIDIA Drivers Ubuntu:
New
Status in mesa package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed
Status in pyqt5 package in Ubuntu:
Invalid
Status in python-qt4 package in Ubuntu:
Invalid
Bug description:
I'm having trouble with a combination of NVIDIA + Python + Qt +
Opengl.
I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and
errors like this these:
QGLShader: could not create shader
Vertex shader for simpleShaderProg (MainVertexShader
&PositionOnlyVertexShader) failed to compile
This is an example application triggering the problem:
http://pastebin.com/R0aa8ejs
The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this
error when trying the original demo application from python-qt4-doc. Also,
calling
QtGui.QApplication.setGraphicsSystem("opengl")
produces the same errors.
I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
provided nvidia drivers (where 12.04 includes the most recent driver
for now). After installing the driver using the original NVidia
installer, the applications work as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+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 1481733] Re: Kernel panic when booting with initramfs-tools version 0.120ubuntu1 generated initramfs
Also happens here. Every newly installed linux versions fail here. Using amd-microcode here, so IMO it happens during upgrade of initramfs-tools. Is there a workaround? -- 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/1481733 Title: Kernel panic when booting with initramfs-tools version 0.120ubuntu1 generated initramfs Status in initramfs-tools package in Ubuntu: In Progress Bug description: After updating initramfs-tools to version 0.120ubuntu1 the kernel stops with a kernel panic during boot. … Begin Running /scripts/local-bottom... Begin Running /scripts/init-bottom... done. /init: exec: line 372: switch_root: not found Kernel panic - not syncing: Attempted to kill init! exitcode=0x0200 … For the rest of the backtrace, see the attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1481733/+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
