The issue had been identified to be in GDM.
** Package changed: authd (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2061850
Title:
Can't authenticate in
Public bug reported:
With nvidia driver, all GTK4 applications have label rendering issues.
They are not refresh until passing the cursor over them, giving blank
windows. The corner are white and not themed. Passing from one app scren
to another one reproduces the issue.
gnome-control-center or
Tracked for OpenShot with https://github.com/OpenShot/openshot-
qt/issues/5221
** Also affects: openshot
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Package changed: gvfs (Ubuntu) => tracker-miners (Ubuntu)
** Changed in: tracker-miners (Ubuntu)
Assignee: (unassigned) => Denison Barbosa (justdenis)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
** Changed in: gvfs (Ubuntu)
Assignee: Didier Roche (didrocks) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1956949
Title:
CPC AWS jammy bui
So, this seems a ack, but the libflatpak0 MIR should be dealt first.
Let's put it as in progress.
** Changed in: malcontent (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to malcontent in
$ ./change-override -c main -S sane-airscan
Override component to main
sane-airscan 0.99.25-0ubuntu1 in hirsute: universe/misc -> main
sane-airscan 0.99.25-0ubuntu1 in hirsute amd64: universe/graphics/optional/100%
-> main
sane-airscan 0.99.25-0ubuntu1 in hirsute arm64:
same here. As the testsuite doesn’t catch this, it clearly means each
shell and mutter updates should be tested both on Xorg and Wayland.
Nvidia user here, so Wayland isn’t an option
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1915570
Title:
Login screen password entry not working on systems with
gnome-shell (3.38.3-2ubuntu1) hirsute; urgency=medium
* Merge with debian, containing new upstream release (LP: #1915089)
* debian/patches: Correctly handle login cancellation and failures.
Ensure the GDM workers are terminated before restarting a new auth
request, allowing
Seems to be fingerprinting linked.
You can’t type any characters (regular or special):
- you type a "a"
- the password prompt shows up a first character being input
- then, the password prompt is immediately reset to empty.
--
You received this bug notification because you are a member of
I’m getting a lot of pam failures due to fingerprints in my logs:
févr. 12 08:21:51 casanier gdm-password][6277]: pam_unix(gdm-password:auth):
Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type
févr. 12 08:21:51 casanier gdm-fingerprint][6278]: gkr-pam: no password is
available
** Attachment added: "Log of upgrade list between a working and faulty reboot"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+attachment/5463728/+files/apt-upgrade-list
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Automated login is disabled here and I’m affecting by this bug too.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Tags added: tracking-hh
** Tags removed: tracking-hh
** Tags added: rls-hh-bugs
--
You received this bug notification because you are a member of Ubuntu
Desktop
$ ./change-override -c main -S golang-github-openprinting-goipp
Override component to main
golang-github-openprinting-goipp 1.0.0-1 in groovy: universe/misc -> main
golang-github-openprinting-goipp-dev 1.0.0-1 in groovy amd64:
universe/devel/optional/100% -> main
** Changed in: libgweather (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU] Update libgweather to 3.36.1
I reapplied your debian/changelog directly and pushed to focal (pending
approval). Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU] Update
Hey Amr and thanks for making ubuntu better.
Do you mind double checking your patch?
Trying to apply it on 3.36.0-1, I get those chunks failing to apply
(tried both your .diff and .diff.gz):
patching file debian/changelog
patching file libgweather/gweather-weather.c
patching file
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2716
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716
Importance: Unknown
Status: Unknown
--
You received this bug
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2715
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
Fresh install of 20.04 LTS with nvidia binary driver from our archive.
(dual Intel/Nvidia setup)
No setting change has been done. The card supports "On demand".
Tested with Firefox (about:support) and Chrome (config:cpu). Both are showing
the same result:
- default launch
Public bug reported:
I think the menu should rather be a checkbox which pins/unpins using a
dedicated card option. That way, people can always launch, for instance,
their browser with nvidia hardware acceleration for instance.
Something to discuss upstream of course.
ProblemType: Bug
Public bug reported:
Once you select manually performance mode in nvidia-settings, GNOME
Shell shouldn’t display "Use dedicated card option".
Launching directly any app, in this mode, starts your application using
the nvidia card already.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
** Package changed: zsys (Ubuntu) => gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1874191
Title:
Brightness setting too high
To
Retargetting to correct project with tag
** Package changed: zsys (Ubuntu) => gnome-disk-utility (Ubuntu)
** Tags added: zfs
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
Rationale: this is a regression on X11 in eoan (maybe not worth fixing
for it right now), but at least, should be fixed in focal IMHO
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Public bug reported:
- Open some non dbus activated apps (so, not terminal for instance) in your dock
- Kill the shell with SIGKILL
- Applications are being killed with the Shell being killed, apart from the
dbus activated ones.
This wasn't the case before 19.10 on X11. (caused by dbus user
zsys is handling this (adduser will try to execute it and creates a
dataset, and if it can't, it fallbacks to traditional directory
creation.
zsys isn't installed by default on 19.10 but should be on 20.04 LTS, so
I encourage you to install and test it! Thanks :)
I'll have to mark the bug as
Only zsys systems will have rollback, we had to revert rollback in pure
ZFS systems as per this package upload:
https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu7.
Indeed, we need to release note that people shouldn't upgrade the bpool
as grub isn't able to read newer zfs pool versions.
--
This is a regression for our vast majority of users using the normal
ubuntu product and quite visible one, I wouldn't put it as low.
** Changed in: gnome-shell (Ubuntu)
Importance: Low => High
** Changed in: mutter (Ubuntu)
Importance: Low => High
--
You received this bug notification
Public bug reported:
GNOME Shell & mutter on 3.33.91
When pressing volume up or down on Xorg and keeping it pressed, only the first
key event is sent, so the volume only goes up or down once, and doesn't scale
up/down as long as you keep the button pressed.
ProblemType: Bug
DistroRelease:
here is the output (reenabled drm to get it back):
$ glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 390.116
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365502
doesn't fix it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
[regression][nvidia]
-> I'm using 2 monitors (1 internal and 1 external).
-> The nvidia GPU is enabled, monitor is plugged to it through HDMI.
-> The CPU usage of GNOME Shell spikes. There is no writed at the same time
(the led doesn't blink) and no other process seems to run for it. The memory
usages seems stable
FYI, this happens even without drm enabled and only on Xorg session.
Alt+F2 -> r fixes it until next reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
** Attachment added: "cpu_mem.logs"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+attachment/5253048/+files/cpu_mem.logs
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050
Mobile] (rev a1)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Public bug reported:
Mutter is hanging for multiple seconds (5 or so) at random times, especially
when your user session starts and you open new applications from the launcher:
- the screen freeze (apps & Shell) completely
- you have a second cursor that you can move and refresh during that
s/upon/until
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1822478
Title:
[regression][nvidia] All on screen text is tiny. Icons are normal size
but text is nearly unreadable.
Note that I'm seeing this with modeset=1 (nvidia):
- Shell UI has small text (and so, small panel and such…)
- icons and application have normal size
Going to g-c-c => displays scaling factor is at 100% (I never changed it before
on that machine). Going to 200% -> Apply. The text is giant. Then,
confirming. I'm seeing the same regularly.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I confirmed that 3.32.0 + trunk commits fixes the crash.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Ok, after some more testing with new GNOME Shell (3.32.0 + some commits
backported), the situation has now improved when this case happens:
- there is no more icons for applications not having any appinfo, like the
update-notifier one.
- applications with appinfo have an icon with a decent size
Needs to be retested with G-S 3.32 which fixes the crash
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126. Test case
is:
1. sleep 1000 on one terminal
2. kill -SIGSEGV $(pidof sleep)
-> wait for update-notifier to try showing up apport (application crash) or
update-notifier
Public bug reported:
GNOME Shell freeze and crash if appindicator can't lookup an icon. A lot
of messages are spawned in the logs:
Feb 20 15:40:46 neutrino gnome-shell[2735]: message repeated 2 times: [
[AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4575]
Feb 20 15:40:46
This is merged and released
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1798612
Title:
OSD
** Changed in: gnome-shell (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1722886
Title:
Include l
I think Daniel was clear by changing to verification-done that this can go in.
We are talking about a less than a second flash, while blocking a bunch of
fixes for GNOME Shell in cosmic. Note that this second flash already existed
before the fix, and that the fix is correct, it will only be
ack for me, seb told me he would take care of the tests.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to teckit in Ubuntu.
https://bugs.launchpad.net/bugs/1803230
Title:
[MIR] teckit & xxhash, new rdeps of texlive-bin
To manage
I don't have the time to do a testround again, but I can give pointers
for whoever has time to have a look:
The patch is
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb,
in particular:
systemBackground = new
Are you sure it's differently? Look at the diff, it's supposively
exactly the same values than Yaru. Please check it and revert the status
as needed.
** Changed in: gnome-shell (Ubuntu Cosmic)
Assignee: Didier Roche (didrocks) => Daniel van Vugt (vanvugt)
--
You received this
The best way to get it fixed is to be able to disable mod extensions,
which is something I'm working on, and you can follow it on
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/2. This will
probably be for dingo.
--
You received this bug notification because you are a member of Ubuntu
I tried with gnome-3-26-1604 rev 74 is still slow fo me at first gnome-
calculator application startup (with no ~/snap)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~didrocks/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/357609
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
load.
By checking the 5. point, we are checking we didn't impact gresources.
>From https://github.com/ubuntu/yaru/issues/917.
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Assignee: Didier Roche (didrocks)
Status: In Progress
** Changed in: gnome-shell (Ubu
[ Regression potentiale ]
+ [ Regression potential ]
If this code change triggers any error, the OSD isn't displayed, but the
Shell stays up.
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: gnome-shell (Ubuntu)
Status: New => In
Upstream MP: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/266
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1798612
Title:
OSD shows volume level = 100% even if
Public bug reported:
[ Rationale ]
Display bug in volume OSD on volume keypress if volume > 100% (amplified)
[ Test case ]
1. Ensure OSD is not displayed on screen avec volume > 100% via the amplified
setting.
2. Press volume + or volume - on your keyboard.
-> OSD is shown, but volume level is
Fixed in gnome-shell as this is a separate parameter. Nice catch!
** Package changed: yaru-theme (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
Fixed in https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-
shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb
** Description changed:
- Dark purple (noise) background flashes up briefly (for a split second)
- during the login animation.
+ [Impact]
- The login screen and
** Description changed:
- Impact
- ==
+ [Impact]
New release in the stable 3.28 series.
https://gitlab.gnome.org/GNOME/evince/commits/gnome-3-28
https://gitlab.gnome.org/GNOME/evince/blob/gnome-3-28/NEWS
- Other Info
- ==
- I am not working on this update now.
+ [Test
Assigning it to gdm, even if the loop is in mutter, as we are going to
workaround it there.
** Package changed: mutter (Ubuntu) => gdm (Ubuntu)
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
didrocks | yes ;) I wonder what would happen if, while this is worked on, we
remove the udev rule to not regress some of our nvidia users for 18.10 release
next week (as
| a workaround)
Public bug reported:
This happens on some nvidia card, with the nvidia blob driver
(fallbacked to Xorg for gdm).
1. Boot your laptop
2. Log into gdm
-> once your user session is loaded, gdm GNOME Shell process goes crazy, up to
100%, continously.
GNOME Shell (for user gdm) restarts in loops
** Package changed: ubuntu-meta (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1795410
Title:
cannot bring up window menu via keybinding (alt-space or
Public bug reported:
In Bionic, we ship a communitheme snap, which shows up an additional gdm
entry named "ubuntu communitheme".
We want those users on Bionic -> Cosmic upgrade (and later, bionic LTS
-> f LTS) to fallback to the ubuntu session to not pick the theme in the
snap.
However, we
** Package changed: gnome-shell (Ubuntu) => pkgbinarymangler (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1793476
Title:
Missing French translations for some
Are you sure this is due to the above patch, can you try without it?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1691678
Title:
Scrollbars escape the bottom and right
** Changed in: evince (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1790609
Title:
Update evince to 3.2
** Changed in: ubuntu-meta (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1783571
Title:
Set Yaru as default
To manage
Thanks a lot! I was just looking at the same issue and got directed to
the bug. The diff is good, I've just sponsored it to cosmic.
Thanks again ;)
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of
** Changed in: gnome-session (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1790532
Ti
As a reminder, ubuntu-settings is failing due to a meson issue:
https://github.com/mesonbuild/meson/issues/3914.
The stack has been tested locally and everything works well, including
transition with removal of older alternatives and fallback to plan Shell
for GDM without the theme installed.
**
yaru MIR is https://bugs.launchpad.net/ubuntu/+source/yaru-
theme/+bug/1783600
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
There is no schedule schema changes as of now, so current replaces: is
still good and we'll see later on if we fork the schema or not. Sounds
good for the current states at least.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Triaged => Fix Released
--
You received
You will have to reimplement something similar to what Unity switcher
did I think. The implementation is different, so it needs to be a proper
implementation.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
** Description changed:
[ Impact ]
- * The current label "Manual" is in fact shutting down whoopsie completely
and not providing any graĥical way to set manual reports (which is our default
on 18.04)
- * We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is
linked to
@Brian: I just had a deeper look after an initial tests, and brought
jibel along.
Indeed, there are quite some flaws on those options which never worked
(but was shipped since 12.04). On top of that, I found another
regression that happened probably during the upstart -> systemd
transition.
If there is a need for a 3rd party package for it, it means that
whoopsie-preferences is broken for quite some years: the automatic
option was present in g-c-c for years in ubuntu, and just use whoopsie-
preferences API to turn this automatic send mode. Note that the API
doesn't report any error
It's an option which was already present (only the "never" one wasn't):
whoopsie upload crash reports automatically.
See the g-c-c panel from that version to see the option dialog box.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Translator team emailed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1774597
Title:
G-C-C privacy option don't allow sending manual report
To manage notifications
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: gnome-shell (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: gnome-control-center (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Deskto
Public bug reported:
[ Impact ]
* The current label "Manual" is in fact shutting down whoopsie completely and
not providing any graĥical way to set manual reports (which is our default on
18.04)
* We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is
linked to sending
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1720310
The list of real entries are (at that time, it's dynamic):
TrackArchChannel VersionRevision
Expires at
latest all stable 0.1124
candidate^ ^
** Changed in: gnome-session (Ubuntu Bionic)
Status: New => Triaged
** Changed in: gnome-session (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-session (Ubuntu Bionic)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notificatio
** Description changed:
+ [Impact]
+
+ * People having this particular setup:
+- removed ubuntu-desktop metapackage from their system
+- upgrading from 16.04 to 18.04 (or previously to 17.10) by manually
editing /etc/apt/sources.lists without using do-release-upgrade (which
reinstalls
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1720310
Title:
unity-gnome-sh
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1764355
Title:
Visual Studio Code, Slack and other
Note that XDG_DATA_DIRS is expanded as well, we should protect against
it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1764355
Title:
Visual Studio Code, Slack and other
** Summary changed:
- XDG_CONFIG_DIRS keeps getting expanded every login
+ Visual Studio Code, Slack and other electrons apps crash due to
XDG_CONFIG_DIRS keeps getting expanded every login
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The I think then an old session is hanging around.
How long are you waiting before logging out and back in again?
Please, try the following:
- login, and wait for *at least* a minute so that everything that is lazy
loaded shutdown
- logout, and login back in
- check XDG_CONFIG_DIRS
/!\ Ensure
** Package changed: gnome-session (Ubuntu) => ubuntu-settings (Ubuntu)
** Description changed:
Change default interface font size in Community theme from 11 to 10.
- It won’t impact the default session only the communitheme.
+ It won’t impact the default session only the communitheme, which
FYI, I started the discussion on the GNOME Shell mailing list in october:
https://mail.gnome.org/archives/gnome-shell-list/2017-October/msg00034.html
There is a pending request with patches posted in November on upstream
bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=789852 and patches in
Adding rls-bb-incoming to inspect the difference between 16.04 and
bionic. Happy to modify the snap as needed.
** Tags added: rls-bb-incoming
** Summary changed:
- communitheme not present in gnome software
+ communitheme not present in gnome software on bionic, but it is on 16.04
** Summary
I think this isn't specific to ubuntu dock, but rather a dash to dock bug. Does
anyone here mind reporting that upstream?
https://github.com/micheleg/dash-to-dock/issues
(you can then link the bug here)
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Package changed: mutter (Ubuntu) => ubuntu-settings (Ubuntu)
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Public bug reported:
This session isn't displayed and available in GDM by default.
If the communitheme snap is installed, 2 new session options appears,
selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
cursor). All session/theme assets will be in the snap. We only expose
here
1 - 100 of 1498 matches
Mail list logo
