This is not fixed. What we have is a reliable workaround to a bug which
apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session
package installed.
Flatpak packages provided by the PPA at
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak (and possibly
others) indirectly
I'm on Ubuntu 16.04.3 with mainline kernel
Linux version 4.13.2-041302-generic (kernel@tangerine) (gcc version
7.2.0 (Ubuntu 7.2.0-3ubuntu1)) #201709132057 SMP Thu Sep 14 00:59:32 UTC
2017
and mesa 1:17.3~git170914191100.7ffd4d2~x~padoka0 and X from the Padoka
PPA.
OpenGL renderer string:
The file I'm testing with has a "H264 - MPEG-4 AVC (part 10) (avc1)"
video track.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1574354
Title:
playing .mp4 in VLC freezes
** Tags removed: patch
** Tags added: trusty
** Changed in: libvirt (Ubuntu)
Assignee: ali salama (alisalama) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
This is apparently a bug, more precisely a regression (#8) in either Ubuntu's
accountservice or lightdm.
This also affects trusty (as I have tested), so adding tag.
There is no patch, yet, removing tag (set in #21), renaming image in #21.
~alisalama has not handled this bug since April, I assume
** Summary changed:
- No network connectivity after upgrade from 16.04 to 16.10
+ No network connectivity (NIC unmanaged) after upgrade
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I observe what is likely the same problem on XUbuntu 16.04.5, running
these commands in xfce4-terminal:
user1@mysystem:~$ lsb_release -ds;cat /proc/version;echo $SHELL;groups;groups
$(whoami)
Ubuntu 16.04.5 LTS
Linux version 4.15.0-29-generic (buildd@lcy01-amd64-024) (gcc version 5.4.0
20160609
TJ is right, I also confirmed this issue on a freshly installed 18.04.1
x86_64 Desktop VM last night. After enabling 'proposed' and installing
all pending updates, 'groups' in a terminal returned just the users
primary group. I then restored a snapshot taken right after the 18.04
installation (but
Public bug reported:
Pointing ubuntu-bug to a non-existing X window makes apport-gtk
segfault:
myrestricteduser@ubuntu1804amd64~$ DISPLAY=:1 ubuntu-bug ubiquity
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Segmentation
$ journalctl --list-boots 2>/dev/null | head -n1 && journalctl --disk-usage
2>/dev/null
-37 64975ef449c34cdc828feb0197d7a2f5 Mon 2018-09-10 02:00:47 CEST—Mon
2018-09-10 08:05:57 CEST
Archived and active journals take up 1.8G in the file system.
My interpretation is my systems' situation is that
It is yet unclear what the root cause of this issue is - libpam, crypt,
passwd and sudo seem like primary suspects. The 256 character password
is hashed to a value which still allows a TTY login to succeed. Also,
passwd run by a different user in the context of the affected user
(using sudo) still
So I wasn't aware of this size hard limit on persistent storage - I just
noticed that it is 'already' allocating 1.8GB, but this is indeed less
than the 10% of the file system the man page says it will consume. So
from my personal point of view this is a non-issue then (ideally
Benjamin will also
Not breached here:
$ journalctl -b -u systemd-journald.service -n 1
-- Logs begin at Sat 2018-09-29 05:03:28 CEST, end at Thu 2019-03-21 18:18:38
CET. --
Mar 20 13:32:03 debby2017 systemd-journald[699]: System journal
(/var/log/journal/f8b692c8bb791fe2804f3d5a5905148b) is 1.8G, max 1.8G, 0B
Thanks for your report. I'm not a developer, just having a quick glance
on your logs:
Your system log shows I/O errors on /dev/sdb, a 1.00 TB storage. This
can be due to bad cabling / connectors or due to a bad disk.
Additionally, the USB connection to the WD My Passport 25E1 drive was
reset
Dear Adam,
the log you provided does not seem to indicate an issue with acquiring
data from http://ppa.launchpad.net/jtaylor/keepass/ubuntu but from
http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu - a PPA which does
not support your Ubuntu release (18.04 / bionic).
So this appears to not be
Public bug reported:
There are some situations where it is desirable to gather debugging
information on a system affected by a bug, but to login (to
Launchpad/Ubuntu SSO) and complete editing this bug report from a
different system.
This is already implemented for situations where the affected
Thanks for explaning that it is possible to create a bug report on one
system, then manually copy it to another computer where the bug report
can then be submitted using ubuntu-bug.
This is not exactly as convenient as being able to run apport on one
system to gather debugging info, submit this
I do not know how priorities in bug handling are set, but I do wonder
what may be the reason to not handle this rather common (30 dupes)
critical (crash) bug on a 'main' package for the past three years -
could someone explain this to me? Thanks in advance.
--
You received this bug notification
*** This bug is a duplicate of bug 1832801 ***
https://bugs.launchpad.net/bugs/1832801
** This bug has been marked a duplicate of bug 1832801
disco: curl error while loading shared libraries: libssl.so.1.0.0
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
fstrim.timer always triggers at 00:00:
$ systemctl list-timers fstrim.timer
NEXT LEFTLAST PASSED
UNIT ACTIVATES
Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days
ago
** Summary changed:
- High memory usage by Xorg.
+ High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
On Ubuntu 19.04 (amd64):
Removing fonts-liberation2 (2.00.5-1) ...
dpkg: warning: while removing fonts-liberation2, directory
'/usr/share/fonts/truetype/liberation2' not empty so not removed
Removing fonts-opensymbol (2:102.10+LibO6.2.2-0ubuntu2) ...
dpkg: warning: while
This command was reported to successfully work around this bug:
sudo sed -i 's/^Automatically/# Automatically/g' /var/lib/dpkg/info
/base-files.postinst
It changes any lines starting with "Automatically" into comments, which
lets the script finish properly when you run:
sudo dpkg
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835095
Title:
Lubuntu initrd images leaking
Hi.
I am just a fellow Ubuntu user, but I am afraid this bug report is most
likely not something anyone could solve, because so many different
chipsets and issues are being discussed here (I assume this is also why
no developers felt inclined to touch it so far).
I very much recommend that
This issue seems to have occurred to me today (and several times
previously) - when I returned to my computer after a while (the screen
had entered power saving mode), the gnome-shell process (on XWayland)
failed.
Neither after logging in to gnome-shell / Xwayland nor after logging out
and back
** Changed in: gnome-terminal
Importance: Medium => Unknown
** Changed in: gnome-terminal
Status: Confirmed => Unknown
** Changed in: gnome-terminal
Remote watch: GNOME Bug Tracker #780622 => bugzilla.gnome.org/ #780622
--
You received this bug notification because you are a member
Is this something which could be supported by now?
gnome-control-center -> power seems to offer a setting to manage wi-fi
power saving but in the end this is just a wi-fi on/off switch which
immediately brings the device down/up (bug 1751954).
Looking through the details of an existing NM
** Attachment added: ""journalctl -b -1" (failed boot) for other user"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848900/+attachment/5298524/+files/jj9k.log
** Summary changed:
- blank display with Eoan Ermine live DVD on Rysen 2200G
+ Blank display with Eoan Ermine live DVD on
I was supporting another Xubuntu 19.10 user on AMD Ryzen 3 2200G
(Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F2
08/08/2018) today, whose log of a failed (standard) boot (to black
screen) showed
kernel: WARNING: CPU: 2 PID: 255 at
Possibly related? https://bugzilla.kernel.org/show_bug.cgi?id=204343
** Bug watch added: Linux Kernel Bug Tracker #204343
https://bugzilla.kernel.org/show_bug.cgi?id=204343
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
There is no easy way to gracefully handle weak crypto. It has been known
for more than five years that 1024 bit (or rather <2048 bit) DH primes
need to be considered weak and should not be used - https://weakdh.org/
- GnuTLS > 3.2 does the right thing in having services which still have
not taken
Relevant lines from DpkgTerminalLog.txt:
Setting up linux-firmware (1.187.3) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic
[..]
cp: cannot stat '/etc/ykluks.cfg': No such file or directory
E: /usr/share/initramfs-tools/hooks/yubikey-luks failed with return 1.
So, as has been previously stated here, and as is documented in section
5 of the journald.conf man page (install man-db, run 'man 5
journald.conf'), journald will, by default, limit the journals' disk
allocation to either a maximum of 10% of available disk space, or to the
absolute size of 4GB,
For gnome-control-center, this bug report was watching
https://bugzilla.gnome.org/show_bug.cgi?id=692666 so far. While still
relevant, the Gnome Project has stopped using this bug tracker and has
since shifted to their Gitlab instance for bug tracking.
A closely related upstream bug report, which
$ apport-unpack _usr_bin_gjs-console.1000.crash Guest79
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 74, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in
extract_keys
[item for item, element in
This can be a dupe of bug 1970066
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1993318
Title:
ZFS + Encryption installations of Ubuntu Desktop do not come up
Thanks to oerheks for pointing me to a related (though AMD there) report at
https://github.com/linux-surface/linux-surface/issues/839#issuecomment-1140287888
Placing the following in /etc/initramfs-tools/modules
#-- Starts here --
surface_hid_core
surface_hid
surface_aggregator_registry
With community support on Libera IRC's #ubuntu Andi and I were able to
determine the root cause of this issue was apparently a read-only /usr
file system (caused by a user-initiated system configuration change).
--
You received this bug notification because you are a member of Ubuntu
Touch
39 matches
Mail list logo
