[Bug 310549] Re: Incorrect works brightness keys in GNOME after a kernel upgrade to 2.6.27-11
I confirm the same problem, after upgrading the kernel to 2.6.27-11. System: Ubuntu 8.10 Laptop: Asus x80l -- Incorrect works brightness keys in GNOME after a kernel upgrade to 2.6.27-11 https://bugs.launchpad.net/bugs/310549 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400786] [NEW] Se bloquea el sistema gr áfico
Public bug reported: Se bloquea el sistema gráfico, normalmente despues de pulsar Alt+Tab o otro cambio entre pantallas. Se puede reiniciar solo con ctrl+alt+prtScrn+REISUB. La tarjeta gráfica Intel(R) 965GM (por glxinfo). Compiz-fusion está activado. gnome-do. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/pidgin NonfreeKernelModules: wl Package: pidgin 1:2.5.8-1ubuntu2~pidgin1.9.04 ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.28-14-generic x86_64 UnreportableReason: Это не оригинальный пакет Ubuntu ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Se bloquea el sistema gráfico https://bugs.launchpad.net/bugs/400786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400786] Re: Se bloquea el sistema gráfic o
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/29198178/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/29198179/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/29198180/ProcStatus.txt -- Se bloquea el sistema gráfico https://bugs.launchpad.net/bugs/400786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77589] Re: debootstrap can't chroot
Same issue here with hardy -- debootstrap can't chroot https://bugs.launchpad.net/bugs/77589 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179192] Re: kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb
The problem is still there after updating to linux- image-2.6.22-14-386_2.6.22-14.52_i386.deb. P.S. The problem reported by Ace Suares is not the same as mine and should had been placed as a separate bug. -- kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb https://bugs.launchpad.net/bugs/179192 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179192] Re: kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb
cat /proc/cmdline says root=UUID=09e11862-4afc-47e0-a715-585b8c29236e ro I've also tried root=/dev/sda2, but I've got an error ALERT! /dev/sda2 does not exist. Dropping to a shell. I neither have any sda nor hda devices in my /dev/ directory. -- kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb https://bugs.launchpad.net/bugs/179192 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152820] Re: Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable
Not sure if I'm having the same issue, but looks similar I have a "sis5513" IDE controller and "Toshiba mk8025gas" hard drive. The update to gusty went ok (had to remove evms). However yesterday (28.12.07) I've updated my system. The linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb has been installed among others. Now my system is unbootable. The kernel doesn't detect my hard drive. As a result I'm getting "ALERT! /dev/disk... not found blah-blah" and initramfs command prompt. -- Upgrade to linux-image-2.6.22-14 kernel renders my PC unbootable https://bugs.launchpad.net/bugs/152820 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179192] kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb
Public bug reported: Binary package hint: linux-image-2.6.22-14-386 Not sure if I'm having the same issue, but looks similar to https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/152820 I have a "sis5513" IDE controller and "Toshiba mk8025gas" hard drive. The update from edgy to gusty went ok (had to remove evms). Since then I've been using a gusty 2.6.22-14 kernel for a while. However yesterday (28.12.07) I've updated my system. The linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb has been installed among others. Now my system is unbootable. The kernel doesn't detect my hard drive. As a result I'm getting "ALERT! /dev/disk... not found" and initramfs command prompt. ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- kernel does not recognize my hard drive after upgrade to linux-image-2.6.22-14-386_2.6.22-14.47_i386.deb https://bugs.launchpad.net/bugs/179192 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495172] [NEW] тра ля ля
Public bug reported: Binary package hint: pidgin екаьотпроьпрьолпрлпррпопропоопрорпопро ProblemType: Bug Architecture: i386 Date: Fri Dec 11 22:13:59 2009 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.4.1-1ubuntu2 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.24-19-generic i686 ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- тра ля ля https://bugs.launchpad.net/bugs/495172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495172] Re: тра ля ля
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/3366/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/3367/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/3369/ProcStatus.txt -- тра ля ля https://bugs.launchpad.net/bugs/495172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278745] Re: telepathy-butterfly crashed with gaierror in query()
When I'v launched empathy, it couldn't conect to MSN and when I'v done click on the message to reconnect, I'v seen the crush windows, but empathy steel working. But I can't connect me to MSN. -- telepathy-butterfly crashed with gaierror in query() https://bugs.launchpad.net/bugs/278745 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936282] Re: package grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
** Description changed: unclear - error resists after a bunch of updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 AptOrdering: - grub-efi-amd64-signed: Configure - NULL: ConfigurePending + grub-efi-amd64-signed: Configure + NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 14 12:23:59 2021 DpkgHistoryLog: - Start-Date: 2021-07-14 12:23:58 - Commandline: apt-get install qpdf - Requested-By: volker (1000) + Start-Date: 2021-07-14 12:23:58 + Commandline: apt-get install qpdf + Requested-By: volker (1000) DpkgTerminalLog: - grub-efi-amd64-signed (1.167~16.04.6+2.04-1ubuntu44.1.2) wird eingerichtet ... - Installing for x86_64-efi platform. - grub-install: Fehler: Kann EFI Verzeichnis nicht finden. - dpkg: Fehler beim Bearbeiten des Paketes grub-efi-amd64-signed (--configure): - Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück + grub-efi-amd64-signed (1.167~16.04.6+2.04-1ubuntu44.1.2) wird eingerichtet ... + Installing for x86_64-efi platform. + grub-install: Fehler: Kann EFI Verzeichnis nicht finden. + dpkg: Fehler beim Bearbeiten des Paketes grub-efi-amd64-signed (--configure): + Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück RelatedPackageVersions: - dpkg 1.18.4ubuntu1.7 - apt 1.2.35 + dpkg 1.18.4ubuntu1.7 + apt 1.2.35 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to xenial on 2016-09-17 (1761 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936282 Title: package grub-efi-amd64-signed 1.167~16.04.6+2.04-1ubuntu44.1.2 failed to install/upgrade: Unterprozess installiertes post-installation- Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1936282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720493] Re: Segmentation fault on loading map even in safe mode
The same issue on Ubuntu bionic ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720493 Title: Segmentation fault on loading map even in safe mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ioquake3/+bug/1720493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720493] Re: Segmentation fault on loading map even in safe mode
Probably it's not libsdl2 2.0.6 caused bug due Ubuntu bionic has libsdl2 2.0.8 onboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720493 Title: Segmentation fault on loading map even in safe mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ioquake3/+bug/1720493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
https://bugs.freedesktop.org/show_bug.cgi?id=108747 Is that ok or I should add something there? ** Bug watch added: freedesktop.org Bugzilla #108747 https://bugs.freedesktop.org/show_bug.cgi?id=108747 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
The main bug report is here https://bugs.freedesktop.org/show_bug.cgi?id=93782 I've tried video=SVIDEO-1:d as boot parameter on 18.04 live CD and it helps. It turns off TV out and the booting is fast as it should. Thank you all for your time and attention. ** Bug watch added: freedesktop.org Bugzilla #93782 https://bugs.freedesktop.org/show_bug.cgi?id=93782 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785326] Re: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe, bionic).
Yes, I see it on 4.20.0-042000rc2-lowlatency (i386) kernel. ** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326/+attachment/5211951/+files/dmesg-4.20.0-042000rc2-lowlatency-i386.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785326 Title: The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823480] Re: Segfault on saving preferences
** Attachment added: "strace -o iptux.txt iptux" https://bugs.launchpad.net/ubuntu/+source/iptux/+bug/1823480/+attachment/5253491/+files/iptux.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823480 Title: Segfault on saving preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptux/+bug/1823480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823480] [NEW] Segfault on saving preferences
Public bug reported: Steps to reproduce: 1) Open preferences 2) Input IP range in Network tab, press Add 3) Click OK or Apply dmesg says [ 2829.339000] iptux[12290]: segfault at 0 ip 7fe557e9c646 sp 7ffe625860a8 error 4 in libc-2.27.so[7fe557deb000+1e7000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iptux 0.7.4-1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Apr 6 21:12:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (299 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: iptux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iptux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823480 Title: Segfault on saving preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptux/+bug/1823480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862402] Re: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862402 Title: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trackballs/+bug/1862402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862402] [NEW] Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic)
Public bug reported: The fault happens when I press "New game". $ trackballs Welcome to Trackballs. Using /usr/share/games/trackballs as gamedata directory. Xlib: extension "AMDGPU" missing on display ":0.0". Xlib: extension "GLX_ARB_context_flush_control" missing on display ":0.0". [WARNING] Warning. Could not find file /home/user/.trackballs/highScores [WARNING] Warning. Could not find file /home/user/.trackballs/user.gmr [WARNING] Warning. Could not find file /home/user/.trackballs/user.gmr Segmentation fault (core dumped) $ uname -a Linux user 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: trackballs 1.2.4-1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Feb 7 21:21:51 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (606 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: trackballs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: trackballs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "$glxinfo > glxinfo.txt" https://bugs.launchpad.net/bugs/1862402/+attachment/5326356/+files/glxinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862402 Title: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trackballs/+bug/1862402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862402] Re: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic)
** Attachment added: "strace -o strace-trackballs.txt trackballs" https://bugs.launchpad.net/ubuntu/+source/trackballs/+bug/1862402/+attachment/5326367/+files/strace-trackballs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862402 Title: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trackballs/+bug/1862402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862402] Re: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic)
Strace file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862402 Title: Trackballs segfaults on game start (amdgpu-pro 19.50) (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trackballs/+bug/1862402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751395] [NEW] scilab does not start (lubuntu 16.04.3)
Public bug reported: 4) when I try to start scilab it prints out this: " Could not create a Scilab main class. Error: Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> profileImpl GL4bc !!! not mapped at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071) at com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954) at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875) at com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842) at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80) at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230) at java.security.AccessController.doPrivileged(Native Method) at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216) at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297) at com.jogamp.opengl.GLProfile.get(GLProfile.java:988) at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722) at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733) at org.scilab.modules.gui.SwingView.(Unknown Source) at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source) at org.scilab.modules.core.Scilab.(Unknown Source) Scilab cannot create Scilab Java Main-Class (we have not been able to find the main Scilab class. Check if the Scilab and thirdparty packages are available). " ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: scilab 5.5.2-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Feb 24 03:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-01-07 (47 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: scilab UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: scilab (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "strace -o scilab-strace.txt scilab" https://bugs.launchpad.net/bugs/1751395/+attachment/5061503/+files/scilab-strace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751395 Title: scilab does not start (lubuntu 16.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1751395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751808] [NEW] OmegaT does not start (lubuntu 16.04.3)
Public bug reported: 4) Instead of starting OmegaT prints out this: user@user:~$ strace -o omegat-strace.txt omegat 85198: Info: === 85198: Info: OmegaT-2.3.0_1 (Mon Feb 26 17:38:29 MSK 2018) Locale en_US 85198: Info: Java: Oracle Corporation ver. 9-internal, executed from '/usr/lib/jvm/java-9-openjdk-amd64' (LOG_STARTUP_INFO) 85198: Info: Docking Framework version: 2.1.4 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7ffa419a6009, pid=4619, tid=4629 # # JRE version: OpenJDK Runtime Environment (9.0) (build 9-internal+0-2016-04-14-195246.buildd.src) # Java VM: OpenJDK 64-Bit Server VM (9-internal+0-2016-04-14-195246.buildd.src, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libjava.so+0x1d009] JNU_GetEnv+0x19 # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P" (or dumping to /home/user/core.4619) # # An error report file with more information is saved as: # /home/user/hs_err_pid4619.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Aborted (core dumped) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: omegat 2.3.0.1+dfsg-4 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Feb 26 17:56:25 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-01-07 (49 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: omegat UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: omegat (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "omegat-strace.txt" https://bugs.launchpad.net/bugs/1751808/+attachment/5063506/+files/omegat-strace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751808 Title: OmegaT does not start (lubuntu 16.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/omegat/+bug/1751808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751808] Re: OmegaT does not start (lubuntu 16.04.3)
** Attachment added: "Probably it's a core dump" https://bugs.launchpad.net/ubuntu/+source/omegat/+bug/1751808/+attachment/5063511/+files/hs_err_pid4619.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751808 Title: OmegaT does not start (lubuntu 16.04.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/omegat/+bug/1751808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772214] [NEW] pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018)
Public bug reported: 1,2) Please see the apport attachment. 3) Steps to reproduce: 1. Open pcmanfm-qt. 2. Go to root dir / 3. Change the view of the dir to "Detailed list" 4. Open /etc dir with double click. If it opened in Icon View mode then step back and try to enter to /etc 4) pcmanfm-qt segfaults in my case. My current related dmesg output: " [ 99.878774] pcmanfm-qt[1051]: segfault at 560d40011390 ip 560d40011390 sp 7ffe107ca5d8 error 15 [ 190.640536] pcmanfm-qt[1237]: segfault at 556c0b82dba0 ip 556c0b82dba0 sp 7fffefd12e08 error 15 [ 1214.139394] pcmanfm-qt[1320]: segfault at 7f242900dda0 ip 7f2428e39cde sp 7ffc37114630 error 4 in libc-2.27.so[7f2428da2000+1e7000] [ 1668.239954] pcmanfm-qt[3154]: segfault at 7fcb0f14f2b0 ip 7fcb0f14f2b0 sp 7ffe60521188 error 15 in libc-2.27.so[7fcb0f14e000+2000] " The last two is after installing of apport. But it maybe unrelated. I've tried it on Lubuntu Next daily-build of 19.05.2018. And the problem is existing on it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pcmanfm-qt 0.12.0-5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: LXQt Date: Sat May 19 21:58:55 2018 LiveMediaBuild: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Release amd64 (20180503) SourcePackage: pcmanfm-qt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcmanfm-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic lubuntu-next ** Attachment added: "$strace -o pcmanfm-qt.txt pcmanfm-qt" https://bugs.launchpad.net/bugs/1772214/+attachment/5141789/+files/pcmanfm-qt.txt ** Tags added: lubuntu-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772214 Title: pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1772214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755037] [NEW] PsychoPy does not start (lubuntu 16.04)
Public bug reported: 1,2) See apport attacments 3) I'd like to see what the program is. 4) I can't do that. Console output is: " fatal: Not a git repository (or any of the parent directories): .git 01:07:58 AM: Debug: Failed to connect to session manager: SESSION_MANAGER environment variable not defined " I've found a few related links: https://discourse.psychopy.org/t/fatal-not-a-git-repository-or-any-of-the-parent-directories-git/2172/7 https://discourse.psychopy.org/t/psychopy-not-running/3054?u=kyung ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: psychopy 1.82.02.dfsg-1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Mar 12 01:14:59 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-01-07 (63 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: psychopy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: psychopy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "strace file ($strace -o psychopy.txt psychopy)" https://bugs.launchpad.net/bugs/1755037/+attachment/5076241/+files/psychopy.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755037 Title: PsychoPy does not start (lubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psychopy/+bug/1755037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
It does work on xenial. (Seems we don't need xorg hwe for hwe kernels now.) user@user:~$ cat /proc/cmdline BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-59-generic root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid user@user:~$ uname -a Linux user 4.15.0-59-generic #66~16.04.1-Ubuntu SMP Wed Aug 14 15:42:01 UTC 2019 i686 i686 i686 GNU/Linux ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846708] [NEW] fl-run-test DistributionNotFound error (doesn't start) (Lubuntu bionic)
Public bug reported: The console output: $ fl-run-test Traceback (most recent call last): File "/usr/bin/fl-run-test", line 6, in from pkg_resources import load_entry_point File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3088, in @_call_aside File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3072, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 574, in _build_master ws.require(__requires__) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 892, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 778, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'funkload==1.17.2' distribution was not found and is required by the application $ Currently the funkload package in bionic has version 1.17.1-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: funkload 1.17.1-2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Oct 4 13:17:08 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (480 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: funkload UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: funkload (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: The console output: - $ fl-run-test + $ fl-run-test Traceback (most recent call last): - File "/usr/bin/fl-run-test", line 6, in - from pkg_resources import load_entry_point - File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3088, in - @_call_aside - File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3072, in _call_aside - f(*args, **kwargs) - File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set - working_set = WorkingSet._build_master() - File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 574, in _build_master - ws.require(__requires__) - File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 892, in require - needed = self.resolve(parse_requirements(requirements)) - File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 778, in resolve - raise DistributionNotFound(req, requirers) + File "/usr/bin/fl-run-test", line 6, in + from pkg_resources import load_entry_point + File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3088, in + @_call_aside + File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3072, in _call_aside + f(*args, **kwargs) + File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set + working_set = WorkingSet._build_master() + File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 574, in _build_master + ws.require(__requires__) + File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 892, in require + needed = self.resolve(parse_requirements(requirements)) + File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 778, in resolve + raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'funkload==1.17.2' distribution was not found and is required by the application $ Currently the funkload package in bionic has version 1.17.1-2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: funkload 1.17.1-2 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Oct 4 13:17:08 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (480 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: funkload UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846708 Title: fl-run-test DistributionNotFound error (doesn't start) (Lubuntu bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/funkload/+bug/1846708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/lis
[Bug 1828625] Re: Can't purge if apt-get update fails (18.04)
And I guess the solution is in deleting "exit 1" on line 120 of bionic ppa-purge script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828625 Title: Can't purge if apt-get update fails (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1828625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828625] [NEW] Can't purge if apt-get update fails (18.04)
Public bug reported: I want to purge buggy ppa that makes apt-get update to report error, but I can't because apt-get update reports error. It's a circle. I can remember a good times when ppa-purge didn't call for apt-get update at all (or that was "add-apt-repository", don't remember...). And everything was ok. I think it's just a wasting of time in the most cases. If I wish to "apt-get update" I'd like to do it manually. But ppa-purge does't have a way to let me avoid it. The buggy ppa is ppa:swatchbooker/ppa. It doesn't have a Release file for bionic for now so "apt-get update" passes the error to ppa-purge and that's it. One can try to add this repo and then ppa-purge it on Ubuntu bionic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ppa-purge 0.2.8+bzr63 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Fri May 10 23:05:17 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (333 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ppa-purge UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ppa-purge (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828625 Title: Can't purge if apt-get update fails (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1828625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
Xenial hwe kernels is affected. Non-hwe isn't affected indeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
*** This bug is a duplicate of bug 1838115 *** https://bugs.launchpad.net/bugs/1838115 I didn't know it. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: x86: mm: early boot problem on i386 with KPTI enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
I've read Juerg's explanation [1]. I guess this commit will appear in xenial repos automatically. Thank you. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
*** This bug is a duplicate of bug 1838115 *** https://bugs.launchpad.net/bugs/1838115 So we use this tags for repositories only? I thought it can be used for a fix in the bug report thread too. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: x86: mm: early boot problem on i386 with KPTI enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
xenial-proposed still doesn't too. The fix for 4.15 does work (https://kernel.ubuntu.com/~cking/lp1827884/4.15). Just copy it to xenial-proposed or something. (Sorry for adding wrong tag, now I know we need to wait for kernel-bot request). ** Tags removed: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency and newer don't boot after update (16.04)(i386)
It does happen for 4.15.0-50-generic too. ** Summary changed: - linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386) + linux-image-4.15.0-48-lowlatency and newer don't boot after update (16.04)(i386) ** Summary changed: - linux-image-4.15.0-48-lowlatency and newer don't boot after update (16.04)(i386) + linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) ** Tags added: apport-collected ** Description changed: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 1820 F pulseaudio + CurrentDesktop: LXDE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb + InstallationDate: Installed on 2018-10-01 (234 days ago) + InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) + MachineType: TOSHIBA Satellite L300 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid + ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-47-lowlatency N/A + linux-backports-modules-4.15.0-47-lowlatency N/A + linux-firmware1.157.21 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: xenial + Uname: Linux 4.15.0-47-lowlatency i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/10/2008 + dmi.bios.vendor: INSYDE + dmi.bios.version: 1.50 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: Base Board Product Name + dmi.board.vendor: Intel Corp. + dmi.board.version: Base Board Version + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: Chassis Manufacturer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: + dmi.product.family: Type1Family + dmi.product.name: Satellite L300 + dmi.product.version: PSLB0E-014012RU + dmi.sys.vendor: TOSHIBA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266160/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266158/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266162/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266159/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266165/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266171/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266166/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266161/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266167/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266163/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266164/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266170/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266169/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266168/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386)
It floods this before reboot: IP: print_modules+0x40/0xbd *pdpt = 36445001 *pde = 0de36063 *pte = Thread overran stack, or stack corrupted Oops: 000 [a1672] PREEMPI SMP PTI Modules linked in: BUG: unable to handle kernel paging request at fffc I don't know which string is first. I can see some video artifacts before rebooting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386)
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844869] [NEW] krita doesn't start (stack smash detected) (Lubuntu bionic)
Public bug reported: Krita doesn't start on my system for a long time. I tried krita ppa versions with the same result. I use appimage version (krita-4.1.8 -41fb78e-x86_64.appimage), that works well. Didn't try newer appimage versions. I have /tmp mounted with noexec and my umask is 066. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: krita 1:4.0.1+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Sep 21 16:00:26 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (467 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: krita UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: krita (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "krita strace" https://bugs.launchpad.net/bugs/1844869/+attachment/5290186/+files/krita.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844869 Title: krita doesn't start (stack smash detected) (Lubuntu bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1844869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844869] Re: krita doesn't start (stack smash detected) (Lubuntu bionic)
** Attachment added: "krita-terminal-output.txt" https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1844869/+attachment/5290190/+files/krita-terminal-output.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to krita in Ubuntu. https://bugs.launchpad.net/bugs/1844869 Title: krita doesn't start (stack smash detected) (Lubuntu bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1844869/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1844869] Re: krita doesn't start (stack smash detected) (Lubuntu bionic)
gdb log. I used this tutorial: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports #Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29 ** Attachment added: "krita-gdb-log.txt" https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1844869/+attachment/5290191/+files/krita-gdb-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844869 Title: krita doesn't start (stack smash detected) (Lubuntu bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1844869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810093] [NEW] pandora window can't be closed, and it doesn't work
Public bug reported: 4) I can't close the pandora window. Cancel and close window doesn't work. It closes with GIMP only. And pandora doesn't do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pandora 0.7.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Dec 30 18:46:16 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (202 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pandora UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pandora (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810093 Title: pandora window can't be closed, and it doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pandora/+bug/1810093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231869] Re: No valid JVM found to run JOSM.
This bug persists on 18.04.1. I have java installed. Also I've tried to change to java 8 by galternatives and it doesn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/231869 Title: No valid JVM found to run JOSM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/231869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810645] [NEW] No valid JVM found to run JOSM. (josm doesn't start) (bionic)
Public bug reported: This is an old bug. Fix released, but it doesn't work on bionic. I can't change the status of old bugs, so I'm opening the new one. The old, fixed bugs: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/231869 https://bugs.launchpad.net/ubuntu/+source/josm/+bug/1186377 The following works $ JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 josm %F ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: josm 0.0.svn13576+dfsg-3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Jan 6 12:56:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (209 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: josm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: josm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: This is an old bug. Fix released, but it doesn't work on bionic. I can't - change the status of old bugs, so I'm opening a new one. + change the status of old bugs, so I'm opening the new one. The old, fixed bugs: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/231869 https://bugs.launchpad.net/ubuntu/+source/josm/+bug/1186377 The following works - $ JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64 josm + $ JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 josm %F ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: josm 0.0.svn13576+dfsg-3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Jan 6 12:56:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (209 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: josm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810645 Title: No valid JVM found to run JOSM. (josm doesn't start) (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/1810645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810645] Re: No valid JVM found to run JOSM. (josm doesn't start) (bionic)
** Attachment added: "josm.desktop" https://bugs.launchpad.net/ubuntu/+source/josm/+bug/1810645/+attachment/5227203/+files/josm.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810645 Title: No valid JVM found to run JOSM. (josm doesn't start) (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/josm/+bug/1810645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891991] [NEW] gthumb crashes ("realloc(): invalid pointer" or "free(): invalid next size (fast)") (Ubuntu 20.04)
Public bug reported:
The console output:
```
$ gthumb
** (gthumb:87867): WARNING **: 10:55:43.072: Invalid thumbnailer:
missing Exec key
** (gthumb:87867): WARNING **: 10:55:43.072: Invalid thumbnailer: missing Exec
key
** (gthumb:87867): WARNING **: 10:55:43.096: Invalid thumbnailer: missing Exec
key
** (gthumb:87867): WARNING **: 10:55:43.096: Invalid thumbnailer: missing Exec
key
realloc(): invalid pointer
Aborted (core dumped)
```
Console output when I did strace:
```
$ strace -o gthumb.strace.txt gthumb
** (gthumb:89344): WARNING **: 10:57:58.057: Invalid thumbnailer:
missing Exec key
** (gthumb:89344): WARNING **: 10:57:58.058: Invalid thumbnailer: missing Exec
key
** (gthumb:89344): WARNING **: 10:57:58.098: Invalid thumbnailer: missing Exec
key
** (gthumb:89344): WARNING **: 10:57:58.099: Invalid thumbnailer: missing Exec
key
free(): invalid next size (fast)
Aborted (core dumped)
```
I have turned off the "Exec key" of evince thumbnailer if it matter.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gthumb 3:3.8.0-2.1build1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXDE
Date: Tue Aug 18 10:56:22 2020
EcryptfsInUse: Yes
SourcePackage: gthumb
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gthumb (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Attachment added: "gthumb.strace.txt"
https://bugs.launchpad.net/bugs/1891991/+attachment/5402389/+files/gthumb.strace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891991
Title:
gthumb crashes ("realloc(): invalid pointer" or "free(): invalid next
size (fast)") (Ubuntu 20.04)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/1891991/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871715] Re: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart
Thanks for reviewing. The need to force restart arisen due to another issue - no connectivity through Bluetooth of my Sony headphones. It was recognized through the Sound setting, but the sound itself still came through another source (my screen for this matter). I think it might be a good idea to open a separate bug ticket for the not connectivity of the headphones. Kind regards, DS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871715 Title: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871715] Re: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart
It indeed sounds very resembling to what I had, but not the exact thing. I will open a new ticket with the details once (or if) it happens again. Thanks for reviewing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871715 Title: gnome-control-center SIGSEGV in pa_context_set_error() on pulseaudio restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883173] [NEW] shutdown or reboot takes too long (link to the patch) (20.04)
Public bug reported: I guess it's a pcmanfm bug. While shutting down I see this message: systemd-shutdown[1]: Waiting for process: gvfs-udisks2-vo, gvfs-thash, pcmanfm, gvfs-afc-volume, pulseaudio, systemd, dbus-daemon I found this link to related patch https://src.fedoraproject.org/rpms/pcmanfm/blob/4b1c3e3004e996ea3192f1725d3b8a916c7c3ab5/f/pcmanfm-0201 -main-set-the-GIOChannel-encoding-to-binary.patch The place where I found it https://bbs.archlinux.org/viewtopic.php?id=254266 As a workaround I set DefaultTimeoutStopSec=3s DefaultTimeoutAbortSec=3s in /etc/systemd/system.conf, but of course it's not the right way. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcmanfm 1.3.1-1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXDE Date: Thu Jun 11 22:38:41 2020 EcryptfsInUse: Yes SourcePackage: pcmanfm Udisks_dump: Error: [Errno 2] No such file or directory: 'udisks' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcmanfm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883173 Title: shutdown or reboot takes too long (link to the patch) (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1883173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883318] [NEW] blender doesn't start with the settings from official portable version (20.04)
Public bug reported: I used official portable version on Lubuntu 18.04 and I have the settings file that still works with official portable version (2.82a). For some reason it doesn't work with blender from ubuntu 20.04 repos. I tried to delete files and directories one by one and the problem is in my userpref.blend. For some reason it works with official portable version but doesn't work with blender shipped with Ubuntu. I could to delete the config directory, but it would take some time to recreate all my customs. I get this messages when I try to start blender: $ blender Read prefs: /home/user/.config/blender/2.82/config/userpref.blend blender(BLI_system_backtrace+0x37) [0x5573be937897] blender(BLI_exists+0x73) [0x5573be932d43] blender(BLI_is_dir+0xd) [0x5573be93300d] blender(+0x13f3912) [0x5573bc24a912] blender(wm_homefile_read+0x54a) [0x5573bc4336aa] blender(WM_init+0x163) [0x5573bc437e53] blender(main+0x2e1) [0x5573bc1f7401] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f61e3fea0b3] blender(_start+0x2e) [0x5573bc2458ae] BLI_assert failed: /build/blender-RL3axj/blender-2.82.a+dfsg/source/blender/blenlib/intern/storage.c:240, BLI_exists(), at '!BLI_path_is_rel(name)' Aborted (core dumped) I will attach my userpref.blend to next message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: blender 2.82.a+dfsg-1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXDE Date: Fri Jun 12 22:25:22 2020 EcryptfsInUse: Yes SourcePackage: blender UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: blender (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883318 Title: blender doesn't start with the settings from official portable version (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1883318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883318] Re: blender doesn't start with the settings from official portable version (20.04)
** Attachment added: "userpref.blend" https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1883318/+attachment/5383372/+files/userpref.blend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883318 Title: blender doesn't start with the settings from official portable version (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1883318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884810] [NEW] Anbox doesn't start, /dev/binder isn't created (20.04)
Public bug reported:
There is one of related bug reports
https://github.com/anbox/anbox-modules/issues/20
Some people say that snap edge version does work. But I get segfault with the
both snap versions.
Probably deb version doesn't work after kernel upgrade.
$ anbox launch --package=org.anbox.appmgr
--component=org.anbox.appmgr.AppViewActivity
[ 2020-06-23 16:34:25] [daemon.cpp:61@Run] Application manager service is not
running yet
$ anbox session-manager
[ 2020-06-23 16:35:01] [session_manager.cpp:133@operator()] Failed to start as
either binder or ashmem kernel drivers are not loaded
$ lsmod | grep binder
binder_linux 180224 0
$ lsmod | grep ashmem
ashmem_linux 20480 0
$ ls -1 /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
/dev/ashmem
I use default kernel version (generic, non-hwe).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: anbox 0.0~git20191115-1build1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXDE
Date: Tue Jun 23 19:23:43 2020
EcryptfsInUse: Yes
SourcePackage: anbox
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: anbox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884810
Title:
Anbox doesn't start, /dev/binder isn't created (20.04)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anbox/+bug/1884810/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879015] [NEW] Autologin doesn't work (Lubuntu 18.04)
Public bug reported: I tried everything. 3) I expected a working autologin once I set autologin-user=myusername in /etc/lightdm/lightdm.conf. Also I tried to change default session option. After I set "Do not ask password" in Users and Groups GUI autologin didn't work either. I needed to press "Login" button anyway. I don't know where the problem is. The only way to make autologin work I know is to set "Autologin" option while system installation. I don't want to reinstall to change just one option. Currently I use slim desktop manager. It's simpler and works. I have all possible options in /etc/slim.conf, I just need to uncomment something and edit. No need of reading docs and forums to just know what it can do. I hope someday lightdm will be changed in the same KISS way as slim. 4) For some reason autologin doesn't work. Looks like lightdm just ignores its config files. It either shouldn't ignore these files or should provide a tool for configuring. The GUI tools I found doesn't provide an autologin option. (lightdm-autologin-greeter package doesn't help (I've edited /etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf properly), lightdm package doesn't have /etc/lightdm/lightdm.conf file) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic i686 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 16 04:05:25 2020 InstallationDate: Installed on 2020-05-09 (6 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release i386 (20200203) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879015 Title: Autologin doesn't work (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159356] Re: When DMA is disabled system freeze on high memory usage
Just a little note. Probably it is not DMA related issue as it entitled. I found it happening with zram swap too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: When DMA is disabled system freeze on high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821499] [NEW] [Feature request] /etc/init/zram-config.conf has no any options. Please add a few.
Public bug reported: Such people as me would like to set some permanent paramenters for zram without editing /usr/bin/init-zram-swapping script file. I think it's wrong to edit something in /usr/bin. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zram-config 0.5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Mar 24 09:37:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (285 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: zram-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zram-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic feature-request not-a-bug wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821499 Title: [Feature request] /etc/init/zram-config.conf has no any options. Please add a few. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1821499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159356] Re: When DMA is disabled system freeze on high memory usage
I've tried to set vm.min_free_kbytes to 6% of my total physical RAM, divided by
the number of cores as it is said there
https://askubuntu.com/questions/41778/computer-freezing-on-almost-full-ram-possibly-disk-cache-problem,
but I decided to keep vm.swapiness at its default (60), because I was going to
tune up zram.
And then I had installed zram-config package, opened
/usr/bin/init-zram-swapping file with my text editor and had changed this string
mem=$(((totalmem / 2 / ${NRDEVICES}) * 1024))
to this:
mem=$(((totalmem / 2 / ${NRDEVICES}) * 5 * 1024))
Then I had rebooted and tested this all with "stress -m 4 --vm-bytes=1G".
This all was happening on my one core 2Gb x86 Lubuntu 16.04 notebook. Seems it
works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/159356
Title:
When DMA is disabled system freeze on high memory usage
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159356] Re: When DMA is disabled system freeze on high memory usage
So as a conclusion for my old 2Gb laptop, I've set zram to twice of amount of physical RAM (/usr/bin/init-zram-swapping), and have added this parameters to /etc/sysctl.d/99-sysctl.conf: vm.min_free_kbytes=128000 vm.overcommit_memory=2 vm.overcommit_ratio=90 And seems it work for me. And I have to say that I don't have physical swap and have /tmp and /var/tmp mounted to ram disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: When DMA is disabled system freeze on high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 159356] Re: When DMA is disabled system freeze on high memory usage
The editing of overcommits makes chromium crash. So I don't know -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: When DMA is disabled system freeze on high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
thermald+systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775717 Title: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
I have another issue, but it may be relevant. I can't make fancontrol service restart after suspend. I've created 3 files (/lib/systemd/system-sleep/fancontrol, /etc/systemd/system/fancontrol-resume.service, /etc/pm/sleep.d/10_fancontrol) and fill them with proper texts, made some of them executable. But it doesn't work in most times I suspend. So maybe it's a systemd related problem? Some services just doesn't restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775717 Title: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] [NEW] linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386)
Public bug reported: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386)
And I don't know why, but I had booted with 4.15.0-48-lowlatency once. Currently the "not booting" state is quite stable. Even after reinstallation of the kernel packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386)
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+attachment/5261501/+files/kern.log ** Description changed: - Currently I an on 4.15.0-47-lowlatency. + Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386)
** Summary changed: - linux-image-4.15.0-48-lowlatency doesn't boot after update (18.04)(i386) + linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386)
kern.log has nothing about it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827725] Re: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386)
I've returned to non-hwe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1827725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] [NEW] twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
Public bug reported: The console output: $ twinkle QApplication: invalid style override passed, ignoring it. Language name: "en" mprotect failed in ExecutableAllocator::makeExecutable: Permission denied *** stack smashing detected ***: terminated Aborted (core dumped) $ I've attached a strace output file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: twinkle 1:1.10.1+dfsg-3 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Apr 16 15:29:30 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (309 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: twinkle UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: twinkle (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "strace -o twinkle.txt twinkle" https://bugs.launchpad.net/bugs/1824986/+attachment/5256269/+files/twinkle.txt ** Summary changed: - twinkle doesn't start (stack smashing detected) + twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
And I have /home and /tmp mounted with noexec. Does anyone know how to find ubuntu-devel-disc...@lists.ubuntu.com in "Subscribe someone else"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825652] Re: False positive symlink loop detection for amdgpu-dkms (lubuntu 18.04)
Is it possible to exclude this directory from debsums checking? ** Description changed: The console output: - $ debsums -c > debsums.txt + $ debsums -c > debsums.txt debsums: Error: symlink loop detected in path 'usr/src/amdgpu-18.50-725072/Makefile'. Please file a bug again amdgpu-dkms. $ The /usr/src is symlinked to /usr/share/.src. '/usr/src/amdgpu-18.50-725072/Makefile' is not a symlink, but a file. - The md5sum of this file is ok. + The md5sum of this file is ok. amdgpu-dkms package is from amdgpu-pro + pack. I have btrfs filesystem and did some hardlink optimizations by FSlint Janiator. I don't know what is wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: debsums 2.2.2 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Apr 20 17:25:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (313 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: debsums UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825652 Title: False positive symlink loop detection for amdgpu-dkms (lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debsums/+bug/1825652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825652] [NEW] False positive symlink loop detection for amdgpu-dkms (lubuntu 18.04)
Public bug reported: The console output: $ debsums -c > debsums.txt debsums: Error: symlink loop detected in path 'usr/src/amdgpu-18.50-725072/Makefile'. Please file a bug again amdgpu-dkms. $ The /usr/src is symlinked to /usr/share/.src. '/usr/src/amdgpu-18.50-725072/Makefile' is not a symlink, but a file. The md5sum of this file is ok. amdgpu-dkms package is from amdgpu-pro pack. I have btrfs filesystem and did some hardlink optimizations by FSlint Janiator. I don't know what is wrong. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: debsums 2.2.2 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Apr 20 17:25:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (313 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: debsums UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: debsums (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825652 Title: False positive symlink loop detection for amdgpu-dkms (lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debsums/+bug/1825652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
I think you already have tried to take the fans by fancontrol. I thought if fancontrol works on this laptop then you just need to add a service to stop fancontrol service before suspend and start it again after suspend after small delay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775717 Title: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826109] [NEW] Permission denied on running krita (Lubuntu 18.04)
Public bug reported: I use umask 066 in all profiles. Maybe this is the cause. The console output: $ flatpak run org.kde.krita error: Error opening file /var/lib/flatpak/app/org.kde.krita/x86_64/stable/efb8b29d1255aa9bbd77212c991c0e82710b0357a5f1c167bce1fb4202ebeadf/deploy: Permission denied $ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: flatpak 1.0.7-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Apr 24 08:42:53 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (316 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "strace -o flatpack.txt flatpak run org.kde.krita" https://bugs.launchpad.net/bugs/1826109/+attachment/5258435/+files/flatpack.txt ** Summary changed: - Permission denied on runing krita (Lubuntu 18.04) + Permission denied on running krita (Lubuntu 18.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826109 Title: Permission denied on running krita (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1826109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
It still present in 4.15.0-54.58 (Tested with lowlatency kernel version on Toshiba Sattelite L300-11Q). "nopti" helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
I've tried. It's still happening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
Seems I used wrong kernel for previous test. Sorry. This new kernel works, but xorg doesn't start. I'm testing on Lubuntu xenial. How to add "Xenial" under the "Bionic" on the top of this thread? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
But I use Lubuntu Xenial. Probably this is why xorg doesn't start with the last test version. I can upload dmesg or something else if it is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
I've rechecked the last test version. Previous problem is gone, but xorg doesn't start. Xorg doesn't start even with the "nopti" option. BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-54-generic root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid Mitigation: PTI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835966] [NEW] Screenruler doesn't start (Lubuntu 18.04.2)
Public bug reported: The console output: user@user:~$ screenruler Loading libraries... /usr/share/screenruler/utils/addons_ruby.rb:42: warning: constant ::Fixnum is deprecated Traceback (most recent call last): 35: from /usr/bin/screenruler:51:in `' 34: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `require' 33: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `each' 32: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `block in require' 31: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 30: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 29: from /usr/lib/ruby/vendor_ruby/gtk2.rb:11:in `' 28: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `require' 27: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `each' 26: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `block in require' 25: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 24: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 23: from /usr/lib/ruby/vendor_ruby/gtk2/base.rb:12:in `' 22: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `require' 21: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `each' 20: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `block in require' 19: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 18: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' 17: from /usr/lib/ruby/vendor_ruby/glib2.rb:127:in `' 16: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `require' 15: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `each' 14: from /usr/share/screenruler/utils/addons_ruby.rb:59:in `block in require' 13: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:39:in `require' 12: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require' 11: from /usr/lib/ruby/2.5.0/rubygems.rb:213:in `try_activate' 10: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1063:in `find_by_path' 9: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1063:in `find' 8: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1063:in `each' 7: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1064:in `block in find_by_path' 6: from /usr/lib/ruby/2.5.0/rubygems/bundler_version_finder.rb:46:in `compatible?' 5: from /usr/lib/ruby/2.5.0/rubygems/bundler_version_finder.rb:12:in `bundler_version' 4: from /usr/lib/ruby/2.5.0/rubygems/bundler_version_finder.rb:29:in `bundler_version_with_reason' 3: from /usr/lib/ruby/2.5.0/rubygems/bundler_version_finder.rb:81:in `lockfile_version' 2: from /usr/lib/ruby/2.5.0/rubygems/bundler_version_finder.rb:93:in `lockfile_contents' 1: from /usr/lib/ruby/2.5.0/rubygems/util.rb:116:in `traverse_parents' /usr/share/screenruler/utils/addons_ruby.rb:62:in `loop': wrong number of arguments (given 0, expected 2..3) (ArgumentError) user@user:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: screenruler 0.960+bzr41-1.2 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Jul 10 01:06:06 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (393 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: screenruler UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: screenruler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835966 Title: Screenruler doesn't start (Lubuntu 18.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screenruler/+bug/1835966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
https://github.com/LubosD/twinkle/issues/157 ** Bug watch added: github.com/LubosD/twinkle/issues #157 https://github.com/LubosD/twinkle/issues/157 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+attachment/5277231/+files/gdb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
Thank YOU, tremendous super cosmo-heroes. ** Attachment added: "gdb-with-qt-dbgsymbols.txt" https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+attachment/5277333/+files/gdb-with-qt-dbgsymbols.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
The previous gdb was with qt 5.9.5+dfsg-0ubuntu2.1 from ubuntu-security. This one is with qt 5.9.5+dfsg-0ubuntu2.3 from proposed updates. ** Attachment added: "gdb-qt-proposed(5.9.5+dfsg-0ubuntu2.3).txt" https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1824986/+attachment/5277334/+files/gdb-qt-proposed%285.9.5+dfsg-0ubuntu2.3%29.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
Yes, this does help. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
I could see that without "quiet" boot option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: x86: mm: early boot problem on i386 with KPTI enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
