[Desktop-packages] [Bug 2012341] Re: xdg-desktop-portal-gnome crashed with SIGSEGV in fast_validate()
I got this too. I think it's fixed by a46d3b338ed362e6dfad359db3d9a505bff0dc9c upstream. This is bad enough - it completely breaks screen sharing for me - that I think fixing in update/SRU rather than waiting for a point release would be warranted, will upload it. I'll write my testcase in the description in a minute. Alex, if you could add your one too, that would be good for the SRU! Also if you could check if the package fixes it for you (it does for me). ** Information type changed from Private to Public ** Also affects: xdg-desktop-portal-gnome (Ubuntu Lunar) Importance: Medium Status: Confirmed ** Changed in: xdg-desktop-portal-gnome (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: xdg-desktop-portal-gnome (Ubuntu Lunar) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2012341 Title: xdg-desktop-portal-gnome crashed with SIGSEGV in fast_validate() Status in xdg-desktop-portal-gnome package in Ubuntu: In Progress Status in xdg-desktop-portal-gnome source package in Lunar: In Progress Bug description: Tried to share a window under Wayland with obs-studio (installed from a deb) and apport popped up saying xdg-desktop-portal-gnome had crashed. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 16:25:47 2023 ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome InstallationDate: Installed on 2021-08-03 (595 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) ProcCmdline: /usr/libexec/xdg-desktop-portal-gnome ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f67fd7a94a0 : movzbl (%rdi),%eax PC (0x7f67fd7a94a0) ok source "(%rdi)" (0xa489eeb5ba526c40) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xdg-desktop-portal-gnome StacktraceTop: g_utf8_validate () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_string () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: xdg-desktop-portal-gnome crashed with SIGSEGV in g_utf8_validate() UpgradeStatus: Upgraded to lunar on 2023-01-27 (52 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2012341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942437] Re: [UIFe] Impish wallpapers
go for it! ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1942437 Title: [UIFe] Impish wallpapers Status in ubuntu-wallpapers package in Ubuntu: Triaged Bug description: The Impish Indri wallpapers, including two original images that won the wallpaper competition¹, and the official ones produced by the Canonical design team. As we got those past UI freeze (which happened on September 9), this requires a UI freeze exception². Gunnar (~gunnarhj), who is an administrator of both the documentation and translation teams, acknowledged the update in comment #8. ¹ https://ubuntu.com/blog/winners-of-the-21-10-wallpaper-competition ² https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions Original description: We need to include the winners of the 21.10 wallpaper competition in the release image. I don't know how to attack files here so I'll just provide links to the winning images in Discourse: First: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/171?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Second: https://discourse.ubuntu.com/t/wallpaper-competition-for- impish-indri-ubuntu-21-10/22852/60?u=rhys- davies&_ga=2.144156597.1440561583.1630580808-2071368223.1629705927 Also, I mentioned in the competition that if the Desktop team decided that they could fit more submissions into the release image without it becoming too big, that the next 8 submissions might make it in too. So if you decide you can fit more in please let me or Monica know and take them from the links in this blog post which lists them in the winning order: https://ubuntu.com/blog/winners-of-the-21-10-wallpaper- competition Let me know if there's anything else I can do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1942437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start
> Looks like both of us sponsored it for the queue. I'd appreciate
rejecting either one of them.
I pushed to the VCS[0] at the same time as sponsoring, so I'll reject
the other one which doesn't quite match up with it.
[0] https://salsa.debian.org/gnome-
team/glib/-/commits/ubuntu/2.64.6-1_ubuntu20.04.4/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1930359
Title:
glib2.0: Uninitialised memory is written to gschema.compiled, failure
to parse this file leads to gdm, gnome-shell failing to start
Status in GLib:
Unknown
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Focal:
In Progress
Bug description:
[Impact]
A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
user with 300 VDIs running Focal, where GNOME applications would fail
to start, and if you reboot, gdm and gnome-shell both fail to start,
and you are left with a black screen and a blinking cursor.
After much investigation, mutter was not at fault. Instead, mutter-
common calls the libglib2.0-0 hook on upgrade:
Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
...
This in turn calls glib-compile-schemas to recompile the gsettings
gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
result is a binary gschemas.compiled file, which is loaded by
libglib2.0 on every invocation of a GNOME application, or gdm or
gnome-shell to fetch application default settings.
Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
deterministic behaviour when calling glib-compile-schemas, causing
generated gschemas.compiled files to have differing contents on each
run:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 D0
3771 A4 DB
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 68
3771 A4 30
3772 55 56
The bytes on the left are from a corrupted gschemas.compiled provided
by an affected user. The changing bytes on the right are non-
deterministic.
I ran valgrind over glib-compile-schemas, and found that we are
writing to uninitialised memory.
https://paste.ubuntu.com/p/hvZccwdzxz/
What is happening is that a submodule of glib, gvdb, contains the
logic for serialising the gschema data structures, and when it
allocates a buffer to store the eventual gschemas.compiled file, it
does not initialise it.
When we populate the fields in the buffer, some bytes are never
overwritten, and these junk bytes find themselves written to
gschemas.compiled.
On boot, when gdm and gnome-shell attempt to parse and load this
corrupted gschemas.compiled file, it can't parse the junk bytes, and
raises and error, which propagates up to a breakpoint in glib logging,
but no debugger is present, so the kernel traps the breakpoint, and
terminates the library, and the calling application, e.g. gdm.
The result is that the user is left starting at a black screen with a
blinking pointer.
[Testcase]
On a Focal system, simply run valgrind over glib-compile-schemas:
# valgrind glib-compile-schemas /usr/share/glib-2.0/schemas
You will get output like this, with the warning "Syscall param
write(buf) points to uninitialised byte(s)":
https://paste.ubuntu.com/p/hvZccwdzxz/
If you happen to have a large amount of gschema overrides present on
your system, like my affected user does, you can save a copy of a
generated gschema.compiled to your home directory and bindiff it
against recompiles:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cp /usr/share/glib-2.0/schemas/gschema.compiled
/home/ubuntu/schemas/gschemas.compiled
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
If you install the test package from the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test
When you run valgrind, it will report a clean run with no writing to
uninitialised buffers, and all invocations of glib-compile-schemas
will be deterministic, and generate the file same with the same sha256
hash every time. The
[Desktop-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start
Thanks, sponsored to the queue
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1930359
Title:
glib2.0: Uninitialised memory is written to gschema.compiled, failure
to parse this file leads to gdm, gnome-shell failing to start
Status in GLib:
Unknown
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Focal:
In Progress
Bug description:
[Impact]
A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
user with 300 VDIs running Focal, where GNOME applications would fail
to start, and if you reboot, gdm and gnome-shell both fail to start,
and you are left with a black screen and a blinking cursor.
After much investigation, mutter was not at fault. Instead, mutter-
common calls the libglib2.0-0 hook on upgrade:
Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
...
This in turn calls glib-compile-schemas to recompile the gsettings
gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
result is a binary gschemas.compiled file, which is loaded by
libglib2.0 on every invocation of a GNOME application, or gdm or
gnome-shell to fetch application default settings.
Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
deterministic behaviour when calling glib-compile-schemas, causing
generated gschemas.compiled files to have differing contents on each
run:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 D0
3771 A4 DB
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 68
3771 A4 30
3772 55 56
The bytes on the left are from a corrupted gschemas.compiled provided
by an affected user. The changing bytes on the right are non-
deterministic.
I ran valgrind over glib-compile-schemas, and found that we are
writing to uninitialised memory.
https://paste.ubuntu.com/p/hvZccwdzxz/
What is happening is that a submodule of glib, gvdb, contains the
logic for serialising the gschema data structures, and when it
allocates a buffer to store the eventual gschemas.compiled file, it
does not initialise it.
When we populate the fields in the buffer, some bytes are never
overwritten, and these junk bytes find themselves written to
gschemas.compiled.
On boot, when gdm and gnome-shell attempt to parse and load this
corrupted gschemas.compiled file, it can't parse the junk bytes, and
raises and error, which propagates up to a breakpoint in glib logging,
but no debugger is present, so the kernel traps the breakpoint, and
terminates the library, and the calling application, e.g. gdm.
The result is that the user is left starting at a black screen with a
blinking pointer.
[Testcase]
On a Focal system, simply run valgrind over glib-compile-schemas:
# valgrind glib-compile-schemas /usr/share/glib-2.0/schemas
You will get output like this, with the warning "Syscall param
write(buf) points to uninitialised byte(s)":
https://paste.ubuntu.com/p/hvZccwdzxz/
If you happen to have a large amount of gschema overrides present on
your system, like my affected user does, you can save a copy of a
generated gschema.compiled to your home directory and bindiff it
against recompiles:
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cp /usr/share/glib-2.0/schemas/gschema.compiled
/home/ubuntu/schemas/gschemas.compiled
# glib-compile-schemas /usr/share/glib-2.0/schemas
# cmp -l /home/ubuntu/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 C3
3771 A4 98
If you install the test package from the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test
When you run valgrind, it will report a clean run with no writing to
uninitialised buffers, and all invocations of glib-compile-schemas
will be deterministic, and generate the file same with the same sha256
hash every time. The unwritten bytes if you do a bindiff from before
and after will be all set to zero.
[Where problems can occur]
I am doubtful that any programs are relying on buggy non-deterministic
behaviour from random bytes found in uninitialised memory, so this
should be a relatively
Re: [Desktop-packages] [Merge] ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel
Review: Approve Thanks Christian. Assuming you've tested this it looks fine to merge, but two things - I'm not sure we shouldn't drop 'dynamic' if that's not expected any more (and bump the required version of dnsmasq then). I could go either way on this - what do you think? - Please do the change in https://code.launchpad.net/~network-manager/network-manager/+git/ubuntu/+ref/ubuntu/master Feel free to make the change, or not, merge and upload - thanks! -- https://code.launchpad.net/~paelzer/ubuntu/+source/network-manager/+git/network-manager/+merge/405081 Your team Desktop Packages is requested to review the proposed merge of ~paelzer/ubuntu/+source/network-manager:fix-lp-1894619-changed-dnsmasq-behavior into ubuntu/+source/network-manager:ubuntu/impish-devel. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Also affects: libgweather (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-weather (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-weather (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libgweather (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-weather (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: libgweather (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: New Status in libgweather source package in Focal: New Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931547] Re: DisplayLink displays are black after Mesa update
Timo, please can you take care of this one, sounds like a regression? ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xorg-server (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: xorg-server (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: New Status in xorg-server source package in Hirsute: New Bug description: Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: mesa (Ubuntu Hirsute)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in Mesa:
Unknown
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Changed in: evolution-data-server (Ubuntu Hirsute) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Triaged Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926771] Re: [SRU] Hard dependency on desktop-file-utils not declared
** Changed in: wslu (Ubuntu Hirsute) Assignee: (unassigned) => Patrick Wu (callmepk) ** Changed in: wslu (Ubuntu Focal) Assignee: (unassigned) => Patrick Wu (callmepk) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: [SRU] Hard dependency on desktop-file-utils not declared Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Focal: New Status in wslu source package in Impish: Fix Released Bug description: [Impact] This bug will cause installation issues once LP #1911432 SRU Process complete. [Test Case] * checkout the ubuntu/master branch on wslu GitHub or launchpad repository; * Run the autopktest with command "autopkgtest path/to/folder -- null" in Ubuntu 20.04 on WSL1 and WSL2. * View the result of the test, it should be passed with 7 Windows Explorer open and 3 webpage open on the default browser. [Regression Potential] The potential regressions would be a result of badly generated ~/.config/wslu/, or a badly merged package. [Original Bug Report] Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: ubuntu-wsl depends on wslu; however: Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: Installed: 3.2.1-0ubuntu1.1 Candidate: 3.2.1-0ubuntu1.1 Version table: *** 3.2.1-0ubuntu1.1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.1-0ubuntu1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1926771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931602] Re: [apparmor] Segfault in logs with apparmor enabled
(Just assigning to clean the report) ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: firefox (Ubuntu Focal) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1931602 Title: [apparmor] Segfault in logs with apparmor enabled Status in firefox package in Ubuntu: New Status in firefox source package in Focal: New Bug description: [Impact] * With apparmor enabled (and usr.bin.firefox in enforce mode) there is a crash happening every time right after launching Firefox. [Test Plan] * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox * launch Firefox * See a similar segfault reported in the syslog: Jun 10 17:25:40 ubuntu kernel: [ 86.775837] firefox[1765]: segfault at 0 ip 7f724dd06384 sp 7fffa7aec450 error 6 in libxul.so[7f724a483000+53b2000] Jun 10 17:25:40 ubuntu kernel: [ 86.775843] Code: 00 0f 1f 44 00 00 50 80 3d f8 56 4c 04 00 74 02 58 c3 c6 05 ed 56 4c 04 01 48 8d 05 24 2c fa 02 48 8b 0d 77 f0 3a 04 48 89 01 04 25 00 00 00 00 8d 01 00 00 e8 74 63 78 fc 66 2e 0f 1f 84 00 [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled
(Just assigning to clean the report) ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) ** Changed in: firefox (Ubuntu Focal) Assignee: (unassigned) => Dariusz Gadomski (dgadomski) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1931603 Title: [apparmor] Unable to show Downloads with apparmor enabled Status in firefox package in Ubuntu: New Status in firefox source package in Focal: New Bug description: Impact] * After a finished download (or opening the downloads list) it is impossible to "Open Containing Folder" for a downloaded file - pressing the button does nothing visible. [Test Plan] * sudo aa-enforce /etc/apparmor.d/usr.bin.firefox * launch Firefox * Download a file. * Go to downloads list. * Press the "Open Containing Folder" button next to the downloaded file on the list. [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932311] Re: migrate to llvm 12
** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1932311 Title: migrate to llvm 12 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: (split off from bug 1917763) [Impact] Mesa should migrate to llvm 12 for new AMDGPU features and HW support. Normally this would be done during the devel series, but this version was delayed too much to migrate before hirsute was out. [Fix] Build-depend on the new packages, including libclc which is now built from llvm sources. [Test case] Test AMD graphics and/or qemu desktop (llvmpipe) after installing migrated packages. [Regression potential] This has been in Impish for a month now without issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Changed in: accountsservice (Ubuntu Groovy) Status: New => Invalid ** Changed in: accountsservice (Ubuntu Hirsute) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu Groovy) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu Hirsute) Status: New => Invalid ** Changed in: dbus (Ubuntu Groovy) Status: New => Incomplete ** Changed in: dbus (Ubuntu Hirsute) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It
[Desktop-packages] [Bug 1925837] Re: [Wayland] Sharing indicator window is not frameless
Just assigning for tracking - Olivier, please close when you do the upload! ** Also affects: firefox (Ubuntu Impish) Importance: Medium Status: Confirmed ** Changed in: firefox (Ubuntu Impish) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1925837 Title: [Wayland] Sharing indicator window is not frameless Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Status in firefox source package in Impish: Confirmed Bug description: I'm running updated hirsute with the firefox 87.0+build3-0ubuntu4 deb, just as it comes. This system was a fresh install of 20.10 that was then upgraded to 21.04. When I have a tab that will start using my webcam/mic, there is a new ff window that is created with these icons. The window is (more or less) minimized to fit the size of the icons (see screenshot). I can close the window by clicking the normal x, and closing this window does not interrupt my webcam/mic usage. What I normally expect is that when my webcam/mic is being used by some ff tab, the ff/webcam/mic icons are displayed constantly in the top middle of my display. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 21.04 ForcedLayersAccel: False InstallationDate: Installed on 2021-01-04 (108 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IpRoute: default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.6 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: firefox 87.0+build3-0ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=87.0/20210318103112 (In use) RunningIncompatibleAddons: False Tags: wayland-session hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1925837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856032] Re: Removable media icon stays on the dock after eject.
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Importance: Low Status: Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags removed: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1856032 Title: Removable media icon stays on the dock after eject. Status in OEM Priority Project: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock source package in Impish: Confirmed Bug description: 1) Ubuntu 19.10 2) Dock 3) I placed a DVD in the optical drive. An optical disc with a DVD tag appeared on the dock. I pressed the button on the optical drive to open it. I removed the disc and pressed in the tray. The icon should have disappeared from the dock. 4) The icon did NOT disappear from the dock. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
** Changed in: libreoffice (Ubuntu Hirsute) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Impish) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Hirsute: New Status in libreoffice source package in Hirsute: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. The no-change rebuild against 9.4.0-1ubuntu1~21.04 results in the same failure now. https://launchpadlibrarian.net/543392061/buildlog_ubuntu-hirsute-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu0.21.04.1~lo1_BUILDING.txt.gz https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-experimental/hirsute/armhf/libr/libreoffice/20210612_113218_f7f69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I filed an upstream bug with D-Bus: https://gitlab.freedesktop.org/dbus/dbus/-/issues/337 Hopefully a maintainer there will be able to give a better opinion as to what's going on here ** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337 https://gitlab.freedesktop.org/dbus/dbus/-/issues/337 ** Also affects: dbus via https://gitlab.freedesktop.org/dbus/dbus/-/issues/337 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Thanks! Here's where I think the problem starts: Ok, let's authenticate to dbus: Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus bus-api-system: changing state AUTHENTICATING → HELLO ... Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus bus-api-system: changing state HELLO → RUNNING Right, systemd thinks it's done it at least. You can see a whole bunch of messages being returned, the connection is working. After a while (note this first timestamp jump; is that significant? looks to be waiting for udev to settle I think so maybe not; could be snapd related) we decide to do something with a Type=dbus unit: Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a And another timestamp jump, waiting for this timeout: Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=3ms, elapsed: 45129ms) Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a error-message=n/a The dbus-daemon didn't think that the connection was authenticated. The last message AFAICS received on the bus connection was: Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading. No smoking gun yet, at least not to me. But interesting that the last thing which happened successfully was reloading. Can we have another go please, with these changes vs. an upstream clean image? - LogLevel=debug in /etc/systemd/system.conf - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. This dbus is just the one from impish backported to hirsute with verbose debugging turned on. And then attach the full `journalctl -b ` which will probably be quite large. :-) Maybe we'll get some information out of the dbus side to say what it thinks goes wrong with the connection. ** Please note ** The "connection has not authenticated" string does not appear in the earlier logs from Christian or Steve. It could be that there are two bugs here, with similar symptoms that systemd loses its connection to the system bus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: New Status in dbus source package in Groovy: New Status in gnome-shell source package in Groovy: New Status in accountsservice source package in Hirsute: New Status in dbus source package in Hirsute: New Status in gnome-shell source package in Hirsute: New Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
That's interesting actually. I thought this was an interaction between reloading dbus-daemon and daemon-reloading systems at the same time. But in this cloud case, I don't think dbus is being reloaded, is it? It's going to be next to impossible for me to look into this in detail without being able to reproduce it or getting a bit more debug information. Maybe you could crank up the system log level and try to reproduce this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
Ok, let's keep this bug report about the udev rule. We will need to make sure 470 works properly with prime, I'll follow up with that separately. So would you be able to prepare a merge proposal please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
Yeah, I read the man page too, but it wasn't understandable to me. If you understand it more, could you prepare a change for upstream? I can't just paste those two entries there to them, that's not enough information. Any hints on the second question about when wayland does start working, what prime support is supposed to do then? On Fri, Jun 04, 2021 at 05:42:53AM -, Alberto Milone wrote: > Here is the difference: > > DRIVER > Match the driver name of the event device. Only set this key for devices > which are bound to a driver at the time the event is generated. > > DRIVERS > Search the devpath upwards for a matching device driver name. > > https://www.freedesktop.org/software/systemd/man/udev.html > > > I assume the device is not always bound to the driver when the event is > generated. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1925238 > > Title: > [nvidia-prime] switches between xorg and wayland session > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
hmm, yeah, that seems to work! Why is that, can you explain why the other one doesn't work so we can forward it upstream (the udev rule is upstream)? Follow up question - we'll want to be dropping this file won't we, once nvidia actually supports wayland. What happens with prime then? On Thu, Jun 03, 2021 at 09:07:50AM -, Alberto Milone wrote: > yes, it is the ubuntu session (I wasn't given a choice on login). > > Can you try replacing "DRIVER" with "DRIVERS" in > /lib/udev/rules.d/61-gdm.rules , please? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1925238 > > Title: > [nvidia-prime] switches between xorg and wayland session > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
ack. Is yours the "ubuntu" session? i.e. auto-detection, the default, not "ubuntu-xorg" which is manually selecting "Ubuntu on Xorg" from gdm. Check $DESKTOP_SESSION. I can confirm that if I pick ubuntu-xorg then nvidia-smi looks like yours. I see from `lsmod` that nvidia is loaded - apparently that's not enough to get it to be used though. I would have expected the udev rule (61-gdm.rules) to have fired here and caused gdm-disable-wayland to run, so that I got Xorg and things running on the nvidia GPU; is that a valid expectation? On Tue, Jun 01, 2021 at 02:22:34PM -, Alberto Milone wrote: > I don't get that at all (see the attached screenshot). > > Detection seems to work well here: > > giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on Wayland... > giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on X11... > giu 01 16:05:52 dell-g7 systemd[1725]: > app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Succeeded. > giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: > Control process exited, code=exited, status=2/INVALIDARGUMENT > giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: > Skipped due to 'exec-condition'. > giu 01 16:05:52 dell-g7 systemd[1725]: Condition check resulted in GNOME > Shell on Wayland being skipped. > > ** Attachment added: "Screenshot from 2021-06-01 16-08-04.png" > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501675/+files/Screenshot%20from%202021-06-01%2016-08-04.png > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1925238 > > Title: > [nvidia-prime] switches between xorg and wayland session > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
No, they should be on "ubuntu" and that is Wayland if wayland works and Xorg if it doesn't. The problem is that changing the setting doesn't appear to have any effect at least from what I can see. For example look at the screenshot attached here. Do you see this kind of thing on a hybrid machine with hirsute or is it all OK for you? ** Attachment added: "Screenshot from 2021-06-01 13-01-36.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501666/+files/Screenshot%20from%202021-06-01%2013-01-36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1
I ran the applications listed in the description against 2.68.1-1~ubuntu21.04.1. I also generally exercised the desktop for a while and didn't notice anything odd. ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Committed Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
** Tags removed: rls-hh-incoming ** Also affects: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Sean, can you provide a debdiff for amdgpu please? I'm happy to sponsor it if you do that, ping me on IRC or something. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in xf86-video-amd: Unknown Status in Xfwm4: Unknown Status in xfwm4 package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Triaged Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Triaged Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Triaged Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Accepting the rls nomination. Daniel, can you maybe get Marco to review the MR upstream and then prepare backports for ubuntu/debian? ** Also affects: gnome-shell (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Hirsute) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Tags removed: rls-hh-incoming rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell source package in Hirsute: New Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: New Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1
automake-1.16> same started happening in impish too - you could cherry- pick 2b8b44ffc37047231757780952f6290398fb73e2 to the hints maybe? netplan.io> slyon told me this is known bad and is skipped in other releases already (upstream) and will be included in the next SRU to hirsute, if any. could be hinted too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Committed Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
I retried libgdata and it works now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Hirsute: Fix Committed Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
Hey Alberto, would you mind taking a look at this please? Feels to me like there might be some updates needed for wayland-by-default here..? ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
>From looking at the code it seems like we're writing Xorg config files - at least this probably needs updating to know about Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928001] [NEW] [SRU] New stable release 2.68.1
Public bug reported: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Hirsute) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: In Progress Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from
Hello Mahmoud, or anyone else affected, Accepted xserver-xorg-input-libinput into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /xserver-xorg-input-libinput/0.30.0-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1918985 Title: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIChangeDeviceProperty() Status in xserver-xorg-input-libinput: Unknown Status in xserver-xorg-input-libinput package in Ubuntu: Fix Committed Status in xserver-xorg-input-libinput source package in Hirsute: Fix Committed Bug description: https://errors.ubuntu.com/problem/ca9c5dd3e5b0995fd1e275261512a4a7bd61f7e9 --- W: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/hirsute/InRelease Verbindung fehlgeschlagen [IP: 141.30.62.24 80] W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: xserver-xorg-core 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 BootLog: Fr Mär 12 12:21:23 CET 2021 Fr Mär 12 22:40:02 CET 2021 CasperMD5CheckResult: unknown CompositorRunning: None Date: Fri Mar 12 23:05:07 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.10.0-14-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:850d] InstallationDate: Installed on 2020-12-17 (85 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 002: ID 1d57:fa60 Xenta 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 Convertible 15-cn1xxx ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/126/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=826c1aaa-9eb3-447b-aede-b8f0b5ef3ee2 ro recovery nomodeset dis_ucode_ldr ProcMaps: Error: [Errno 13] Permission denied: 'maps' Signal: 6 SourcePackage: xorg-server StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 11/16/2020 dmi.bios.release: 15.24 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 850D dmi.board.vendor: HP dmi.board.version: 70.76 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.76 dmi.modalias:
[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
Hello errors.ubuntu.com, or anyone else affected, Accepted nautilus into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.38.2-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Hirsute: Fix Committed Bug description: * Impact nautilus hits a segfault when called with the version argument, which was annoying but became problematic in hirsute since the desktop icons ng calls that command to check if nautilus is available * Test case $ nautilus --version shouldn't segfault * Regression potential The change is in a patch which was added to expose open locations to Unity for the benefit of the launcher and which is also used by the dashtodock one now. Check that the launcher correctly indicates which windows are active, especially when dealing with external devices. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
** Description changed: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg - too. When it's wayland then ondemand mode is selected. + too. + + Performance mode is selected in nvidia-settings, which is supposed to + mean nvidia & therefore xorg but it's not working. Selecting it + explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
>From the second boot ** Attachment added: "gpu-manager-wayland.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490359/+files/gpu-manager-wayland.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. When it's wayland then ondemand mode is selected. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
>From the first boot ** Attachment added: "gpu-manager-xorg.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490357/+files/gpu-manager-xorg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. When it's wayland then ondemand mode is selected. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
>From the second boot ** Attachment added: "lsmod-wayland.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490358/+files/lsmod-wayland.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. When it's wayland then ondemand mode is selected. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
>From the first boot ** Attachment added: "lsmod-xorg.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490356/+files/lsmod-xorg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. When it's wayland then ondemand mode is selected. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] [NEW] [nvidia-prime] switches between xorg and wayland session
Public bug reported: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. When it's wayland then ondemand mode is selected. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Attachment added: "modinfo-nvidia-drm.log" https://bugs.launchpad.net/bugs/1925238/+attachment/5490355/+files/modinfo-nvidia-drm.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. When it's wayland then ondemand mode is selected. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
I'll handle this, probably after Hirsute releases. Thanks! ** Changed in: gnome-terminal (Ubuntu Hirsute) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from
thanks. Timo, could you SRU this one please? ** Also affects: xserver-xorg-input-libinput (Ubuntu Hirsute) Importance: High Status: Triaged ** Changed in: xserver-xorg-input-libinput (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1918985 Title: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIChangeDeviceProperty() Status in xserver-xorg-input-libinput: Unknown Status in xserver-xorg-input-libinput package in Ubuntu: Triaged Status in xserver-xorg-input-libinput source package in Hirsute: Triaged Bug description: https://errors.ubuntu.com/problem/ca9c5dd3e5b0995fd1e275261512a4a7bd61f7e9 --- W: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/hirsute/InRelease Verbindung fehlgeschlagen [IP: 141.30.62.24 80] W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: xserver-xorg-core 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 BootLog: Fr Mär 12 12:21:23 CET 2021 Fr Mär 12 22:40:02 CET 2021 CasperMD5CheckResult: unknown CompositorRunning: None Date: Fri Mar 12 23:05:07 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.10.0-14-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:850d] InstallationDate: Installed on 2020-12-17 (85 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 002: ID 1d57:fa60 Xenta 2.4G Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 Convertible 15-cn1xxx ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/126/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=826c1aaa-9eb3-447b-aede-b8f0b5ef3ee2 ro recovery nomodeset dis_ucode_ldr ProcMaps: Error: [Errno 13] Permission denied: 'maps' Signal: 6 SourcePackage: xorg-server StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 11/16/2020 dmi.bios.release: 15.24 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 850D dmi.board.vendor: HP dmi.board.version: 70.76 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.76 dmi.modalias: dmi:bvnInsyde:bvrF.24:bd11/16/2020:br15.24:efr70.76:svnHP:pnHPENVYx360Convertible15-cn1xxx:pvrType1ProductConfigId:rvnHP:rn850D:rvr70.76:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-cn1xxx dmi.product.sku: 5WA69EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.3.4-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-libinput/+bug/1918985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04
(sorry, just noticed I didn't assign this last week when I was supposed to) ** Changed in: geoclue-2.0 (Ubuntu Focal) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1890924 Title: Location services work with location services off, 20.04 Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-2.0 source package in Focal: Triaged Status in geoclue-2.0 source package in Groovy: Won't Fix Bug description: * Impact Disabling the location service in settings isn't reflection on traditional deb applications * Test case - Log in an Ubuntu desktop session - install geoclue-2-demo - go to gnome-control-center, privacy, location and ensure the service is disabled - $ /usr/libexec/geoclue-2.0/demos/where-am-i the script should return a permission error and not a location * Regression potential [racb] Users who are currently relying on a working location service despite having a setting disabling it will find that the location service will stop working because the setting will start to be honoured. The change is in the client library, try a few applications, deb and snap or flatpak and make sure the status is correct respected - Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I had to have my application be approved by user to access location with Geoclue. Now it seems this is working without the location services "enabled"?? My application is repeater-START: https://sourceforge.net/projects /repeater-start/ Steps to see issue: 1) install Repeater-START and click the locate me button circle to the left. It goes to your rough location on map. 2) Go to settings, privacy, location, note that location is turned off!? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 19:38:12 2020 InstallationDate: Installed on 2017-07-29 (1106 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1890924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866035] Re: [FFe] List and install OEM enablement packages
The grub2 work was descoped. ** Changed in: grub2 (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1866035 Title: [FFe] List and install OEM enablement packages Status in grub2 package in Ubuntu: Won't Fix Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: [ Description ] We have a project underway at the minute to install any hardware- specific tweaks that are needed for the currently running machine, and to select a different kernel on those machines: the OEM kernel. This requires changes in grub, ubiquity and ubuntu-drivers common. We'd like to land those changes. grub On a live session, construct a DMI modalias and match it against the packages on the CD to see if we need to boot the OEM kernel. ubuntu-drivers-common = List the oem-*meta packages which apply to the running machine, and install those with 'install'. ubiquity Use the information that ubuntu-drivers provides to show some UI if there is a matching package, and also install the package if the user selects it. [ Testing ] We have a package "oem-qemu-meta" in Focal which you can use to test this inn a VM. If you're using libvirt, edit the XML for a Focal VM and add In the section: Under : UBUNTUQEMUTEST To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923187] Re: [FFe] Enable opencc support
We've discussed this on IRC but reporting here for the record- I think we should wait until next cycle for this change. It's unfortunate because the delays aren't Gunnar's fault (mainly waiting for the MIR), but now we don't have much time to find any bugs - if there are any - before the release, and we don't have people on hand skilled in the stack that Given that there isn't a pressing driver or a known super compelling feature that requires this to be in *this* release, it's safer to wait. Please feel free to get this uploaded at the start of the 21.10 cycle. Cheers! ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1923187 Title: [FFe] Enable opencc support Status in ibus-libpinyin package in Ubuntu: Won't Fix Bug description: opencc is a tool for conversion between traditional and simplified Chinese. In Debian ibus-libpinyin with opencc support has been in testing since the year end, and no bugs have been reported as a result of that. On the Ubuntu side we had to disable opencc support, since the required additional dependencies - libopencc1.1, libopencc-data and libmarisa0 - were in universe. libopencc1.1 and libopencc-data have since been promoted to main (bug #1909665), and as regards libmarisa0 it has been cleared for main promoting by both the MIR team and the security team (bug #1914808). Accordingly I'm asking the release team for permission to enable opencc support in Ubuntu hirsute too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1923187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
It does seem like it requires a feature freeze exception, but we should do it, so I'll accept. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Committed Status in vlc package in Ubuntu: Invalid Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
(but I asked for some input there from an apport maintainer, it could be better than I did it) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
See the attached branch, it's a fix for this in apport. ** Branch linked: lp:~laney/apport/pkttyagent -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment
I don't think we would want to carry the proposed patch as a distro patch. So as long as polkit doesn't have direct support for this, apport should do as systemd does, and spawn pkttyagent (--fallback) itself. I'll try quickly now to work on an initial patch for this. ** Changed in: policykit-1 (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Won't Fix Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
assigning to timo for better tracking ** Changed in: mesa (Ubuntu Hirsute) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: ubiquity (Ubuntu Hirsute) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921949] Re: math save icon reset upon click or arrow action
** Changed in: libreoffice (Ubuntu Focal) Status: New => Triaged ** Changed in: libreoffice (Ubuntu Hirsute) Status: New => Triaged ** Changed in: libreoffice (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1921949 Title: math save icon reset upon click or arrow action Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Status in libreoffice source package in Hirsute: Triaged Bug description: libreoffice 7.1.2.2 Changes are not being stored properly. Steps to reproduce: 1. open new math doc 2. add any equation -> see the save icon indicates there are changes that need to be saved. 3. click anywhere or arrow anywhere -> see the save icon go back to indicating there are no changes. Additionally you can close the doc in this state and you will not be prompted to save/discard changes. True in both focal and hirsute vms, in both the snap and the debs from the prereleases ppa. This problem *does not manifest* in an updated debian testing vm, with 7.1.2~rc2 from experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1921949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fail to appear or disappear and [JS ERROR: Error: Wrong type number; float expected. But it's out of range: -Infinity ... from _syncWorkspacesAc
We think this is fixed with the latest gjs in hirsute; can someone see if they can still reproduce? ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fail to appear or disappear and [JS ERROR: Error: Wrong type number; float expected. But it's out of range: -Infinity ... from _syncWorkspacesActualGeometry workspacesView.js:728] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922423] Re: Can't connect to some OpenVPN providers using openvpn 2.5.0 and nm-openvpn plugin
** Changed in: network-manager-openvpn (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: network-manager-openvpn (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1922423 Title: Can't connect to some OpenVPN providers using openvpn 2.5.0 and nm- openvpn plugin Status in NetworkManager-OpenVPN: Unknown Status in network-manager-openvpn package in Ubuntu: Triaged Bug description: There is a bug fixed upstream https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/64 This makes it impossible to use my VPN connections on Ubuntu 21.04. Please backport that fix before the release. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1922423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921963] Re: SRU 3.36.9
I guess hirsute is fixed for this? ** Changed in: yaru-theme (Ubuntu) Status: New => Fix Released ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress ** Changed in: yaru-theme (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1921963 Title: SRU 3.36.9 Status in gnome-shell package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Login a11y changed and so the usage of icons for notifications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1921963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
This came up on our tracking report for the desktop team, but we're not clear what is required in libxcb/amdgpu vs. a fix in the WMs themselves. Can someone clarify please? ** Changed in: libxcb (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libxcb (Ubuntu Focal) Status: New => Incomplete ** Changed in: libxcb (Ubuntu Groovy) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Incomplete Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Status in libxcb source package in Focal: Incomplete Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Incomplete Status in libxcb source package in Groovy: Incomplete Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Incomplete Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Groovy: Triaged Bug description: +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 libieee1284-3 libimobiledevice6 libjavascriptcoregtk-4.0-18 libldb2 libmediaart-2.0-0 libmozjs-68-0 libmutter-6-0 libnma0 libnotify4 libnss-mdns libnvidia-cfg1-435 libnvidia-common-435 libnvidia-compute-435 libnvidia-decode-435 libnvidia-encode-435 libnvidia-fbc1-435 libnvidia-gl-435 libnvidia-ifr1-435 libopenjp2-7 libpam-fprintd libpam-gnome-keyring libphonenumber7 libplist3 libprotobuf17
[Desktop-packages] [Bug 1921139]
-- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] ** Attachment added: "Hirsute-Hippo_WP_4096x2304_Grey_blank.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480520/+files/Hirsute-Hippo_WP_4096x2304_Grey_blank.png ** Attachment added: "Hirsuit-Hippo_WP_4096x2304_blank.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480521/+files/Hirsuit-Hippo_WP_4096x2304_blank.png ** Attachment added: "Hirsuit-Hippo_WP_4096x2304.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480522/+files/Hirsuit-Hippo_WP_4096x2304.png ** Attachment added: "Hirsute-Hippo_WP_4096x2304_Grey.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480523/+files/Hirsute-Hippo_WP_4096x2304_Grey.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1921139 Title: Hippo wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Here we go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1921139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921139] Fwd:
-- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] ** Attachment added: "Hirsute-Hippo_WP_2560x1440_Grey_blank.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480512/+files/Hirsute-Hippo_WP_2560x1440_Grey_blank.png ** Attachment added: "Hirsuit-Hippo_WP_2560x1440_blank.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480513/+files/Hirsuit-Hippo_WP_2560x1440_blank.png ** Attachment added: "Hirsuit-Hippo_WP_2560x1440.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480514/+files/Hirsuit-Hippo_WP_2560x1440.png ** Attachment added: "Hirsuit-Hippo_WP_1920x1080.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480515/+files/Hirsuit-Hippo_WP_1920x1080.png ** Attachment added: "Hirsuit-Hippo_WP_1920x1080_blank.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480516/+files/Hirsuit-Hippo_WP_1920x1080_blank.png ** Attachment added: "Hirsute-Hippo_WP_2560x1440_Grey.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480517/+files/Hirsute-Hippo_WP_2560x1440_Grey.png ** Attachment added: "Hirsute-Hippo_WP_1920x1080_Grey_blank.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480518/+files/Hirsute-Hippo_WP_1920x1080_Grey_blank.png ** Attachment added: "Hirsute-Hippo_WP_1920x1080_Grey.png" https://bugs.launchpad.net/bugs/1921139/+attachment/5480519/+files/Hirsute-Hippo_WP_1920x1080_Grey.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1921139 Title: Hippo wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Here we go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1921139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921139] [NEW] Hippo wallpapers
Public bug reported: Here we go ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1921139 Title: Hippo wallpapers Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Here we go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1921139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12
ACK, go for it (with 11 for now, I agree that switching to an RC compiler feels dodgy) ** Changed in: mesa (Ubuntu) Status: New => Triaged ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1917763 Title: FFE: new upstream release 21.0 and migrate to llvm 12 Status in mesa package in Ubuntu: Triaged Bug description: Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's been in Debian experimental since rc1. The packaging also migrates it to use llvm 12. The risks involve graphical issues or even crashes when running more intense OpenGL/Vulkan apps like games. Running a desktop is a simple use-case and should work fine across the board. Upstream gitlab has a fairly extensive CI for various drivers, while Intel tests on their own CI. This means that any showstoppers should be shaken out already. We will be able to pull maybe two point-releases before hirsute is frozen, and then push more as an SRU. I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too with some games, all good. packages for hirsute are available on ppa:canonical-x/x-staging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1917763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918336] Re: Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main)
This bug was fixed in the package gnome-remote-desktop - 0.1.9-5 Sponsored for fossfreedom (fossfreedom) --- gnome-remote-desktop (0.1.9-5) unstable; urgency=medium * Team upload [ David Mohammed ] * debian/control: add budgie-desktop as an alternate for gnome-shell (Closes: #982937) -- Simon McVittie Tue, 09 Mar 2021 10:31:04 + ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1918336 Title: Sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main) Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: Please sync gnome-remote-desktop 0.1.9-5 (main) from Debian unstable (main) Changelog entries since current hirsute version 0.1.9-4build1: gnome-remote-desktop (0.1.9-5) unstable; urgency=medium * Team upload [ David Mohammed ] * debian/control: add budgie-desktop as an alternate for gnome-shell (Closes: #982937) -- Simon McVittie Tue, 09 Mar 2021 10:31:04 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1918336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
> Also open-vm-tools is also FTBFS by this, so I need to add a task and
work on that as well.
You want this kind of thing minimally to get over the FTBFS:
--- open-vm-tools-11.2.5.orig/open-vm-tools/configure.ac
+++ open-vm-tools-11.2.5/open-vm-tools/configure.ac
@@ -503,6 +503,9 @@ AC_CHECK_PROG([have_genmarshal],
[yes],
[no])
+AC_DEFINE(GLIB_VERSION_MIN_REQUIRED, GLIB_VERSION_2_34, [Ignore post 2.34
deprecations])
+AC_DEFINE(GLIB_VERSION_MAX_ALLOWED, GLIB_VERSION_2_34, [Prevent post 2.34
APIs])
+
if test "$have_genmarshal" != "yes"; then
AC_MSG_ERROR([glib-genmarshal is required; make sure it is available in
your path.])
fi
But I would recommend also at least asking upstream to do the full fix
and move glib's headers out of 'extern "C"' too as outlined in comment
#2 here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include from an extern C context
Status in glib2.0 package in Ubuntu:
Fix Released
Status in open-vm-tools package in Ubuntu:
New
Status in qemu package in Ubuntu:
Fix Released
Status in ukui-control-center package in Ubuntu:
Triaged
Bug description:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as
[Desktop-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)
** Changed in: glib2.0 (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916701 Title: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered) Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Committed Bug description: When I installed the glib2.0 2.67.4-1 packages I consistently encountered a black screen on boot. The login screen was missing/delayed but eventually comes up without Wayland support (only Xorg sessions offered). To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1916701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
I'm going to close this bug in the 2.67.5-1 upload which I'm just making
to experimental. There will still be "some" projects still affected, but
it's as fixed as it's going to get from glib2.0's side - we made the API
break opt in for packages that have followed glib's longstanding advice
and defined the MAX_ALLOWED/MIN_REQUIRED macros.
Affected projects can do either (but should do both) of these.
- Define GLIB_VERSION_MAX_ALLOWED to something below GLIB_VERISON_2_66 to opt
out or _2_68 to opt in to this new typesafe behaviour.
- Not include glib's headers in an 'extern "C"' context. GLib has
G_{BEGIN,END}_DECLS that might help with this.
** Changed in: glib2.0 (Ubuntu)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Iain Lane (laney)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks include from an extern C context
Status in glib2.0 package in Ubuntu:
In Progress
Status in qemu package in Ubuntu:
Triaged
Status in ukui-control-center package in Ubuntu:
New
Bug description:
qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz
Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages
Error:
../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
from
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
from /usr/include/glib-2.0/glib/gtypes.h:32,
from /usr/include/glib-2.0/glib/galloca.h:32,
from /usr/include/glib-2.0/glib.h:30,
from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
56 | template
| ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
20 | extern "C" {
| ^~
Also in disas/nanomips.cpp, ...
And indeed disas/arm-a64.cc has:
20 extern "C" {
21 #include "qemu/osdep.h"
22 #include "disas/dis-asm.h"
23 }
Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.
So C++ constructs within a C scope which is this bug.
Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.
But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...
It is indeed failing in -proposed but working in hirsute-release.
10.2.1-20ubuntu1 : bad
repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp
With that I have a test env...
Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1
[Desktop-packages] [Bug 1802614] Re: [MIR] gnome-remote-desktop
The package got seeded, so 1. subscribed desktop-packages 2. laney@dev> ./change-override -S -c main -s hirsute gnome-remote-desktop Override component to main gnome-remote-desktop 0.1.9-4build1 in hirsute: universe/misc -> main gnome-remote-desktop 0.1.9-4build1 in hirsute amd64: universe/gnome/optional/100% -> main gnome-remote-desktop 0.1.9-4build1 in hirsute arm64: universe/gnome/optional/100% -> main gnome-remote-desktop 0.1.9-4build1 in hirsute armhf: universe/gnome/optional/100% -> main gnome-remote-desktop 0.1.9-4build1 in hirsute ppc64el: universe/gnome/optional/100% -> main gnome-remote-desktop 0.1.9-4build1 in hirsute riscv64: universe/gnome/optional/100% -> main gnome-remote-desktop 0.1.9-4build1 in hirsute s390x: universe/gnome/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: gnome-remote-desktop (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1802614 Title: [MIR] gnome-remote-desktop Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = GNOME switched to Wayland by default in the 3.22 release 2 years ago. Ubuntu followed that lead and defaulted to Wayland with 17.10 but switched back to X for 18.04 LTS. One key feature that the Ubuntu Desktop team supports with X and wants to continue supporting with Wayland is remote desktop. Therefore, I think this MIR is a blocker to enabling Wayland by default for 20.04 LTS. This MIR depends on the pipewire MIR (LP: #1802533) GNOME Remote Desktop To enable GNOME's remote desktop feature in Ubuntu, you need: - Build mutter with --enable-remote-desktop This has been done in Debian but we need pipewire in Ubuntu main to enable on Ubuntu - Install gnome-remote-desktop (MIR bug not filed yet) - I suggest uninstalling vino to make sure you will be using gnome- remote-desktop - Restart your computer - Log in to the Ubuntu on Wayland session. I believe it should work on X too but there is a misconfiguration in GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/212 - Open the Settings app to the Sharing page. Turn on Sharing in the app's top bar. Click Screen Sharing and turn it on. Only VNC is supported at this time. - Use remmina (Ubuntu's default app) or another VNC client like Remmina to connect from another computer. Security No known security issues https://security-tracker.debian.org/tracker/source-package/gnome-remote-desktop https://launchpad.net/ubuntu/+source/gnome-remote-desktop/+cve I expect the Security Team will want to review this MIR. Quality assurance = - Ubuntu Desktop bugs needs to be subscribed https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=gnome-remote-desktop https://gitlab.gnome.org/jadahl/gnome-remote-desktop/issues No autopkgtests. No build tests. Dependencies pipewire MIR (LP: #1802533) Standards compliance 4.2.1, debhelper compat 11, simple dh7 style rules Maintenance === Co-maintained in Debian with the Debian GNOME team upstream: https://gitlab.gnome.org/jadahl/gnome-remote-desktop https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Other Info == I think Debian Buster "10" GNOME will include GNOME Remote Desktop by default. Fedora 29 will include it by default soon (it looks like an oversight that it wasn't done before the 29 release). vino still has additional features that we want so we don't plan to demote vino to universe any time soon.Tha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1802614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916511] Re: [MIR] gnome-shell-extension-desktop-icons-ng
It's showing up on component-mismatches as it's been seeded: laney@dev> ./change-override -S -c main -s hirsute gnome-shell-extension-desktop-icons-ng Override component to main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute: universe/gnome -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute amd64: universe/gnome/optional/100% -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute arm64: universe/gnome/optional/100% -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute armhf: universe/gnome/optional/100% -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute i386: universe/gnome/optional/100% -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute ppc64el: universe/gnome/optional/100% -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute riscv64: universe/gnome/optional/100% -> main gnome-shell-extension-desktop-icons-ng 0.15.0-0ubuntu1 in hirsute s390x: universe/gnome/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1916511 Title: [MIR] gnome-shell-extension-desktop-icons-ng Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: * Availability The binary is an arch all one https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/0.15.0-0ubuntu1 The package is going to be uploaded to Debian and synced back once NEWed * Rationale The package is a replacement for our currently used gnome-shell- extension-desktop-icons, it's based on the same source but followed different technical choices to fix existing limitations Ideally we would like to integrate the feature in the desktop this cycle * Security There is no known security issues https://people.canonical.com/~ubuntu-security/cve/pkg/gnome-shell-extension-desktop-icons-ng.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=gnome-shell-extension-desktop-icons-ng * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons-ng/+bugs There are no bugs reported but the component is new. There is no tests nor autopkgtgests but that's not a difference over our current version. * Dependencies The dependencies are in main Depends: dconf-gsettings-backend | gsettings-backend, gnome-shell (>= 3.38), gjs, nautilus (>= 3.38), xdg-desktop-portal * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is going to be maintained in Debian by pkg-gnome and the desktop team is going to sign up for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1916511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914051] Re: `ubuntu-drivers list-oem --package-list` is broken
I think it'd be good to have an autopkgtest covering this when fixing it ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Milestone: None => ubuntu-20.04.2 ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Focal: New Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914051] [NEW] `ubuntu-drivers list-oem --package-list` is broken
Public bug reported: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: New Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6
> retry the test That has been done. Now the only red is netplan.io. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1907433 Title: [SRU] New stable release 2.64.6 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Committed Bug description: [ Description ] Take this new upstrem stable release. It was easiest for me to merge the latest release in this series from Debian, and then import the subsequent point releases on top of that. Visually in the diff there is one change resulting from this: splitting a two-patch upstream cherry pick into two individual patch files. This is cleaner anyway IMO, but is also no change if you look at the resulting patched source. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6
> retry the test with a trigger on libxmlb to get the -proposed version installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1907433 Title: [SRU] New stable release 2.64.6 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Committed Bug description: [ Description ] Take this new upstrem stable release. It was easiest for me to merge the latest release in this series from Debian, and then import the subsequent point releases on top of that. Visually in the diff there is one change resulting from this: splitting a two-patch upstream cherry pick into two individual patch files. This is cleaner anyway IMO, but is also no change if you look at the resulting patched source. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6
Okay I've verified this now, thanks for adding. Using 2.64.6-1~ubuntu20.04.1 I tested - Logging in to Ubuntu - Logging out from Ubuntu - Fast user switching w/gdm3 - Many applications which use GLib, including gedit and epiphany-browser It seems good to me. There are two outstanding autopkgtest regressions. The libxmlb failure is bug #1890313 and I just fixed it upstream, in hirsute (devel) & uploaded to the queue for focal/groovy. If you prefer you can accept that and retry the test, it should go green. netplan.io's one I didn't look into, but I think it is bug #1875677 (i.e. pre-existing). Should be hinted if not fixed? ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1907433 Title: [SRU] New stable release 2.64.6 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Committed Bug description: [ Description ] Take this new upstrem stable release. It was easiest for me to merge the latest release in this series from Debian, and then import the subsequent point releases on top of that. Visually in the diff there is one change resulting from this: splitting a two-patch upstream cherry pick into two individual patch files. This is cleaner anyway IMO, but is also no change if you look at the resulting patched source. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908502] Re: [MIR] libtiff5 dependency on libdeflate0
** Also affects: tiff (Ubuntu Hirsute) Importance: Undecided Assignee: Olivier Tilloy (osomon) Status: Confirmed ** Also affects: libdeflate (Ubuntu Hirsute) Importance: Undecided Status: Incomplete ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libtiff5 dependency on libdeflate0 Status in libdeflate package in Ubuntu: Incomplete Status in tiff package in Ubuntu: Confirmed Status in libdeflate source package in Hirsute: Incomplete Status in tiff source package in Hirsute: Confirmed Bug description: tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as a dependency to libtiff5, making the package uninstallable. Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate support to make libtiff5 installable again. Either this package stays this way, or it needs a MIR for libdeflate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
> OTOH I think there is an easy fix for GTK+ to always include an
"image-missing" icon at compile time
I'm sorry, it's not that easy. A PNG icon is indeed included, and it
gets found properly (also from the actual icon theme; that is a
dependency of GTK). The problem is the ability to load PNGs *at all* is
not available sometimes during the middle of dist-upgrades.
I think extending that test program in Debconf (referred to in the IRC
log above) to do a bit more work - trying to load an icon - might make
the fallback trigger in this case too.
e.g:
my $window = Gtk3::Window->new('toplevel');
my $icontheme = Gtk3::IconTheme::get_default;
my $icon = $icontheme->load_icon('image-missing', 32, []);
If you manually remove '/usr/lib/*/gdk-pixbuf-2.0/2.10.0/loaders.cache'
(suggest doing this in a VM) then you can reproduce this by extracting
the program out of Debconf.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Invalid
** Changed in: gtk+3.0 (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1627564
Title:
Debconf crash due to assertion failure in ensure_surface_for_gicon
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)
Status in debconf package in Ubuntu:
Confirmed
Status in gtk+3.0 package in Ubuntu:
Invalid
Status in debconf source package in Focal:
Confirmed
Status in gtk+3.0 source package in Focal:
Invalid
Bug description:
https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383
---
bubble opened up indicating there was a failure during the latest
update.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.4.0-9136-generic i686
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
Date: Sun Sep 25 20:37:06 2016
ExecutablePath: /usr/sbin/lightdm-gtk-greeter
InstallationDate: Installed on 2016-08-04 (52 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
ProcCmdline: /usr/sbin/lightdm-gtk-greeter
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/false
Signal: 6
SourcePackage: lightdm-gtk-greeter
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
[greeter]
theme-name = Lubuntu-dark-panel
mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
2016-08-14T22:33:57.293011
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky
On Wed, Dec 09, 2020 at 10:46:52PM -, Rico Tzschichholz wrote: > This issue is not restricted to arm* but have been seen occasionally on amd64. > It effects the binary package build too, where these tests are part of "make > check". > > There are a lot tests disabled in > 'sw/qa/uitest/writer_dialogs/openDialogs.py' for similar reasons. > > So while it locks up at "test_21_.uno:EditGlossary (openDialogs.openDialogs) > ... " I would give that a try: > https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=0136e1c7a8f8823cbd0e5027ed203ee0d2f71262 Thanks for the bug reference - I had an unconfirmed theory that the test was deadlocking somewhere! I think Heather mentioned seeing this in other tests too - it would be good to grep the failing logs to see... seems like the string when it starts a test doesn't contain a \n, so it looks like: test_21_.uno:EditGlossary (openDialogs.openDialogs) ... autopkgtest [22:36:52]: ERROR: timed out on command "... If it's only this one, or only a small number of tests which can hang (on slow / loaded machines particularly it seems) always, then skipping those few would be a reasonable solution, indeed. But if this can apply to any of the uicheck tests, then I think I'm still in favour of using timeout(1) to paper over the deadlock, by setting our own timeout, lower than the autopkgtest one, and skipping if we hit it. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1785262 Title: arm64 autopkgtests are flaky Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64. In the past 30 days, 8 out of 45 test runs failed. That a 18% failure rate. It would be good to understand if all those failures are similar, what's causing them, and if they can easily be made more robust. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1785262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6
** Description changed: [ Description ] Take this new upstrem stable release. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable - series is 2.66, and maintenance efforts will shift to that + series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - - #2194 gtk3/glib crash on gimp - - #2209 gthreadedresolver: faulty logic in parse_res_txt - - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 + - #2194 gtk3/glib crash on gimp + - #2209 gthreadedresolver: faulty logic in parse_res_txt + - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 + - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 + - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 + - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 + - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 + - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - - Croatian - - Portuguese - + - Croatian + - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 - + - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 + - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 + - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 + - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 + - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 + - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - - #2140 calling malloc in fork child is undefined-behaviour - - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 + - #2140 calling malloc in fork child is undefined-behaviour + - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 + - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 + - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - - Kazakh - - Slovenian + - Kazakh + - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. - [ Regression potential ] + [ What could go wrong ] - Various fixes in multiple places so multiple apps could be affected. + This update contains fixes in multiple places so multiple apps could be + affected. The consequences of a broken GLib can range from some + functions returning bad results sometimes, which have minimal runtime + implications, up to the system simply crashing all the time. + Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Description changed: [ Description ] Take this new upstrem stable release. + + It was easiest for me to merge the latest release in this series from + Debian,
[Desktop-packages] [Bug 1907433] [NEW] [SRU] New stable release 2.64.6
Public bug reported: [ Description ] Take this new upstrem stable release. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Focal) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu Focal) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1907433 Title: [SRU] New stable release 2.64.6 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: In Progress Bug description: [ Description ] Take this new upstrem stable release. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin
[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Status: New => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Importance: Undecided => High ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock source package in Focal: Confirmed Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1872268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906296] [NEW] All my USB devices are autosuspending now because of a too broad rule in libfprint
Public bug reported:
laney@raleigh> apt policy libfprint-2-2
libfprint-2-2:
Installed: 1:1.90.3+tod1-0ubuntu2
Candidate: 1:1.90.3+tod1-0ubuntu2
Version table:
*** 1:1.90.3+tod1-0ubuntu2 500
500 file:/srv/mirrors/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
This is the USB controller on my desktop (no fingerprint reader)
laney@raleigh> sudo udevadm info /sys/devices/pci:00/:00:1d.0/usb2/
P: /devices/pci:00/:00:1d.0/usb2
N: bus/usb/002/001
L: 0
E: DEVPATH=/devices/pci:00/:00:1d.0/usb2
E: DEVNAME=/dev/bus/usb/002/001
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=1d6b/2/508
E: TYPE=9/0/0
E: BUSNUM=002
E: DEVNUM=001
E: MAJOR=189
E: MINOR=128
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=1086603
E: ID_VENDOR=Linux_5.8.0-26-generic_ehci_hcd
E: ID_VENDOR_ENC=Linux\x205.8.0-26-generic\x20ehci_hcd
E: ID_VENDOR_ID=1d6b
E: ID_MODEL=EHCI_Host_Controller
E: ID_MODEL_ENC=EHCI\x20Host\x20Controller
E: ID_MODEL_ID=0002
E: ID_REVISION=0508
E: ID_SERIAL=Linux_5.8.0-26-generic_ehci_hcd_EHCI_Host_Controller_:00:1d.0
E: ID_SERIAL_SHORT=:00:1d.0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:09:
E: ID_VENDOR_FROM_DATABASE=Linux Foundation
E: ID_AUTOSUSPEND=1
E: ID_MODEL_FROM_DATABASE=2.0 root hub
E: ID_PATH=pci-:00:1d.0
E: ID_PATH_TAG=pci-_00_1d_0
E: LIBFPRINT_DRIVER=Hardcoded whitelist
E: ID_FOR_SEAT=usb-pci-_00_1d_0
E: TAGS=:snap_arduino_arduino:seat:
Note that it has
E: LIBFPRINT_DRIVER=Hardcoded whitelist
which is suspicious, why is libfprint touching that?
Furthermore, all devices attached to it have
ATTRS{power/control}=="auto"
in particular this causes problems for my mouse which doesn't like being
suspended - it takes a few seconds to wake up each time after I stop
using it, which is surprisingly annoying.
It's these rules:
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d6b", ATTRS{idProduct}=="0002",
ATTRS{dev}=="*", TEST=="power/control", ATTR{power/control}="auto",
MODE="0660", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d6b", ATTRS{idProduct}=="0002",
ENV{LIBFPRINT_DRIVER}="Hardcoded whitelist"
which are matching, and they shouldn't be here since they aren't
matching a fingerprint reader.
This is listed on
https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported%20Devices
as being "Mantra MFS100", which seems wrong I think.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: libfprint-2-2 1:1.90.3+tod1-0ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu53
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Mon Nov 30 18:43:42 2020
InstallationDate: Installed on 2012-10-07 (2976 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
SourcePackage: libfprint
UpgradeStatus: Upgraded to hirsute on 2020-08-18 (104 days ago)
** Affects: libfprint (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute third-party-packages
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1906296
Title:
All my USB devices are autosuspending now because of a too broad rule
in libfprint
Status in libfprint package in Ubuntu:
New
Bug description:
laney@raleigh> apt policy libfprint-2-2
libfprint-2-2:
Installed: 1:1.90.3+tod1-0ubuntu2
Candidate: 1:1.90.3+tod1-0ubuntu2
Version table:
*** 1:1.90.3+tod1-0ubuntu2 500
500 file:/srv/mirrors/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
This is the USB controller on my desktop (no fingerprint reader)
laney@raleigh> sudo udevadm info /sys/devices/pci:00/:00:1d.0/usb2/
P: /devices/pci:00/:00:1d.0/usb2
N: bus/usb/002/001
L: 0
E: DEVPATH=/devices/pci:00/:00:1d.0/usb2
E: DEVNAME=/dev/bus/usb/002/001
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=1d6b/2/508
E: TYPE=9/0/0
E: BUSNUM=002
E: DEVNUM=001
E: MAJOR=189
E: MINOR=128
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=1086603
E: ID_VENDOR=Linux_5.8.0-26-generic_ehci_hcd
E: ID_VENDOR_ENC=Linux\x205.8.0-26-generic\x20ehci_hcd
E: ID_VENDOR_ID=1d6b
E: ID_MODEL=EHCI_Host_Controller
E: ID_MODEL_ENC=EHCI\x20Host\x20Controller
E: ID_MODEL_ID=0002
E: ID_REVISION=0508
E: ID_SERIAL=Linux_5.8.0-26-generic_ehci_hcd_EHCI_Host_Controller_:00:1d.0
E: ID_SERIAL_SHORT=:00:1d.0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:09:
E: ID_VENDOR_FROM_DATABASE=Linux Foundation
E: ID_AUTOSUSPEND=1
E: ID_MODEL_FROM_DATABASE=2.0 root hub
E: ID_PATH=pci-:00:1d.0
E: ID_PATH_TAG=pci-_00_1d_0
E: LIBFPRINT_DRIVER=Hardcoded whitelist
E: ID_FOR_SEAT=usb-pci-_00_1d_0
E: TAGS=:snap_arduino_arduino:seat:
Note that it has
E: LIBFPRINT_DRIVER=Hardcoded whitelist
which
[Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky
> Would work for me, can we mark flaky-on-armhf only (I'd not be aware)? The only way I could think to do this would be to duplicate the test and use "Architecture:" to run the "Restrictions: flaky" one on armhf arm64 only and the other one otherwise. In this case the failure is a *timeout* though so I'm not sure that Restrictions: flaky works since it is being killed from the outside by autopkgtest itself (the test runner). That would need to be tested to make sure it does. You could do that by making a simple (in another package, doesn't have to be libreoffice) which has "Restricitons: flaky" and runs something like "sleep infinity". See what happens when autopkgtest times out the test - you can pass --timeout-test to reduce this value for testing. Onto the test itself a bit. When the "uicheck-sw" test passes, it takes in the region of 20-25 minutes. Picking two recent results: armhf: autopkgtest [05:43:20]: test uicheck-sw: [--- autopkgtest [06:03:54]: test uicheck-sw: ---] autopkgtest [06:03:58]: test uicheck-sw: - - - - - - - - - - results - - - - - - - - - - uicheck-sw PASS arm64: autopkgtest [02:52:01]: test uicheck-sw: [--- autopkgtest [03:05:33]: test uicheck-sw: ---] autopkgtest [03:05:34]: test uicheck-sw: - - - - - - - - - - results - - - - - - - - - - uicheck-sw PASS but the timeout we have (this is a "large" test, it runs with higher timeouts than we use by default) is after over 5 *hours* 30 minutes. It's clearly wildly variable, that's more than 10× as much time and it still timed out. If this is to do with the test runners being "loaded" (slower) vs "unloaded" (faster), then it could be a race condition that happens when the test runs slowly that causes it to get stuck? I'm not sure if you want to go down the route of investigating the actual failure, though, but it does feel to me like this "shouldn't" be failing. We're not usually close to the limits and just being tipped over them sometimes, does look like the test is actually getting stuck. But it would require someone to actually look at the tests themselves to determine that. Clearly having the tests working would be ideal; we want assurance that Libreoffice works on armhf and arm64. In the absence of this, since we're just mashing the retry button and not actually trying to fix them (ATM), making this stop blocking us one way or another would be better than the status quo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1785262 Title: arm64 autopkgtests are flaky Status in libreoffice package in Ubuntu: Triaged Bug description: See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64. In the past 30 days, 8 out of 45 test runs failed. That a 18% failure rate. It would be good to understand if all those failures are similar, what's causing them, and if they can easily be made more robust. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky
> we don't believe it's a release issue It would be good to elaborate when making such comments. It's a drag on the archive in general when we have flaky tests, and even more so when they take many hours and potentially multiple retries to succeed. What's the criteria you're using here? Are we saying that "release" is only for user facing issues and bugs which have a negative impact on development of Ubuntu itself aren't to go through this process? If so, I think the team should come up with a way of being able to raise such issues. That would seem to rule out FTBFS for example too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1785262 Title: arm64 autopkgtests are flaky Status in libreoffice package in Ubuntu: Triaged Bug description: See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64. In the past 30 days, 8 out of 45 test runs failed. That a 18% failure rate. It would be good to understand if all those failures are similar, what's causing them, and if they can easily be made more robust. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky
Christian raised this with us just now - I think we should consider taking a look at this. Looking at http://autopkgtest.ubuntu.com/packages/libreoffice/hirsute/arm64 http://autopkgtest.ubuntu.com/packages/libreoffice/hirsute/armhf the tests are basically OK but one of the uicheck-* ones ends up timing out often enough that it can be described as flaky. When this happens it causes a problem for other migrations, doubly so as the runs take many hours to complete whether they fail or not, which slows down migration speed. If it's not possible to fix the timeouts (feels like it might be hard or take a while) then disabling these subtests (only) on arm would be an option - stable tests with less coverage are better than flaky ones with more. We had https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?id=baf5a581da7ce3bb27a5b8ed44fadeb6e245e1ff in the past which might be a basis for what to do now, but that would want to be extended to arm64 too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1785262 Title: arm64 autopkgtests are flaky Status in libreoffice package in Ubuntu: Triaged Bug description: See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64. In the past 30 days, 8 out of 45 test runs failed. That a 18% failure rate. It would be good to understand if all those failures are similar, what's causing them, and if they can easily be made more robust. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky
** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1785262 Title: arm64 autopkgtests are flaky Status in libreoffice package in Ubuntu: Triaged Bug description: See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64. In the past 30 days, 8 out of 45 test runs failed. That a 18% failure rate. It would be good to understand if all those failures are similar, what's causing them, and if they can easily be made more robust. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1785262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
On Tue, Nov 17, 2020 at 07:50:20AM -, Julien Blanc wrote: > Same issue here. > > gvfsd is started by tracker-miner-fs. Disabling it made it work (note > that i also made the /etc/pam/systemd-user pam_sss change), ie gvfsd now > correctly has access to the kerberos token. > > I'm wondering why gvfsd is started by systemd-user and not gnome- > session. Changing that may be an acceptable workaround until a better > solution is found. It's being D-Bus activated by things early in the startup of the session. By disabling tracker or whatever you are stopping that D-Bus activation. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter
Issue here I think is that we use per-session overrides for the majority of our Ubuntu customisations, and these don't apply to greeter sessions. ** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Focal: Confirmed Status in ubuntu-settings source package in Groovy: New Status in ubuntu-settings source package in Hirsute: New Bug description: When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken
The package in groovy-proposed is a no-change backport of 20.10.3-0ubuntu1. But nevertheless, I've verified the fix with 20.10.3-0ubuntu0.20.10.1 installed now. The grey gorilla appears fine. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901353 Title: Ubuntu Default Greyscale Wallpaper Sym Link Broken Status in ubuntu-wallpapers package in Ubuntu: Fix Released Status in ubuntu-wallpapers source package in Groovy: Fix Committed Bug description: [ Description ] I forgot to update the symlink for the greyscale default gorilla wallpaper and so it doesn't show up in the wallpaper chooser. [ Fix ] Fix the symlink. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the greyscale groovy wallpaper isn't there. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] The sym link still links to the nonexistent Focal greyscale wallpaper. How to reproduce: Try to set the wallpaper to the default greyscale in Settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-wallpapers 20.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 21:40:40 2020 Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
I think maybe sssd needs to learn how to set the environment in "session" mode. I did ask some people at Canonical who know about this project, hopefully they will have some advice soon. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
I think anything which causes gvfs to start "early enough" (before gnome-session has a chance to upload the environment to systemd) will trigger this problem. So anything which starts from e.g. default.target, or maybe there are things like ibus which are started outside of systemd's control. I did a little bit of investigation on the upstream bug, and I think what is happening is that we don't run pam_sss for systemd-user sessions - it's not in /etc/pam.d/systemd-user or included in there e.g. via common-session-noninteractive. That means that when the session starts `systemd --user`, in its own `systemd-user` PAM session, the env var is not instantiated there and so it's not available to stuff that starts really early. Early - but not early enough - in the startup process, gnome-session uploads environment variables into the systemd environment. Anything which starts after that will get the right environment. In other words this is a race condition. Can someone experiencing this bug please undo all of the workarounds applied, and then try adding "session optional pam_sss.so" into /etc/pam.d/systemd-user just above the `pam_systemd.so` line? And then check that KRB5CCNAME is set in gvfsd's environment. I don't have an environment to fully test this so I was just able to do it with a hack, but it worked that far for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: Nautilus prompts for username and password when accessing a Samba share on a network drive, despite having a perfectly valid unexpired Kerberos ticket. The Kerberos ticket is obtained automatically at logon by authentication against a Samba Active Directory server (Samba AD-DC). Accessing the same Samba share with the same Kerberos ticket via "smbclient //host/sharename -k" works fine. One known workaround is: "nautilus -q", and then "killall gvfsd". After that, accessing the Samba share with Nautilus works normally as it should. I did not experience this issue in Ubuntu 16.04. It appears that a regression was introduced somewhere between 16.04 and 18.04. The issue is quite annoying and confusing for the users who are used to accessing Samba shares on the network drive without being prompted for their username and password. The issue appears to manifest itself usually not on the first access to a Samba share, but on subsequent accesses after a system reboot or upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry file before user login appears to fix the issue for the current user session, but then the problem reappears upon subsequent user logins or after a system reboot. Nemo appears to have the same problem as Nautilus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-daemons 1.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 3 11:12:06 2018 ExecutablePath: /usr/lib/gvfs/gvfsd InstallationDate: Installed on 2018-04-27 (66 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_CA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I was running libmutter-7-0 3.38.1-1ubuntu1. I could reproduce the
initial bug of not being able to launch Chromium from the snap. After
upgrading to 3.38.1-2ubuntu1, now I can launch it fine.
Additionally, ss shows that Xwayland is listening on the abstract socket
too.
laney@nightingale> ss -xlp | grep Xwayland
u_str LISTEN 0 1/tmp/.X11-unix/X0 71964
* 0 users:(("Xwayland",pid=3713,fd=5))
u_str LISTEN 0 1 @/tmp/.X11-unix/X0 71963
* 0 users:(("Xwayland",pid=3713,fd=4))
u_str LISTEN 0 1 @/tmp/.X11-unix/X1 71965
* 0 users:(("Xwayland",pid=3713,fd=7))
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1897224
Title:
Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
Status in Mutter:
Unknown
Status in snapd:
In Progress
Status in mutter package in Ubuntu:
In Progress
Status in snapd package in Ubuntu:
Won't Fix
Status in mutter source package in Groovy:
Fix Committed
Status in snapd source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users who select the Wayland session on Ubuntu 20.10 cannot run snap
confined X11 applications, due to gnome-shell no longer listening on an
abstract socket for connections.
* The fix, which has been accepted into upstream's gnome-3-38 branch
reverts the change removing the abstract socket, and fixes the bug that
prompted it's removal:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508
[Test Case]
* Start with a stock Ubuntu 20.10 desktop install.
* At the GDM login screen, after selecting your user account use the gear
icon to select the "Ubuntu on Wayland" session, and log in.
* Ensure Chromium is installed by running "sudo snap install
chromium".
* Try to run "chromium" from the terminal. Without the fix, it will fail
with the error "Unable to open X display". With the fix applied, it
will launch as normal.
[Regression Potential]
* The patch modifies the logic gnome-shell uses to launch Xwayland. So
there is a potential that the change could break X11 application
support on the Wayland session.
* The default configuration for gnome-shell is to launch Xwayland on
session start, so it should be immediately obvious if there are
problems.
* In addition to checking snapped X11 apps like Chromium, verify that a
few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc).
[Other Info]
* Running "ss -xlp | grep Xwayland" should show that it is listening on
both "/tmp/.X11-unix/X0" (the regular unix domain socket) and
"@/tmp/.X11-unix/X0" (the abstract socket).
---
I'm trying to run chromium installed via snap in Ubuntu 20.10 when running
Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
> chromium
[49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to
open X display.
I am able to run Firefox just fine (assuming that Firefox still runs
on xwayland) and also Intellij snap works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 25 09:45:16 2020
InstallationDate: Installed on 2016-09-05 (1480 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
Snap: chromium 85.0.4183.121 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901367] Re: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser
I checked the SRU (20.10.3-0ubuntu20.10.1, weird version) and this wallpaper appears now. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901367 Title: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser Status in ubuntu-wallpapers package in Ubuntu: Fix Released Status in ubuntu-wallpapers source package in Groovy: Fix Committed Bug description: [ Description ] The file Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is shipped in ubuntu-wallpapers-groovy but it isn't shown in the chooser, because of a typo in the two listing files. I probably renamed the file but forgot to update this. [ Fix ] Fix the typo by replacing a space character with an underscore. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg. wallpaper isn't there. I'll attach the picture down below so you can see what it will look like. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] about ubuntu 20.10 background /usr/share/backgrounds/contest/groovy.xml /usr/share/gnome-background-properties/groovy-wallpapers.xml wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..." and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken
Sorry, we don't do that. The current default greyscale wallpaper only is shown there, and this happens via ubuntu-wallpapers.xml. The reason is that we found that if we show them all (if you have multiple ubuntu- wallpapers-* installed) then it's very hard to tell between the different wallpapers, they all look quite similar when shrunk to the small size in the wallpaper selector. So if you can see the default grey wallpaper in Settings at all, then that's good for us. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901353 Title: Ubuntu Default Greyscale Wallpaper Sym Link Broken Status in ubuntu-wallpapers package in Ubuntu: Fix Released Status in ubuntu-wallpapers source package in Groovy: Fix Committed Bug description: [ Description ] I forgot to update the symlink for the greyscale default gorilla wallpaper and so it doesn't show up in the wallpaper chooser. [ Fix ] Fix the symlink. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the greyscale groovy wallpaper isn't there. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] The sym link still links to the nonexistent Focal greyscale wallpaper. How to reproduce: Try to set the wallpaper to the default greyscale in Settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-wallpapers 20.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 21:40:40 2020 Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901548] Re: Segfault on arm
(gnome-initial-setup:69424): InitialSetup-WARNING **: 11:35:06.795: Failed to send report: metrics from this machine have already been reported and can be found in: /home/laney/.cache/ubuntu-report/ubuntu.20.10 [New Thread 0x337fdb60 (LWP 69455)] [Thread 0x337fdb60 (LWP 69455) exited] [Thread 0xa0afab60 (LWP 69440) exited] (gnome-initial-setup:69424): GLib-GObject-WARNING **: 11:35:29.760: invalid cast from 'GtkFlowBoxChild' to 'GisSnapTile' Thread 1 "gnome-initial-s" received signal SIGSEGV, Segmentation fault. 0xf361a8b4 in SNAPD_IS_SNAP (ptr=0xab742b90) at ../snapd-glib/snapd-snap.h:25 25 ../snapd-glib/snapd-snap.h: No such file or directory. (gdb) bt #0 0xf361a8b4 in SNAPD_IS_SNAP (ptr=0xab742b90) at ../snapd-glib/snapd-snap.h:25 #1 snapd_snap_get_name (self=0xab742b90) at ../snapd-glib/snapd-snap.c:555 #2 0xaaaed7c0 in on_app_clicked (flow_box=, child=child@entry=0xab604e30, user_data=) at ../gnome-initial-setup/pages/apps/gis-apps-page.c:460 #3 0xf7c06a20 in g_cclosure_marshal_VOID__OBJECTv (closure=0xab67afe0, return_value=, instance=0xab34e6c0, args=..., marshal_data=, n_params=, param_types=) at ../../../gobject/gmarshal.c:1910 #4 0xf7c032b4 in _g_closure_invoke_va (closure=, return_value=, instance=, args=..., n_params=, param_types=) at ../../../gobject/gclosure.c:873 #5 0xf7c1df24 in g_signal_emit_valist (instance=0xab34e6c0, signal_id=, detail=, var_args=...) at ../../../gobject/gsignal.c:3403 #6 0xf7c1e170 in g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3550 #7 0xf759bfa8 in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #8 0xf7c032b4 in _g_closure_invoke_va (closure=, return_value=, instance=, args=..., n_params=, param_types=) at ../../../gobject/gclosure.c:873 #9 0xf7c1df24 in g_signal_emit_valist (instance=0xab1fa2c0, signal_id=, detail=, var_args=...) at ../../../gobject/gsignal.c:3403 #10 0xf7c1e170 in g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3550 #11 0xf7391dd0 in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #12 0xf7c066dc in g_cclosure_marshal_VOID__BOXEDv (closure=0xab1f5fd0, return_value=, instance=0xab1fa2c0, args=..., marshal_data=0xf7391d14, n_params=, param_types=0xaacdffa0) at ../../../gobject/gmarshal.c:1686 #13 0xf7c01484 in g_type_class_meta_marshalv (closure=, return_value=, instance=, args=, marshal_data=, n_params=, param_types=) at ../../../gobject/gclosure.c:1034 #14 0xf7c032b4 in _g_closure_invoke_va (closure=, return_value=, instance=, args=..., n_params=, param_types=) at ../../../gobject/gclosure.c:873 #15 0xf7c1df24 in g_signal_emit_valist (instance=0xab1fa2c0, signal_id=, detail=, var_args=...) at ../../../gobject/gsignal.c:3403 #16 0xf7c1e170 in g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3550 #17 0xf738e85c in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #18 0xf7390118 in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #19 0xf73938c4 in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #20 0xf73569a0 in gtk_event_controller_handle_event () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #21 0xf7537a54 in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #22 0xf759536c in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #23 0xf7c01484 in g_type_class_meta_marshalv (closure=, return_value=, instance=, args=, marshal_data=, n_params=, param_types=) at ../../../gobject/gclosure.c:1034 #24 0xf7c032b4 in _g_closure_invoke_va (closure=, return_value=, instance=, args=..., n_params=, param_types=) at ../../../gobject/gclosure.c:873 #25 0xf7c1d3c4 in g_signal_emit_valist (instance=0xab34e6c0, signal_id=, detail=, var_args=...) at ../../../gobject/gsignal.c:3403 #26 0xf7c1e170 in g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3550 #27 0xf7539d70 in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #28 0xf73df79c in ?? () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #29 0xf73e1488 in gtk_main_do_event () from /lib/aarch64-linux-gnu/libgtk-3.so.0 #30 0xf70a2674 in ?? () from /lib/aarch64-linux-gnu/libgdk-3.so.0 #31 0xf70d7b48 in ?? () from /lib/aarch64-linux-gnu/libgdk-3.so.0 #32 0xf7afdb00 in g_main_dispatch (context=0xaac8cdc0) at ../../../glib/gmain.c:3325 #33 g_main_context_dispatch (context=0xaac8cdc0) at ../../../glib/gmain.c:4016 #34 0xf7afdd98 in g_main_context_iterate (context=context@entry=0xaac8cdc0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4092 #35 0xf7afde64 in g_main_context_iteration (context=context@entry=0xaac8cdc0,
[Desktop-packages] [Bug 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken
Yeah, thanks for duping that. This is uploaded now to hirsute (the new in-development release) and groovy (it's in the review queue, look out for a message to test when it's accepted). ** Attachment added: "greyscale.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+attachment/5427228/+files/greyscale.png ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901353 Title: Ubuntu Default Greyscale Wallpaper Sym Link Broken Status in ubuntu-wallpapers package in Ubuntu: Fix Committed Status in ubuntu-wallpapers source package in Groovy: In Progress Bug description: [ Description ] I forgot to update the symlink for the greyscale default gorilla wallpaper and so it doesn't show up in the wallpaper chooser. [ Fix ] Fix the symlink. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the greyscale groovy wallpaper isn't there. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] The sym link still links to the nonexistent Focal greyscale wallpaper. How to reproduce: Try to set the wallpaper to the default greyscale in Settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-wallpapers 20.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 21:40:40 2020 Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901367] Re: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser
This is uploaded now to hirsute (the new in-development release) and groovy (it's in the review queue, look out for a message to test when it's accepted). Thanks a lot for reporting. ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901367 Title: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser Status in ubuntu-wallpapers package in Ubuntu: Fix Committed Status in ubuntu-wallpapers source package in Groovy: In Progress Bug description: [ Description ] The file Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is shipped in ubuntu-wallpapers-groovy but it isn't shown in the chooser, because of a typo in the two listing files. I probably renamed the file but forgot to update this. [ Fix ] Fix the typo by replacing a space character with an underscore. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg. wallpaper isn't there. I'll attach the picture down below so you can see what it will look like. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] about ubuntu 20.10 background /usr/share/backgrounds/contest/groovy.xml /usr/share/gnome-background-properties/groovy-wallpapers.xml wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..." and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901367] Re: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser
** Description changed: + [ Description ] + + The file Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is + shipped in ubuntu-wallpapers-groovy but it isn't shown in the chooser, + because of a typo in the two listing files. + + I probably renamed the file but forgot to update this. + + [ Fix ] + + Fix the typo by replacing a space character with an underscore. + + [ QA ] + + Right click on the desktop, ideally on a clean system so you don't have + other clutter. Pick "Change Background...". See that the + Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg. wallpaper isn't + there. I'll attach the picture down below so you can see what it will + look like. + + Install the SRU and check that it now appears and becomes selected. + + [ Regression potential ] + + The code in Settings checks that the wallpaper exists before showing it. + So if you can see it it must be there - there's no chance you can set a + wallpaper which simply won't work via this UI. + + Thinking laterally, it might be considered a regression if this + wallpaper is inappropriate in some way - like the resolution is too low, + or it renders badly for another reason. Make sure it looks right, since + this is the first time it's getting shown. + + [ Original description ] + about ubuntu 20.10 background /usr/share/backgrounds/contest/groovy.xml /usr/share/gnome-background-properties/groovy-wallpapers.xml wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..." and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-) ** Changed in: ubuntu-wallpapers (Ubuntu Groovy) Status: New => In Progress ** Changed in: ubuntu-wallpapers (Ubuntu Groovy) Assignee: (unassigned) => Iain Lane (laney) ** Attachment added: "Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+attachment/5427194/+files/Abstract_Painting_Photo_by_Pierre_Ch%C3%A2tel-Innocenti.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901367 Title: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser Status in ubuntu-wallpapers package in Ubuntu: New Status in ubuntu-wallpapers source package in Groovy: In Progress Bug description: [ Description ] The file Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is shipped in ubuntu-wallpapers-groovy but it isn't shown in the chooser, because of a typo in the two listing files. I probably renamed the file but forgot to update this. [ Fix ] Fix the typo by replacing a space character with an underscore. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg. wallpaper isn't there. I'll attach the picture down below so you can see what it will look like. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] about ubuntu 20.10 background /usr/share/backgrounds/contest/groovy.xml /usr/share/gnome-background-properties/groovy-wallpapers.xml wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..." and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken
** Description changed: + [ Description ] + + I forgot to update the symlink for the greyscale default gorilla + wallpaper and so it doesn't show up in the wallpaper chooser. + + [ Fix ] + + Fix the symlink. + + [ QA ] + + Right click on the desktop, ideally on a clean system so you don't have + other clutter. Pick "Change Background...". See that the greyscale + groovy wallpaper isn't there. + + Install the SRU and check that it now appears and becomes selected. + + [ Regression potential ] + + The code in Settings checks that the wallpaper exists before showing it. + So if you can see it it must be there - there's no chance you can set a + wallpaper which simply won't work via this UI. + + Thinking laterally, it might be considered a regression if this + wallpaper is inappropriate in some way - like the resolution is too low, + or it renders badly for another reason. Make sure it looks right, since + this is the first time it's getting shown. + + [ Original description ] + The sym link still links to the nonexistent Focal greyscale wallpaper. How to reproduce: Try to set the wallpaper to the default greyscale in Settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-wallpapers 20.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 21:40:40 2020 Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901353 Title: Ubuntu Default Greyscale Wallpaper Sym Link Broken Status in ubuntu-wallpapers package in Ubuntu: New Status in ubuntu-wallpapers source package in Groovy: In Progress Bug description: [ Description ] I forgot to update the symlink for the greyscale default gorilla wallpaper and so it doesn't show up in the wallpaper chooser. [ Fix ] Fix the symlink. [ QA ] Right click on the desktop, ideally on a clean system so you don't have other clutter. Pick "Change Background...". See that the greyscale groovy wallpaper isn't there. Install the SRU and check that it now appears and becomes selected. [ Regression potential ] The code in Settings checks that the wallpaper exists before showing it. So if you can see it it must be there - there's no chance you can set a wallpaper which simply won't work via this UI. Thinking laterally, it might be considered a regression if this wallpaper is inappropriate in some way - like the resolution is too low, or it renders badly for another reason. Make sure it looks right, since this is the first time it's getting shown. [ Original description ] The sym link still links to the nonexistent Focal greyscale wallpaper. How to reproduce: Try to set the wallpaper to the default greyscale in Settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-wallpapers 20.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 21:40:40 2020 Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901353] Re: Ubuntu Default Greyscale Wallpaper Sym Link Broken
** Changed in: ubuntu-wallpapers (Ubuntu Groovy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901353 Title: Ubuntu Default Greyscale Wallpaper Sym Link Broken Status in ubuntu-wallpapers package in Ubuntu: New Status in ubuntu-wallpapers source package in Groovy: In Progress Bug description: The sym link still links to the nonexistent Focal greyscale wallpaper. How to reproduce: Try to set the wallpaper to the default greyscale in Settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-wallpapers 20.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 21:40:40 2020 Dependencies: ubuntu-wallpapers-groovy 20.10.2-0ubuntu1 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-wallpapers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901367] Re: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser
Thanks a lot. It's not exactly a duplicate - there are two bugs here :( ** Summary changed: - ubuntu 20.10 background + Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser ** Also affects: ubuntu-wallpapers (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1901367 Title: Abstract_Painting_Photo_by_Pierre_Châtel-Innocenti.jpg is missing from wallpaper chooser Status in ubuntu-wallpapers package in Ubuntu: New Status in ubuntu-wallpapers source package in Groovy: New Bug description: about ubuntu 20.10 background /usr/share/backgrounds/contest/groovy.xml /usr/share/gnome-background-properties/groovy-wallpapers.xml wrong Filename "x:...Pierre Châte... -> o:...Pierre_Châte..." and please add "Gorilla Wallpaper Grey" to groovy-wallpapers.xml :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1901367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
