Public bug reported:
Getting many messages like this in my dmesg:
[207441.489056] systemd-journald[1439]: Data hash table of
/run/log/journal/de5de074689f427db9c98ca2ef0070f0/system.journal has a fill
level at 75.0 (82165 of 109553 items, 41943040 file size, 510 bytes per hash
table item), sug
The Diagnostics option showed as "Automatic"... and then showed "Never"!
I flipped it to automatic, and now I see this:
systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
Loaded: loaded (/lib/systemd/system/whoopsie.path; enabled; pres
ls /var/crash/
_opt_Signal_signal-desktop.1000.crash _usr_bin_gnome-shell.1000.crash
_usr_bin_gnome-shell.1000.uploaded _usr_libexec_goa-daemon.1000.upload
_opt_Signal_signal-desktop.1000.upload _usr_bin_gnome-shell.1000.upload
_usr_libexec_goa-daemon.1000.crash _usr_libexec_goa-daemon.10
satadru@mbp113 ~$ sudo systemctl status apport-autoreport.service
× apport-autoreport.service - Process error reports when automatic reporting is
enabled
Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
Active: failed (Result: exit-code) since Mon 2022-09-12 09:22:
satadru@mbp113 ~$ systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
Loaded: loaded (/lib/systemd/system/whoopsie.path; disabled; preset:
enabled)
Active: active (waiting) since Mon 2022-09-12 09:22:59 EDT; 4min 35s ago
Until
Public bug reported:
This is what the service reports. Aside from crash reports no longer
uploading automatically, I'm having trouble pointing ubuntu-bug to crash
reports in /var/crash - a window opens, but then a browser never opens.
ubuntu-bug program-name does open the browser though.
× apport
@vorlon it is in the graphic which shows up in the GUI surrounding the checkbox
to enable -proposed
here:
https://wiki.ubuntu.com/Testing/EnableProposed?action=AttachFile&do=get&target=devoptions_1604.png
Thank you @knox for the clarification. This was largely my fault for doing a
's/focal/gro
Fully aware that proposed is not supported, and that this may cause
instability.
Just trying to be helpful as per
https://wiki.ubuntu.com/Testing/EnableProposed
"Proposed updates are only for testing updates and providing development
feedback. Enabling this may introduce instability."
This bug r
This problem went away once I stopped using groovy-proposed and
(painfully) removed libffi8ubuntu1 and all dependencies which used it.
** Also affects: libffi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- gnome-shell crashing with Wayland
+ gnome-shell crashing (libf
Any resolution on this? Has anyone contacted people who work on util-
linux?
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubunt
I'm not sure which package to file a bug report on, but I have multiple
pools, and after this last update, bpool wouldn't mount properly due to
files on /boot, and as a result update-grub updated grub.cfg with no
info about my kernels. :/
--
You received this bug notification because you are a me
Here is the wpa supplicant log, gathered as per:
https://gist.github.com/wch/8305204#gistcomment-2477237
https://paste.ubuntu.com/p/Nm7G6STc22/
Note there are 3 sections.
The first section starts with "wpa_supplicant v2.6"
When I upgrade to 2.9 you can see this start with "wpa_supplicant v2.9"
Wh
** Description changed:
Running on arm64 eoan build with kernel from raspberry pi folks (
4.19.71-v8-g6de367fd7 ) on a rpi4.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
-
- With wpasupplicant 2.29, wifi comes up on boot, but then drops
Public bug reported:
Running on arm64 eoan build with kernel from raspberry pi folks (
4.19.71-v8-g6de367fd7 ) on a rpi4.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
With wpasupplicant 2.29, wifi comes up on boot, but then drops out shortly
the
14 matches
Mail list logo
