I've reinstalled a fresh copy of 24.04 with extras enabled and
recommended proprietary software installed, and I recorded a set of
observations on a fresh system. I recorded journal logs and other stats
in a similar format.
I think I may have identified a culprit. The crash appears to only occur
I've updated my bios, but the issue seems to persist. It's still
inconsistent. Sometimes it un-blanks without issue, sometimes I get the
gray-screen-of-death, and sometimes it unblanks directly to the login
page without a GSOD.
I'll try any other debugging suggestions, including a OS-reinstall.
Oh boy, so I've spent the past two days recording observations on this
issue, and I see no clear patterns at all. I've created a zipfile with a
text document called update.txt which contains my actions and
observations.
The basic pattern is: I do stuff, wait for the screen blank, un-blank
and see
I made an interesting observation. If I unplug all bug one monitor (I
have been using 3 in tests up until now), the crash does not occur in
X11. I have not tried wayland yet.
I'm going to plug in a second monitor to check if it happens with 2, and
then verify that it still occurs with 3.
--
You
Here is prevboot.txt
Is my whoopsie-id something that should be kept private? I do have files
in /var/crash that have timestamps from yesterday and today, but they do
not seem to appear under https://errors.ubuntu.com/user/ even after
I ran `ubuntu-bug `
** Attachment added: "prevboot.txt"
I have noticed that it will happen in the wrong place and then go away
from time to time. That bothers me a lot less than when it persists and
obscures something I want to look at. I have no idea how to replicate it
yet.
--
You received this bug notification because you are a member of Ubuntu
Update: I don't know what changed, (I did do an apt upgrade), but now
the crash is happening for Wayland too whenever the screen powers off.
It's very frustrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm not sure if this is the same exact bug, my problem just seems to
happen randomly not when necessarily when I close something, I'm still
trying to identify a reproducible cause. My problem seems more similar
to https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
Is there a resource you could point me to where I can learn what the
security risks of public .crash files are? I'm interested to know what
sensitive information could be contained in them.
Interesting that the whoopsie-id seems to persist across OS installs, or maybe
it's tied to my Ubuntu One
I did have another "random" crash in the middle of a session. I was
moving a window around. So it's not rela.ted to the main reason for this
bug report, but I figure its relevant enough to attach the journalctl
logs
** Attachment added: "wayland_crash_journalctl.log"
On the matrix chat Nils mentioned that "im on nvidia 550 atm and on
wayland. i had some X11 crashes in the past and wayland does a much
better job so far"
So, I changed my session type to Wayland by logging out and using the
gear by my username to select wayland. Doing that seems to have an issue
Also attaching the results of `sudo journalctl --dmesg --priority
warning > journalctl_dmsg_warnings.log` it does seem to have some nvidia
errors and tracebacks. It doesn't mean much to me, but perhaps it has
useful information in it.
** Attachment added: "journalctl_dmsg_warnings.log"
I'm also experiencing intermittent crashes of the window manager -
either gnome-shell or gdm3, not 100% sure. What I am sure of is that I'm
getting forcibly logged out.
I just experienced a crash when discussion this issue in matrix chat.
There were a few things going on at the time. I did have
Public bug reported:
I've written an AskUbuntu question about this:
https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring-
on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075
Originally I thought it was gnome not respecting my setting to prevent
locking the screen after
I've confirmed it does happen when just using super+arrow and no mouse
interaction. I still cannot get it to work reliably though.
My monitor setup looks roughly like this:
```
+--+
|2 | +--+
| | |1 |
+--+ | |
+--+ | |
|3 | |
I was able to get a screenshot of the issue. I edited the images to
remove sensitive information I was working with at the time, but the
point is that I was moving around windows (I forget if I was using
super+arrow or dragging to corners), and the issue happened. I'm still
not sure exactly how to
Public bug reported:
I've got a fresh install of the first 24.04 release, and I'm seeing
strange behavior related to super+arrow keys and the enhanced tiling.
I've disabled tiling popups and tiling groups, but I like the quad
blocks.
The issue is when I'm moving around windows, sometimes the
Thanks all for the details. Assuming it is safe to be removed and that
the new conflict in -proposed will help to do so automatically for users
that upgrade, once mainlined.
apt autoremove python3-distutils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm the behaviour after a recent upgrade from mantic to noble
and has also been reported in https://discourse.ubuntu.com/t/noble-dev-
branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt-
install-work-but-apt-upgrade-fail/43979
Another oddity is, that I seem to have to
Public bug reported:
After upgrading mantic to noble, there are multiple SSH agents who are
independently trying to set SSH_AUTH_SOCK, none of which is successful.
1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to
/etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified)
This
Public bug reported:
After upgrading to noble, there appears to be a regression between the
to-be-installed python3-distutils package and its dependency
python3-lib2to3. The old packages from mantic remain installed.
python3-distutils
Depends on: python3-lib2to3 (= 3.12.2-3ubuntu1.1)
This bug still exists on Ubuntu 23.10. HP Elitebook 840 G1.
inxi -Fxz
System:
Kernel: 6.5.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
v: 45.2 Distro: Ubuntu 23.10 (Mantic Minotaur)
Machine:
Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G1
v:
The SMB1 code should be entirely removed from the stack. It’s insecure and
deprecated everywhere.
On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net>
wrote:
> Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
> fixed? This is now over 4 years old.
>
> --
>
Yes, I can second the notion that this seems independent from the two
proposed upstream issues, since this has also happened here when
upgrading to 22.04.
$ sudo cat /etc/default/keyboard
XKBLAYOUT="de,us"
XKBVARIANT=","
BACKSPACE="guess"
XKBMODEL="pc105"
Removal of the package 'sabily-gdm-themes' and rebooting had no effect
on my situation.
Daniel, perhaps you have some insight into this. What information I've found
in my internet search says that gdm/gdm3 defaults to Adwaita icon theme. I'm
looked for "how to configure" type articles
about
** Attachment added: "login screen WITH Adwaita/cursors"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588894/+files/login-screen-with-Adwaita-cursors.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "login screen without Adwaita/cursors"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588893/+files/login-screen-without-Adwaita-cursors.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "list of installed packages"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588892/+files/minis-packages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972080
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and
rebooting had no effect on the issue. White square "mouse pointer" is
present on gdm login screen if /usr/share/icons/adwaita/cursors is
missing (renamed).
If instead I install a symbolic link .../Adwaita/cursors ->
The reported problem is during login, not after successful login.
I don't think mutter configuration has any effect before graphical login.
Ubuntu's cursor theme may come from 'yaru-theme-icon', but does gdm's?
Two files affect the observed condition:
/usr/share/icons/Adwaita/cursors/left_ptr
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5587825/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972080
Title:
gdm has
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5587826/+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/1972080
Title:
gdm has
I tried Fedora 35, and found the exact same behaviour (ie the boot
program recognises the keyboard, but the final linux image does not).
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Jon Tha
* log2 (180) hours, ie about 4 hours.
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Daniel van Vugt" <1930...@bugs.launchpad.net>
To: j...@pobox.com
Sent: 22/04/2022 03:00:03
Subject:
year, there will be no Ubuntu (or Debian I think,
given that Rapsbian doesn't work with the KVM either) distribution I can
use, as at that point 18.04 will be end of support. I shall then start
having to try and learn other distros to see if any of them have
fixed/failed to create this bug.
Jon
Public bug reported:
goverlay does not display its window and immediately exits, with the
following error if run from terminal:
can't get libdl.so
Tested on jammy beta, up to date as of 2022-04-20 1500 UTC.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: goverlay 0.7.1-2
From libvirt gitlib...
Daniel P. Berrangé @berrange · 2 months ago
Owner
The QEMU patches required to solve this are here
https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg03279.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8
Still having this problem. Very surprised it has lasted this long. In
any case, if it is fixed, will this change make it to the next LTS
update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I don't really know what happened.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
I am also adding the output from boltctl, if you need any other info
please advise.
** Attachment added: "Boltctl output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540412/+files/boltctl.txt
--
You received this bug notification because you are a member of
Adding dmesg output from computer
** Attachment added: "Output from dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540411/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have a Lenovo Thunderbolt 3 Gen 2 dock and wanted to use this with
Ubuntu 21.10. When booting an unmodified version the usb ports do not
work. After an inspection with journalctl I find the error message "No
bus number available for hot-added bridge" and a google search led
Public bug reported:
Doing a dist-upgrade from 18.04 to 20.04:
Errors were encountered while processing:
ubuntu-advantage-tools
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error
code (1)
*** Send problem report to the developers?
After the problem report has
Confirmed! Finally. With the latest HWE:
$ apt show linux-image-5.11.0-37-generic
Package: linux-image-5.11.0-37-generic
Version: 5.11.0-37.41~20.04.2
...
No errors or warnings in dmesg or journalctl -b seen on my statem
anymore.
Motherboard: ASUS PRIME X570-PRO (latest BIOS v 4021)
CPU: Ryzen
Confirmed. Just updated and same.
Can you backport the fix to the 20.04 HWE kernel? I mean that's the one
Canonical recommends has as first choice if downloading Ubuntu from
ubuntu.com, for years now. And they've become more stable in my
experience than the ones between LTS versions, which is
And will that kernel come to the Ubuntu 20.04 LTS HWE stack, say in
20.04.4? Kinda need to use LTS versions, us that need that stability at
least.
Not really interested in fixes for 21.10 or something... Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
To be clear this issue started with Kernel 5.8.0-63 NOT 5.11 (on Focal /
20.04 HWE LTS)
Well Ubuntu Kernel Bot, that's exactly what I did in comment #14
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/comments/14
Latest 5.13 kernel in -prosed on Focal (20.04.3) gets the same gpio
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg after update of
Added tag 'verification-failed-hirsute'. Enabled proposed and installed
package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4'
on my 20.04.3 LTS, and still get in dmesg:
[1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
[1.228732]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929504
Title:
Add support for IO functions of AAEON devices
To manage notifications about this bug go to:
Hi,
The latest file shows as follows:
```
try:
fcntl.ioctl(sock, SIOCETHTOOL, packed) # Status ioctl() call
if _PY3:
res = status_cmd.tobytes()
else:
res = status_cmd.tostring()
speed, duplex = struct.unpack("12xHB28x", res)
```
OK, but don't try to load the gpio-aaeon module on PCs that, if simply
one tries to load it manually, it simply says that no such device
exists... It shows twice in the boot log (dmesg + journalctl -b) but
even worse also on the monitors, although GRUB has "quiet" specified (no
splash).
Worst of
Well OK there is a module with that name, however I did blacklist it and
same error still occurs. It happens very early in the boot process. Now
maybe it tries to load gpio-aaeon, but still early to load modules I
would say, it's still doing say GRUB kernel parameters like fsck ones.
Now I have
Same on Ubuntu 20.04 both GA and HWE kernel.
Sure, it just takes this command to find which package has it:
$ apt-file search libbd_mdraid.so.2
And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it.
Depends on packages I don't need, MOST don't need:
$ apt show
No, I can't, because there isn't a single module loaded with even the
name "gpio" in it.
So running: $ lsmod|grep gpio == No result
It's in the kernel, not a module. I reverted to the GA kernel and
although with that I've had some issue with on headless *Intel* NUC
running Virtual Machines that
EDIT: To clarify both times these lines come they refer to "gpiochip1"
(so not 2 different ones).
I started getting the same 3 lines of errors TWICE at boot, with the now
latest official 5.8 HWE kernel. Without "splash", just "quiet" set for
GRUB it also shows on my monitors when booting.
Public bug reported:
After running a fresh installation the app crashed.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon
Same problem too with Radeon RX 5500 XT. It worked on my Radeon RX 570
(AMD X570 + Ryzen 3950X). Using the generic ICD and Mesa OpenCL doesn't
work.
The easy fix that also gives better results on all benchmarks I've done
for Vulkan and OpenGL is installing the latest AMDGPU Pro driver
(version
Did some more testing:
- Issue does not happen when launching frescobaldi with sudo, but the setting
does not apply to normal user
- Issue does not happen in GNOME (tested with Ubuntu 21.04)
- workaround: add line to ~/.config/frescobaldi/frescobaldi.conf in the
[lilypond_settings] section-
Public bug reported:
I'm on Ubuntu Studio 21.04 with KDE Plasma 5.21.4 and Frescobaldi 3.1.3
from the repos.
When I go to the Preferences, under Lilypond Preferences, I tried to add
a folder to the include path. When I click Add, the dialog seems to be
looking for a file rather than a folder.
Public bug reported:
The most recent version of this program is 3.6.2 and contains
significant improvements in engraving, including new fonts.
https://musescore.org/en/node/317195
** Affects: musescore3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
buntu.com/ubuntu bionic/universe
amd64 Packages
2.5.3+dfsg-2.1build1 -1
100 /var/lib/dpkg/status
```
This error seems identical to an error reported for Debian Sid in 2018 (see
link below).
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909558
Best,
Jon Green
** Affects: shibbo
I don't have a "Unifying receiver". That's just the name which appears
and/or disappears when I plug in the KVM to the PC. The KVM in all cases
is directly connected to the keyboard/mouse/screen at one end, and USB
ports/HDMI at the PC end.
-- Original Message --
From: "Hui Wang"
Installed RAM16.0 GB
Device ID86452CEC-D6C1-46A6-9970-7FE2338F4B02
Product ID00326-1-0-AA334
System type64-bit operating system, x64-based processor
Pen and touchNo pen or touch input is available for this display
Here's the motherboard info
C:\Users\Jon>wmic basebo
Confirmed everything appears to be working. We can consider this closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930640
Title:
Error when using S3 multipart upload - TypeError: cannot use a
After a little more digging, I believe part of my issue with the
boto3+s3 option was that I was still using the full URL rather than just
the bucket name, so rather than:
boto3+s3://BUCKET_NAME/folder
I was still using:
boto3+s3://s3-us-west-2.amazonaws.com/BUCKET_NAME/folder
So this appears
No funny characters in the bucket name.
It's literally just alpha characters and dashes: labkey-artifactory-
backup
And the folder it drops into uses an underscore: artifactory_backup
I'll recheck that link. There were a few that I already saw, but were not
applicable to my situation.
--
I've tried using boto3+s3:// as well before and it was unsuccessful.
Swapping it out with this newer version of duplicity produced an error
regarding the HeadBucket operation.
See new failure below. I turned up the verbosity to 9 for this one.
Note: My company is using Duplicity 0.8.11 and Duply
Public bug reported:
I have recently acquired a acquired a desktop running ubuntu 20.04. I
have several computers and switch between them using this KVM
https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8=1
The other machines are either running windows or
Unfortunately, the same issue is coming up, even after installing the
requirements via pip.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/duplicity/backends/_boto_multi.py", line
223, in _upload
mp.upload_part_from_file(fd, offset + 1, cb=_upload_callback,
File
I ran into the same issue, but upgrading to 0.8.19 didn't fix it.
I've put in a new bug for this:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930640
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I followed the solution in
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was
running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19,
the problem still persists for me when trying to use S3 multipart
uploads.
Note: This problem doesn't
Public bug reported:
>From a fresh installation of qmail I find
jon@frobenius:/etc/qmail/qmail-send$ ls -l supervise
lrwxrwxrwx 1 root root 29 May 21 20:17 supervise ->
/var/lib/supervise/qmail-send
jon@frobenius:/etc/qmail/qmail-send$ ls -l /var/lib/qmail/supervise/
total 12
lrwxrwxrwx
Public bug reported:
Multiple identities can be used for authentication:
1. user,,, (user)
2. Jon Thackray,,, (jon)
Choose identity to authenticate as (1-2): 2
Password:
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
AUTHENTICATION FAILED ===
Error executing
Public bug reported:
crashed on upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
Public bug reported:
Disk Usage Analyzer no longer works at all; becomes unresponsive several
seconds after starting
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: baobab 3.34.0-1
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
** Description changed:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 344mm x 194mm
-1920x1080 59.93*+ 39.99
-1680x1050 59.93
-1280x1024 59.93
-
Public bug reported:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
344mm x 194mm
1920x1080 59.93*+ 39.99
1680x1050 59.93
1280x1024 59.93
1440x900
Same issue for me as I'd like general notifications just not routed to
Gnome via the Evolution popup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805666
Title:
Evolution Alarm Notify continues
Public bug reported:
Using Ubuntu 18.04. Got prompted to upgrade to 20.04 again today. Tried
before but never works. Today I got the following info on screen.
Could not install 'oracle-java11-installer-local'
The upgrade will continue but the 'oracle-java11-installer-local' package may
not be
I can deterministically reproduce this crash with Wireguard on the RPI3
running 20.10 and hence using the lan78xx driver on eth0. A few minutes
of browsing public web sites on a client connected through Wireguard to
the RPI3 crashes the RPI. Changing nothing except for running
Wireguard's
@Quinn - Same problem, since you say its a different bug I went ahead
and opened one with the dist-upgrade log:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1907652
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
PostGIS and PGRouting are in the removal blacklist, making it hard to
upgrade from 18.04 LTS to 20.04 LTS
dist-upgrade main.log:
2020-12-10 11:51:35,686 DEBUG blacklist expr '^postgresql-.*[0-9]\.[0-9].*'
matches 'postgresql-10-postgis-2.4'
2020-12-10 11:51:35,686 DEBUG
'journalctl -b -1' comes back with:
Specifying boot ID has no effect, no persistent journal was found
I'm assuming though you're after the boot log for the previous session
(that froze) so I've manually extracted this from /var/log/syslog in the
attached archive (prevboot.txt).
Unfortunately
same fail. literally last10 seconds fail error message. dual boot installation
on two nvme drives
Acer Nitro5 AN5-15-55 pls help ,, is there a workaround? I been using Ubuntu
last 8 yrs cant live without it. I triede 20.04 and 20.10 with install thrid
party drivers elected and install updates
I have managed to upload the crash report via another machine, the ID is
1904626. For some reason it appears to be associated with bash which
makes me wonder if it is related - the timestamp is roughly 6 minutes
after restarting the machine from the freeze which puts it in the right
time frame but
There is one crash report in the /var/crash folder which corresponds to
the last time the system restarted due to this issue (other instances
are >7 days so will have been removed). Running ubuntu-bug as requested
generated a lot of dots but did not provide a bug ID:
jon@monolith:/var/cr
Public bug reported:
After performing a recent update, I am encountering a complete system
freeze shortly after logging on to a graphical session but only for a
single user (which may suggest a corrupted configuration file
somewhere). This is repeatable - happens every time I attempt to login.
Running Chromium Version 86.0.4240.111 (Official Build) snap (64-bit) on
Ubuntu 20.04 and I'm not seeing my policies enforced inside Chromium.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714244
I installed a Bionic VM with the minimal .iso. Followed my steps to
reproduce this fault and got the error in my browser. I then properly
read Brian's instructions on how to use "proposed" and now get the
Icinga web 2 setup wizard in my browser.
I'll keep the VM around for a few weeks if you
I have encountered this issue trying a fresh install of Kubuntu 20.04.1.
The entire reason that I tried a fresh install is that trying to upgrade
my existing system from Ubuntu Mate 18.04 to 20.04 resulted in the
upgrade finishing with errors and leaving my system in an unusable state
** Attachment added: "The attachment for my comment above does not seem to have
taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04
installation"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog
--
You received this bug
Public bug reported:
Ubuntu 18.04.5
iproute2 4.15.0-2ubuntu1.2
iproute2-doc 4.15.0-2ubuntu1.2
Most of the subcommands for /sbin/ip are documented in a manpage with a name of
the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at
"ip-address(8)".
However, ip tuntap seems to
How is it not a bug when the kernel fails to boot when you use the
default setting?
There is a workaround for this problem which is to limit memory, but
there is still a crash. The Raspbian kernel doesn't crash -- it works.
That would suggest there is a problem here.
JW
-Original
Still doesn't work for me after all updates，and there are side
effects... Now every time I boot up, the Desktop's font is very small,
even there is no external monitor...if ALT + F2 -> R, then restore :(
libmutter-6-0:
Installed: 3.36.4-0ubuntu0.20.04.2
Candidate: 3.36.4-0ubuntu0.20.04.2
Changing the status of this bug from 'expired' to 'confirmed', since all
the way up here in Ubuntu 20 land (in 2020), I have found this bug when
development testing my research OS. Random lockups and segfaults, after
which the CPU usage of the qemu-system-x86 process sticks at over 100%.
**
We completed a test this morning with the modified pigpio library and
verified our applications can now read the GPIO signals once we removed
the PROT_EXEC flags from the library init code.
We will pursue getting a change in with the pigpio library separately.
--
You received this bug
We are going to try editing the pigpio library and rebuilding it and
seeing if it works. There doesn't appear to be a clear requirement for
pigpio to rely on PROT_EXEC and it has been removed in the past.
Conversation about this is happening here:
https://github.com/joan2937/pigpio/issues/375
Qt responded and thinks cma-128 will work for our application.
I modified our Pi test unit to use the original Ubuntu 20.04 .dtbo file
and booted successfully when I used the dtoverlay=vc4-kms-v3d,cma-64
setting.
I will test our UI with this configuration early next week.
--
You received this
Will those changes be merged into the 20.04.1 release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736
Title:
[nvidia] Screen scaling 125% gives 200%
To manage notifications about this bug
1 - 100 of 4159 matches
Mail list logo
