# 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:
** 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
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
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:
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
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:
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 =
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
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
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
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:
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
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.
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
** 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
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
** 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
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.
**
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:
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
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
** 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
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
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
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.
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
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:
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]
** 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.
--
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:
d/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.launc
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
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
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"
** 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.
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.
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
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
*** 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
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.
*** 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
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
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
*** 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
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
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
*** 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
*** 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
*** 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.
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
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
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
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
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
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
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"
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,
** 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:
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.
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
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
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.
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
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
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
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
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)
*** 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
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
** 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
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
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:
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
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:
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
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
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.
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
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
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
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.
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:
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:
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
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.
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
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
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
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
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
** 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.
** 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.
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.
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:
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
$
I think you already have tried to take the fans by fancontrol. I thought
if fancontrol works on this laptop then you just need to add a service
to stop fancontrol service before suspend and start it again after
suspend after small delay.
--
You received this bug notification because you are a
Public bug reported:
The console output:
$ debsums -c > debsums.txt
debsums: Error: symlink loop detected in path
'usr/src/amdgpu-18.50-725072/Makefile'. Please file a bug again amdgpu-dkms.
$
The /usr/src is symlinked to /usr/share/.src.
'/usr/src/amdgpu-18.50-725072/Makefile' is not a
Is it possible to exclude this directory from debsums checking?
** Description changed:
The console output:
- $ debsums -c > debsums.txt
+ $ debsums -c > debsums.txt
debsums: Error: symlink loop detected in path
'usr/src/amdgpu-18.50-725072/Makefile'. Please file a bug again
And I have /home and /tmp mounted with noexec.
Does anyone know how to find ubuntu-devel-disc...@lists.ubuntu.com in
"Subscribe someone else"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824986
Public bug reported:
The console output:
$ twinkle
QApplication: invalid style override passed, ignoring it.
Language name: "en"
mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
*** stack smashing detected ***: terminated
Aborted (core dumped)
$
I've attached a strace
1 - 100 of 799 matches
Mail list logo
