Public bug reported:
[Impact]
NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-SERIAL
symlinks.
[Test Case]
On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
with the patch, it will contain link(s) named by the drive serial
number.
[Regression Potential]
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851164
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Public bug reported:
[Impact]
After including the patch from bug 1642903, NVMe devices that include spaces in
their model or serial strings result in incorrect symlinks, e.g. if the model
string is "XYZ Corp NVMe drive" then instead of creating:
/dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL
oken
operation.
[Other Info]
This needs fixing upstream, which I'm in progress on.
** Affects: systemd (Ubuntu)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in
** Also affects: systemd via
https://github.com/systemd/systemd/issues/6723
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1714505
: Medium
Assignee: Dan Streetman (ddstreet)
Status: Won't Fix
** Changed in: debian-installer-utils (Ubuntu Artful)
Status: New => Fix Released
** Changed in: debian-installer-utils (Ubuntu Zesty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: debian-ins
Hi Seyeong,
first, I commend you for going to the trouble of fixing tests in
lp1316970_trusty_glib2.0.debdiff, but I think those are unrelated to
this actual bug and so the patch is not required for this. I'll focus
only on the first patch.
In that patch, I did a quick review of the changes,
Seyeong, can you also clarify - are the glib2.0 patches also needed to
fix memory leaks?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1316970
Title:
g_dbus memory leak in lrmd
Seyeong, the debdiff patch is very large, and contains more than just
the 1-line memleak fix from the description...can you remove the extra
changes from the debdiff so it only contains the memleak patch? Or
explain why the other changes are needed?
** Tags added: sts-sponsor-ddstreet
--
You
glib2.0 memleak patch moved over to bug 1750741
** No longer affects: glib2.0 (Ubuntu)
** No longer affects: glib2.0 (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
Seyeong,
can you check this updated debdiff to verify it still fixes the mem
leak?
I reverted the free->g_free changes that I previously suggested, as you
were correct - the existing code uses chars and normal free() so we
should stick with that, i was wrong to suggest using g_free().
Also I
Seyeong,
+ - d/p/0001-GDBusProxy-Fix-a-memory-leak-during-
initialization.patch
this fixes a memory leak, but in later code than the Trusty glib2.0 code
+ - d/p/0001-tests-gdatetime-Use-a-real-rather-than-invented-
time.patch
this fixes an autopkgtest regression, that's unrelated to
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
** Also affects: glib2.0 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1750741
Title:
Memory leak in
Ok, in that case, can you open a separate lp bug for the glib2.0 memory
leak? I think it will be easier to track just fixing the pacemaker mem
leaks in this bug, and track fixing the glib2.0 mem leak in a separate
bug.
--
You received this bug notification because you are a member of Ubuntu
> so lets focus on pacemaker instead of glib2.0
sounds good - i will mark this as 'wont fix', but we can come back to it
if needed.
Also note, the existing bug 1545308 appears to be the same as this.
** Changed in: glib2.0 (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received
** Also affects: hwdata (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: gnome-desktop3 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: unity-settings-daemon (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in:
** Tags added: sts-sponsor sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal on login screen or when auto-login is
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu)
Status: New => Invalid
** Changed in: gdm3 (Ubuntu Bionic)
Status: New => Invalid
** Also affects: plymouth (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also
** Tags removed: sts-sponsor sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal on login screen or when auto-login is
> can you get it pushed out to eoan-updates (or revert it)?
sorry i meant eoan-release
also, see discussion in #ubuntu-devel, I'll revert this patch in my
upload to eoan, so that the regression can be figured out.
--
You received this bug notification because you are a member of Ubuntu
Desktop
@rbalint, this is still in eoan-proposed, can you get it pushed out to
eoan-updates (or revert it)?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on
This may have caused a regression upstream, see
https://github.com/systemd/systemd/pull/12378#issuecomment-493776598
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
> Looking at the discussion at
https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this
might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4.
I noticed that, however that points to:
added info from previous comment to the upstream freedesktop bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on the VT1 screen
To manage
** Tags added: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on the VT1 screen
To manage notifications about this bug go to:
Public bug reported:
[impact]
gvfs autopkgtests are highly flaky and fail across different
releases/archs for multiple different reasons. It's unclear if the
failures are actual package bugs, or just testcase bugs.
[test case]
look at the autopkgtest results:
** Also affects: dbus (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-terminal (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gnome-terminal
hi @cpaelzer, sorry i missed reading this earlier, i'll give all the
test failures a look to see what can be done.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392373
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1892358
Title:
Medium
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Focal)
ok, very sorry for my delay in looking at this.
a quick scan of the results for x/b/f show:
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:00.893145-04:00'
88: boot-smoke FAIL non-zero exit
** Package changed: systemd (Ubuntu) => tracker (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896756
Title:
tracker* startup is defined multiple times
To manage
fyi, this was an intentional upstream change, thanks @vtapia for
pointing me to the upstream wiki:
https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#SMB1_is_disabled_by_default
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Whew, this is a long bug.
So given comment 40 indicating part of this bug has been fixed in bug
1828639, and comment 42 indicating the any remaining patches should be
sent to debian, it seems to me that the ubuntu-sponsors team does not
need to be subscribed to this, as it's unclear what parts,
** Tags removed: ddstreet
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1803993
Title:
Password appears on the VT1 screen
To manage notifications about this bug go to:
autopkgtests pass for bionic for all archs, except once for i386, for
which I opened bug 1902554; the i386 test passed on retry.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification
autopkgtests pass for focal for all archs (except i386 which is expected
to fail for focal)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in
> This should fix the problem:
https://github.com/lxc/distrobuilder/pull/476
wow...all those 'fixes' lxd is adding look like things will continue to
break in bad ways, like this bug. ouch.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1699360
Title:
package libpam-systemd:amd64
please reopen if this is still an issue for systemd
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
** Description changed:
+ [impact]
+
+ pam_umask, from /etc/passwd, is not honored in systemd --user instances
+
+ [test case]
+
+ on a desktop system, edit /etc/passwd to change the test user entry
+ (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
+ field). For example
> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared
I just tested with groovy and can't reproduce the issue; umask is
correct under gnome-terminal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notificatio
Unfortunately I can't reproduce this bug, even with the
0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for
sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2.
Also note that the [test case] in the description is wrong, that would
be correct with the systemd change
I'm marking this invalid for systemd (the patch there was reverted) and
fix released for plymouth, with the assumption this was fixed with the
patch for bug 1817738.
If anyone is able to reproduce the problem please add a comment.
--
You received this bug notification because you are a member
As suggested in the freedesktop bug, this probably was fixed with the patch
added for bug 1817738 which is this commit:
https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/85d843af843589ce8538a59e5cb665b8253e380d
I haven't been able to reproduce this myself yet (when using the
plymouth
** Changed in: trusty-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1285783
Title:
Right panel has a transparent background
To manage
** Changed in: oneiric-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/865907
Title:
Please backport tracker to Oneiric
To manage
** Changed in: hardy-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/151207
Title:
Error when trying to open a .wmf file, should use Gimp
To
** Changed in: hardy-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/326741
Title:
Update GIMP to version 2.4.7 in hardy-backports
To manage
53 matches
Mail list logo
