[Bug 252415] Re: remake (and make) memory free() error
** Changed in: remake (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/252415 Title: remake (and make) memory free() error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remake/+bug/252415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880837] Re: remake for GNU Make 4.3 is available
** Changed in: remake (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880837 Title: remake for GNU Make 4.3 is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remake/+bug/1880837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071467] Re: python3-numpysane 0.41-4 FTBFS
Fixed in Debian in the 0.41-5 upload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071467 Title: python3-numpysane 0.41-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-numpysane/+bug/2071467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064959] Re: mrcal was deleted from ubuntu 24.04
Hi. Thank you very much for doing this! The process looked challenging, and I had given up. That debdiff to mrbuild 1.8 (to effectively make it into mrbuild 1.9) looks good to me. And if it makes mrcal build, then that's the required proof that it works properly. With this updated mrbuild uploaded, the rebuilt mrcal will also be uploaded, and both will end up in noble? And pyfltk ALSO didn't make it into noble??? That's yet another one of my packages that was thrown away without telling me, and giving me a chance to fix it. I'm guessing it's because swig 4.2 required patching pyfltk. Can we do the same thing for pyfltk? Uploading the current thing that's in Debian would be wonderful. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064959 Title: mrcal was deleted from ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mrbuild/+bug/2064959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508298] Re: pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no format arguments [-Werror=format-security]
** Changed in: pyfltk (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508298 Title: pyfltk: FTBFS: ./python/fltk_wrap.cpp:5241:35: error: format not a string literal and no format arguments [-Werror=format-security] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyfltk/+bug/1508298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054724] Re: "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2" package isn't automatically installed by metapackage "nvidia-driver-545_545.29.06-0ubuntu0.23.10.2"
# lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054724 Title: "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2" package isn't automatically installed by metapackage "nvidia- driver-545_545.29.06-0ubuntu0.23.10.2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2054724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313166] Re: SIFT functionality is stripped out from VLFeat
** Changed in: vlfeat (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313166 Title: SIFT functionality is stripped out from VLFeat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlfeat/+bug/1313166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064959] Re: mrcal was deleted from ubuntu 24.04
I'm requesting an SRU: https://wiki.ubuntu.com/StableReleaseUpdates [ Proposed solution ] The original bug report and its solution are described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067398 * Update mrbuild to >= 1.9-2 to fix the build issue that caused mrcal to be deleted * Build and include the omitted source packages: * mrcal gl-image-display [ Impact ] * The deleted packages mrcal, gl-image-display will be available in 24.04 [ Test Plan ] * The affected packages have no rdepends * The "mrbuild" package does have a build-rdepends: * mrcal * gl-image-display * libdogleg * mrgingham * vnlog And none of these have any rdepends or build-rdepends outside of this set * Testing would mean confirming that the updated mrbuild can still be used to build the above packages. This will work, since the update to mrbuild is tiny, and is verified functional in Debian [ Where problems could occur ] * The proposed solution adds two deleted source packages, and updates one (mrbuild). Thus the mrbuild update is the only thing that could possibly break anything * Because of the limited depends and rdepends, the implications are limited to the above-listed set of packages. mrbuild is the build system. If the above packages build successfully with the updated mrbuild, and their tests pass, we can declare victory. [ Other Info ] * As described in the mailing list thread above, these packages weren't excluded because there was anything specifically wrong. The problem has been fixed for weeks in Debian when the Ubuntu FTBFS bug came through, and the only reason for the exclusion is the rush to meet the release deadline. ** Bug watch added: Debian Bug tracker #1067398 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067398 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064959 Title: mrcal was deleted from ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mrcal/+bug/2064959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064959] [NEW] mrcal was deleted from ubuntu 24.04
Public bug reported: Due to an update to an unrelated package and insufficient communication and the rush to get 24.04 out the door, this package was dropped from the release. Lots of detail about what happened and how to resolve it appears here: https://lists.ubuntu.com/archives/ubuntu-devel/2024-May/042982.html ** Affects: mrcal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064959 Title: mrcal was deleted from ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mrcal/+bug/2064959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970021] [NEW] xrandr reports 1360x768 instead of 1366x768
Public bug reported: See https://gitlab.freedesktop.org/xorg/lib/libxcvt/-/merge_requests/9. The screenshot there is taken with jammy's xwayland 2:22.1.1-1 (running fullscreen, maximized by the compositor) and libxcvt0 0.1.1-3. This bug prevents applications from filling the screen when fullscreen, and can cause blurriness in applications that compensate for the missing 6x of width. ** Affects: libxcvt (Ubuntu) Importance: Undecided Status: New ** Description changed: See https://gitlab.freedesktop.org/xorg/lib/libxcvt/-/merge_requests/9. + The screenshot there is taken with jammy's xwayland 2:22.1.1-1 (running + fullscreen, maximized by the compositor) and libxcvt0 0.1.1-3. - This prevents applications from filling the screen when fullscreen, and - can cause blurriness in applications that compensate for the missing 6x - of width. + This bug prevents applications from filling the screen when fullscreen, + and can cause blurriness in applications that compensate for the missing + 6x of width. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970021 Title: xrandr reports 1360x768 instead of 1366x768 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcvt/+bug/1970021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964974] Re: gufw doesn't start (ValueError: invalid literal for int() with base 10: 'WARN:)
My Ubuntu is updated. Gufw worked since fresh install. I don't know when it stopped and what happened. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964974 Title: gufw doesn't start (ValueError: invalid literal for int() with base 10: 'WARN:) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1964974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964974] [NEW] gufw doesn't start (ValueError: invalid literal for int() with base 10: 'WARN:)
Public bug reported: 1) Ubuntu 20.04.4 LTS 2) 20.04.1-1ubuntu1 3) I expected to see the gufw GUI 4) After password input there is nothing Console output: user@user:~$ gufw Traceback (most recent call last): File "/usr/share/gufw/gufw/gufw.py", line 30, in gufw = Gufw(controler.get_frontend()) File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 80, in __init__ self._set_initial_values() File "/usr/share/gufw/gufw/gufw/view/gufw.py", line 283, in _set_initial_values self.listening = ListeningReport(self) File "/usr/share/gufw/gufw/gufw/view/listening.py", line 35, in __init__ self._show_report() File "/usr/share/gufw/gufw/gufw/view/listening.py", line 48, in _show_report self._view_report(report, self.previous_report) File "/usr/share/gufw/gufw/gufw/view/listening.py", line 83, in _view_report self.gufw.listening_model.set_value(iter_row, 1, int(line_split[1].strip())) # port ValueError: invalid literal for int() with base 10: 'WARN:' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gufw 20.04.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXDE Date: Tue Mar 15 17:33:26 2022 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: gui-ufw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gui-ufw (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/1964974 Title: gufw doesn't start (ValueError: invalid literal for int() with base 10: 'WARN:) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1964974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
All these links points to names like foobar.png, but what's important that they point to locations excluded by the policy (actually, the same directory where the links reside!). As long as the policy is in force, nothing can be installed to locations they point to - besides more broken links, of course. I actually don't understand the rationale of all this - even if these links are pointing somewhere else, there should be nothing in that directory, by policy! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
In this case the links are not pointing to directories, they are pointing to files in the same directory. So there is no excuse to install them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
Sure, when I was filing the report I had no idea what's really going on - the only indications were `dpkg -V` reporting missing files, and broken links in /usr/share/doc. ** Description changed: Also reported on https://github.com/tianon/docker-brew-ubuntu- core/issues/230 Using official Jammy image in Docker (macOS) and Podman (Fedora). In both cases, using CLI in the image and running apt install singular-doc dpkg -V singular-doc reports a lot of missing files. In fact, the only present files are dangling links to missing files in the package. + (EDIT: the latter should not be there, it contradics `exclude` policy for dpkg installed in the Docker image) + The package itself is not broken - extracting it in Jammy not in Docker/Podman (say, in an lxc container) works. And extracting it in Debian/bookworm CLI run in Docker works too. As well, the same behaviour is observed using the corresponding singular-doc_4.2.1-p3+ds-1_all.deb file, and installing it using dpkg -i. This points to dpkg as the culprit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
And if you want to keep this behaviour, at least make sure `dpkg -V` reports that files are missing due to a policy, not cause it's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
This was discovered during the run of a CI, and interactive steps are provided for the ease of reproduction, not because it's the way it was found. If you don't know how to use Docker images interactively, it doesn't mean they are not used this way. Also, even if I'd agree that Docker containers are useless for interactive work (I don't) note that the steps still install broken symbolic links into /usr/share/doc. One sees # ls -l /usr/share/doc/singular/html/ total 0 lrwxrwxrwx 1 root root 13 Dec 17 20:20 sing_1068.png -> sing_1008.png ... root@c9df22f5e5ab:/sage# ls -l /usr/share/doc/singular/html/ | wc -l 71 And I really think that it's up to the user to decide how to use Docker containers, and you should not break things like this. By the way, Jammy lxc container does not show this bug - are you telling me that lxc images are OK for interactive work, but Docker containers are not? Containers/images are very useful for quick testing of whatever pops up, and breaking system packages like this is very bad. I wasted a day chasing this weirdness up - dpkg should at the very least emit a warning that it drops things in such a case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] [NEW] dpkg incorrectly installs singular-doc in jammy Docker container
Public bug reported: Also reported on https://github.com/tianon/docker-brew-ubuntu- core/issues/230 Using official Jammy image in Docker (macOS) and Podman (Fedora). In both cases, using CLI in the image and running apt install singular-doc dpkg -V singular-doc reports a lot of missing files. In fact, the only present files are dangling links to missing files in the package. The package itself is not broken - extracting it in Jammy not in Docker/Podman (say, in an lxc container) works. And extracting it in Debian/bookworm CLI run in Docker works too. As well, the same behaviour is observed using the corresponding singular-doc_4.2.1-p3+ds-1_all.deb file, and installing it using dpkg -i. This points to dpkg as the culprit. ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Bug watch added: trac.sagemath.org/ #32789 https://trac.sagemath.org/ticket/32789 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
What's unusual about singular-doc_4.2.1-p3+ds-1_all.deb ? I suppose * data.tar is compressed using zst * it contains symbolic links within the tarball. The data.tar.zst tarball extracted from .deb works fine in Docker image CLI (assuming zstd is installed), so I presume it's something to do with dpkg expaning the file by itself. This was found while working on https://trac.sagemath.org/ticket/32789 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- 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 1916830] [NEW] Crashes and memory leaks after reloading knockd
Public bug reported: knockd leaks memory and segfaults after systemd reload knockd (or killall -HUP knockd) due to use-after-free. Checked on bionic, but this is very likely affect other versions as well because git blame tells these bugs are years old. Fixes are merged to master now - see https://github.com/jvinet/knock/pull/74. ** Affects: knockd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916830 Title: Crashes and memory leaks after reloading knockd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1916830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897371] Re: don't ship libgc with -Wl,-Bsymbolic-functions
** Description changed: - This option leads to various issues, see the upstream discussion on + This option leads to various issues, see the upstream discussion on https://github.com/ivmai/bdwgc/issues/321 Steps to reproduction are given there. We ran into it in Sagemath, see https://trac.sagemath.org/ticket/30629 - Basically, ecl built with this libgc is broken. + Basically, ecl built with this libgc on WSL is broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897371 Title: don't ship libgc with -Wl,-Bsymbolic-functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgc/+bug/1897371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897371] [NEW] don't ship libgc with -Wl,-Bsymbolic-functions
Public bug reported: This option leads to various issues, see the upstream discussion on https://github.com/ivmai/bdwgc/issues/321 Steps to reproduction are given there. We ran into it in Sagemath, see https://trac.sagemath.org/ticket/30629 Basically, ecl built with this libgc is broken. ** Affects: libgc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897371 Title: don't ship libgc with -Wl,-Bsymbolic-functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgc/+bug/1897371/+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 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 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 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 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 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 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 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 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)
-- 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
Re: [Bug 1861062] Re: Ubuntu installer crashes
Thank you for your response. On Tue, Jan 28, 2020 at 1:05 AM Chris Guiver <1861...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this issue and helping to make > Ubuntu better. > > This package failure looks like it was caused by bad ISO download, > corrupted install media, or device failure. eg. look in the logs and > you'll see messages like these :- > > Jan 28 05:17:10 ubuntu kernel: [ 1666.240508] SQUASHFS error: zlib > decompression failed, data probably corrupt > Jan 28 05:17:10 ubuntu kernel: [ 1666.240510] SQUASHFS error: > squashfs_read_data failed to read block 0x38a866 > > Examining the information you have given us, this does not appear to be > a useful bug report so I am closing it, as it appears to be a bad ISO or > faulty device (inc. bad write-to-device). If you believe I'm in error, > please leave a comment explaining why and change the status back to > 'New'. I suggest you verify your ISO download, and use the 'check disc > for defects' option to validate your media before install to ensure a > good download & write. > > Possibly useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to- > verify-ubuntu#0 > <https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#0> > and > https://help.ubuntu.com/community/Installation/CDIntegrityCheck (where > CD refers to your install media, be it CD, DVD, HDD, SSD, thumb-drive > etc) > > ** Changed in: ubiquity (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1861062 > > Title: > Ubuntu installer crashes > > Status in ubiquity package in Ubuntu: > Invalid > > Bug description: > Installer crashed after starting install > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Mon Jan 27 21:17:17 2020 > InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz > file=/cdrom/preseed/ubuntu.seed quiet splash --- > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861062/+subscriptions > -- Best, Dima -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861062 Title: Ubuntu installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861062] [NEW] Ubuntu installer crashes
Public bug reported: Installer crashed after starting install ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Mon Jan 27 21:17:17 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861062 Title: Ubuntu installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861062/+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
[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 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] [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 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 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 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
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 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
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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
I don't know how to add Xenial as affected. -- 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 user@user:~$ cat /proc/cmdline BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-57-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:~$ user@user:~$ uname -a Linux user 4.15.0-57-generic #63~lp1827884 SMP Mon Jul 29 15:10:18 UTC 2019 i686 i686 i686 GNU/Linux user@user:~$ -- 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
user@user:~$ cat /proc/cmdline BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-57-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:~$ user@user:~$ uname -a Linux user 4.15.0-57-generic #63~lp1827884 SMP Mon Jul 29 15:10:18 UTC 2019 i686 i686 i686 GNU/Linux user@user:~$ -- 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 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
I've tested https://kernel.ubuntu.com/~cking/lp1827884/4.15 on xenial. It works. ** 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 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've tested https://kernel.ubuntu.com/~cking/lp1827884/4.15 on xenial. It works. Xorg starts too. ** 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/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 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 Why this report is a duplicate of https://bugs.launchpad.net/bugs/1838115 ? That report is more recent than this one. -- 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 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 Juerg, I used xenial-hwe kernel (4.15). Kernel 4.4 works fine. -- 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 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
Anthony, I had that problem with fresh Lubuntu 16.04 on Toshiba Sattelite L300. I don't know why but after a while the problem disappeared. Try "sudo update-initramfs -ck all" and removing of "quiet" option from /etc/default/grub (and then "sudo update-grub"). And if "nopti" option doesn't help I think you should make a separate bug report. -- 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 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
I can test it on xenial. Is the fix released in xenial proposed? -- 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 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
It flooded 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. (I just copied this message from #1827725) -- 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 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725 -- 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 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
[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 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)
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)
** 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)
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 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 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 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)
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)
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)
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 1789139] Re: dizzy doesn't start (bionic)
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623 ** Also affects: libopengl-perl (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #918623 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918623 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789139 Title: dizzy doesn't start (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dizzy/+bug/1789139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832808] [NEW] The game doesn't start
Public bug reported: Java console + SYSTEM PROPERTIES + Memory + THREAD DUMP outputs: triplea.engine.version.bin:1.9java.lang.NullPointerException at org.pushingpixels.substance.internal.utils.SubstanceColorUtilities.getDefaultBackgroundColor(SubstanceColorUtilities.java:759) at org.pushingpixels.substance.internal.utils.SubstanceColorUtilities.getBackgroundFillColor(SubstanceColorUtilities.java:661) at org.pushingpixels.substance.internal.ui.SubstancePanelUI.__org__pushingpixels__substance__internal__ui__SubstancePanelUI__installDefaults(SubstancePanelUI.java:74) at org.pushingpixels.substance.internal.ui.SubstancePanelUI.installDefaults(SubstancePanelUI.java) at java.desktop/javax.swing.plaf.basic.BasicPanelUI.installUI(BasicPanelUI.java:62) at org.pushingpixels.substance.internal.ui.SubstancePanelUI.__org__pushingpixels__substance__internal__ui__SubstancePanelUI__installUI(SubstancePanelUI.java) at org.pushingpixels.substance.internal.ui.SubstancePanelUI.installUI(SubstancePanelUI.java) at java.desktop/javax.swing.JComponent.setUI(JComponent.java:685) at java.desktop/javax.swing.JPanel.setUI(JPanel.java:150) at java.desktop/javax.swing.JPanel.updateUI(JPanel.java:126) at java.desktop/javax.swing.JPanel.(JPanel.java:86) at java.desktop/javax.swing.JPanel.(JPanel.java:109) at java.desktop/javax.swing.JPanel.(JPanel.java:117) at games.strategy.engine.framework.startup.ui.SetupPanel.(SetupPanel.java:25) at games.strategy.engine.framework.startup.ui.MetaSetupPanel.(MetaSetupPanel.java:45) at games.strategy.engine.framework.startup.mc.SetupPanelModel.showSelectType(SetupPanelModel.java:33) at games.strategy.engine.framework.GameRunner.lambda$main$0(GameRunner.java:159) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) java.lang.NullPointerException at games.strategy.engine.framework.GameRunner.lambda$showMainFrame$4(GameRunner.java:255) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740) at games.strategy.engine.framework.GameRunner$1.dispatchEvent(GameRunner.java:330) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) java.lang.NullPointerException at games.strategy.engine.framework.GameRunner.lambda$showMainFrame$4(GameRunner.java:255) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at
[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)
*** This bug is a duplicate of bug 1827884 *** https://bugs.launchpad.net/bugs/1827884 Yes, nopti helps. Thank you. ** This bug has been marked a duplicate of bug 1827884 Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/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 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)
And it's Toshiba Satellite L300-11Q laptop -- 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 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] 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] 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] 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] 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 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 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 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)
** 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 (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 (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] [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 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
