Public bug reported:
Device: Minisforum u820 "nuc-like" minipc, 512GB Kingston SSD and 2x8GB
RAM. No dedicated GPU. Intel i5-8259 with built in 655 graphics.
This issue only appears on reboot, not when I turn the device off
(shutdown) and turn it back on 10sec later.
After installing Ubuntu Budg
Yes I did, on 5 different systems already, for each I found the ID in the
whoopsie file, the URL works with the ID. No report is shown.
This is not new. I posted it also here:
https://discourse.ubuntubudgie.org/t/unable-to-send-crash-report/5056
And was directed to a failure in whoopsie:
https:
Additional info: when I try ubuntu-bug or apport-cli with that crash
file, an empty 0 byte .upload file is created. No .uploaded file is
created (which would be expected).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoops
Public bug reported:
For every system I install Ubuntu Budgie 21.04 with BTRFS filesystem on,
I get a "Report a problem" popup. I do not notice a crash, but there is
a crash file: _usr_lib_xorg_Xorg.0.crash
I am unable to send this crash report in. I tried ubuntu-bug but also
apport-cli, nothing
I did that, as said, I do not get anything, just returns to $ and a 0
byte .upload file with the same name appears in /var/crash. I tried
multiple times.
I installed Ubuntu Budgie 21.04 after downloading the image and
verifying checksum, I installed it now on 5 different systems, each one
shows th
Thanks, i tried that, still nothing happens and nothing new appears in
https://errors.ubuntu.com/user/ID
But going through the info shown when I use ubuntu-bug, I can confirm this
crash on 2 different systems and it is about: "xorg crashed with sigabrt in
osabort()"
- The mentioned Intel C246
OK I can confirm:
1. The crash has nothing to do with this error message.
2. This error message is easy to reproduce as it happens on a clean install on
a Fujitsu D3644-B mobo with Intel C246 chipset and Realtek ALC671 audiochip. No
wifi or bluetooth.
offtopic:
regarding the crash, it is /va
Public bug reported:
Not sure if the bluez error is related, perhaps not (this is a desktop
without Wifi/Bluetooth).
jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service
'org.bluez': timed out (service_start_timeout=25000ms)
jun 01 12:46:30 Obelix pulseaudio[1749]: GetMa
I reported this today, didn't realise an extensive bug report already exists:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570
Lenovo S540-13ARE (AMD Ryzen 4800u).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
** Summary changed:
- After updating libasound2 and libasound2-data the only audio output device is
"Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop
Lenovo S540-13ARE.
+ libasound2 and libasound2-data update replaces all audio outputs with "Dummy
Output"
--
You r
Public bug reported:
After updating libasound2 and libasound2-data the only audio output
device is "Dummy Output". Rolling back to prev version solves it. AMD
Ryzen 4800u laptop Lenovo S540-13ARE.
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.
11 matches
Mail list logo
