It's marked failed to upload on all architectures right now:
INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
I guess that
I've loaded up a system with a hand built kernel that has simpledrm
enabled, and then verified the problem occurred. I then updated to
proposed and verified it went away.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
Do you have something in /usr/local perhaps? Or did you have a snap
installed for fwupd?
** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu)
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
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/2039570
Title:
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
This should be a different issue than the mutter issue; please open it
up separately for investigation.
--
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/2034619
Title:
[amdgpu]
#75
You can turn on proposed and then use ppa-purge command to remove my
PPA.
--
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/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'd
they will be different binaries.
Please reject the *ubuntu4 version from the mantic-proposed queue and
accept the *ubuntu3.1 version (if it looks good).
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because
I've also uploaded the mutter package into the proposed queue for SRU
team to look at.
** Changed in: mutter (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Mantic)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received th
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
** This bug has been marked a duplicate of bug 2034619
[amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in
Wayland
--
You received this bug notification because you are a
This is the upstream fix for this issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** Description changed:
[ Impact ]
When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a
series of events can occur that cause simpledrm to race with GDM. When GDM
loses the race then a user is left with a black screen.
This series of events doesn't currently
I've split up the GDM for Jammy change into
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757
** No longer affects: gdm3 (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
> Oh, wait. You are just fixing the race condition?
Yeah; I see the confusion. This issue got caught up by making sure the
GDM race condition was fixed at the same as when this feature is
enabled.
Perhaps it's better to split the GDM part of it off to it's own bug
instead then.
> In that case,
The problem is specifically when 24.04's kernel backports to 22.04 it
will expose the race condition to GDM. If that kernel will never
backport then it won't be a problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
The issue won't occur in Lunar. It's only specifically a problem with gdm when
a kernel has been configured this way.
It's not a problem in Jammy yet, but will be a problem when such a kernel gets
backported as HWE.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status:
The kernel part yes. The bug fix in GDM to prepare for whenever the
kernel part happens I would think not.
--
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/1965303
Title:
Migrate from
changes landing in OEM-6.5, or HWE-6.5.
** Changed in: gdm3 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: gdm3 (Ubuntu Jammy)
Assignee: (unassigned) => Mario Limonciello (superm1)
** Description changed:
- [ Impact ]
+ [ Impact ]
The fbdev subsystem ha
** Description changed:
- The fbdev subsystem has been deprecated for a long time. We should drop
- it in favour of using simpledrm with fbdev emulation layer.
+ [ Impact ]
+ The fbdev subsystem has been deprecated for a long time. We should drop it in
favour of using simpledrm with fbdev
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is
still open.
** Changed in: gdm3 (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
I think that this should be changed in gnome software not to try to
start fwupd then when in WSL2.
** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in
** Also affects: gdm (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu
I'm adding a task for gdm to this bug. The reason is that if simpledrm
is used, we've found race conditions that occur where the transition
from simpledrm to the proper KMS driver may race with gdm starting up
the login screen.
When gdm loses the race you end up with a black screen. So please
> Crashing in getenv with a valid parameter like this should not be
possible so I think some heap corruption must have occurred before the
crash.
So at least as a hint coming from a report that was marked as a
duplicate of this - at least for me it's specifically when the system
had a monitor
I tested 42.5-0ubuntu1 on a Z13 (which prompted the heuristics change)
and can confirm it's working with Wayland and the non-functional
resolutions are no longer offered.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
> A default Ubuntu install only gets us "Security Level 1". The highest
level is "Security Level 3".
It's not a function of the OS, it's a function of the underlying hardware,
firmware, and firmware configuration for your given system.
The "!" in the HSI string is controlled by OS behavior (such
FYI - 1.8.4 synced from Debian to Ubuntu kinetic now.
--
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/1987162
Title:
43: New Device Security feature is confusing and
> The comment at
https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992
suggests that disabling the DynamicUser= setting makes the service work
again. Maybe that's worth a try, in order to get both problems solved?
(i.e. shipping an override config for fwupd)
> $cat
> https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907
This appears to have caused a regression in fwupd in Ubuntu 20.04 with
details at https://github.com/fwupd/fwupd/issues/3037
fwupd-refresh.service uses DynamicUser and now
** Also affects: libfprint (Ubuntu Jammy)
Importance: Medium
Status: New
** Also affects: libfprint (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: libfprint (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Jammy)
Reproduced again:
1. Logged out from Xorg session
2. Logged in again with default of Xorg selected, it logs into Wayland
3. Logged out once more and clicked the selected Xorg menu entry again.
4. Logged back in - now into Xorg.
5. Created the attached journal.txt.
There are no crash reports in
** Summary changed:
- Log in with Wayland although Xorg looks selected in session menu. Need to
reselect
+ Logs in with Wayland although Xorg looks selected in session menu. Need to
reselect
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
After upgrade to Impish.
1. Log in with Xorg session
2. Log out
3. Check gdm session menu > Xorg is displayed as selected
4. Log in > Wayland is running
5. Log out
6. Check gdm session menu > Xorg is displayed as selected
7. Choose Xorg again anyway
8. Log in
9. Success.
I am having the same issue in Fedora 34 / gnome-disk-utility 40.1 /
Gnome 40.
Probably not an Ubuntu specific issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
Thank you, I tested the new values and it all works as expected for me.
However, not sure what it is but the 225% value seems to change the rendering
in an unpleasant way. Not sure if it's only not being used to it, but for the
time being it feels more "comfortable" reverting to 200% and upping
Daniel, I am affected as well like in the previous bug. Model is Dell XPS 9575
2-in-1.
Shall I run the apport-collect as well?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
@albertvaka
I realize it stopped working for me as well, 20.04 with mutter
3.36.6-1ubuntu0.20.04.2
Still same machine as in above posts, Dell XPS 9575 2-in-1
No idea if same problem reappeared or it's an entirely new one
--
You received this bug notification because you are a member of Ubuntu
@michel.ekimia, please see bug #1880596
--
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/1760399
Title:
New On-screen keyboard does not appear automatically when selecting
Maybe I should add that I qualify the OSK appearing in laptop mode under X as
"Success" because:
-This is how it behaved until 19.10 both under X and Wayland
-In the upstream bug it was mentioned that the laptop vs tablet mode detection
would not work under X and so the new behavior under
Fix released, see the new bug #1880596. Should this one be marked a
duplicate of bug #1880596?
--
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/1866556
Title:
On-screen keyboard
Installed mutter 3.36.3-0ubuntu0.20.04.1 from -proposed.
This fixes the bug for me on the Dell XPS 9575 (could not test on the Asus
Zenbook)
Tested:
1. Logged into Xorg session
2. In laptop mode (physical keyboard enabled):
- Touch Activities > Search: Success, OSK appears
- Touch Show
And thank you!
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible
Will be fixed in 3.36.3:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242#note_823253
--
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/1880596
Title:
[Focal regression]
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
sudo libinput list-devices > list-devices.txt:
was generated in laptop mode i.e. with the physical keyboard enabled.
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bugs:
+ Related upstream bugs:
@seb128: Created the new bug #1880596
--
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/1866556
Title:
On-screen keyboard (OSK) on touch screen does not seem to work at all
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+ Related upstream bugs:
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
+
Public bug reported:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices
@seb128: A new bug for each device? I am the OP and I reproduced this on
two different foldable laptops (Dell XPS and Asus Flip), should I open a
new bug for each? (When opening this here bug, I used ubuntu-bug on the
Dell XPS)
--
You received this bug notification because you are a member of
Related Bug #1851931 ?
--
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/1866556
Title:
On-screen keyboard (OSK) on touch screen does not seem to work at all
under Xorg in
Thanks.
It does look to me that the keyboard issue is probably separate and certainly
warrants a bug, in particular if it is a regression and those 2-in-1s switched
fine with Ubuntu 19.10.
But I am just a mere user here, @vanvugt will know.
--
You received this bug notification because you are
Thanks. So it seems as follows, correct?
This here bug report refers only to running under Xorg in Focal, where ...
- the OSK does not work at all on the properly supported devices (at least the
ones listed),
- neither per autosummon nor on demand by swiping,
- regardless of a physical
@esjarc, does the keyboard get disabled when you fold your machines? It
does on mine, as it should be. I'm just wondering where the difference
comes from
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
@esjrac, you wrote in the duplicate Bug #1874017 that the issue occurs
for you under Wayland as well. Can you repro this also in the tablet
mode of the foldable devices that you mentioned there?
I am asking because for me this occurs under Wayland only if the devices
are laptop mode. In tablet
*** This bug is a duplicate of bug 1807276 ***
https://bugs.launchpad.net/bugs/1807276
@esjarc, as the OP of this report I agree and also commented as much in
the other #1807276 already.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Still reproducible with Ubuntu 20.04 beta with gnome-control-center
1:3.36.1-1ubuntu4 and gnome-3.36.1, where the option to enable
fractional scaling is exposed in the GUI
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
But it worked before for me before, see duplicate
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556
And the part where it does not appear at all occurred in the past and was
fixed: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399
--
You received this bug
Public bug reported:
After upgrading to Focal, the OSK never appears for me under Xorg
- Does not appear automatically when selecting text fields
- Cannot be summoned on-demand by swiping up from bottom screen border (which
worked on Eoan also under Xorg)
Under Wayland, both these things
Sadly, I am not having Nvidia drivers installed and the fix about
GRUB_CMDLINE_LINUX_DEFAULT=""
doesn't work either for me. The only way I was able to suspend the login
loop was to uninstall gdm3 and switch back to lightdm.
I think it is not useful that I open up a new issue therefore I am
I'm the OP and I can't. Thanks
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1832124
Title:
Right-click file on desktop > Move to Trash frequently
On Eoan (on the Dell XPS 9575 mentioned before), the OSK auto-summons
nearly everywhere as far as I can tell, incl. Chrome. The only
application I use and found so far where this does not work is Gnucash.
There is even an improvement in X that helps in this case: the OSK now
can be summoned by
Holy cow, I completely misunderstood the UI. Sorry for bothering!!!
** Changed in: gnome-terminal (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
And regarding "Can you recall when was the last time the cursor showed
up correctly for you? (Like, about 1 day ago, about 1 week ago...?) Was
that on disco, or eoan beta?"
I cannot be sure, but it probably was within the last week that it still worked
with the custom theme I had. I am tempted
Thanks. My results:
No cursor visible with the command running.
No cursor with any of the three cursor shapes selected (and blinking off).
Colors: This did it.
My system theme option was unchecked (I did that recently after some Yaru (I
think) update in Eoan changed the background color from
Public bug reported:
There is no cursor in gnome-terminal. Issue persists after reboot.
Must have happened after some recent update as I use gnome-terminal not
all the time but regularly and it is immediately noticeable when
editing.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package:
Sorry, "appear *behind* the Ubuntu dock" the
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1835706
Title:
Extensions don't load in gnome-shell
gnome-shell-extension-workspaces-to-dock
universe, version: 51-1
When active, the Activities and Application menus stop working, incl.
Super key. In addition the window management breaks, windows appear
being the Ubuntu dock.
--
You received this bug notification because you are a member of
With GNOME Shell 3.33.91:
gpaste 3.30.2-1ubuntu3 (universe)
gnome-shell-extension-suspend-button 0~git20180827-2 (universe)
Both marked as "Error loading extension" in Tweaks
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Summary changed:
- Moving file to Trash requently crashes gnome-shell
+ Moving file to Trash frequently crashes gnome-shell
** Summary changed:
- Moving file to Trash frequently crashes gnome-shell
+ Right-click file on desktop > Move to Trash frequently crashes gnome-shell
--
You
Public bug reported:
In 19.04 Disco fully up to date. Reproduced on two different machines:
1. Log into Wayland session (did not try with X)
2. touch ~/Desktop/testfile
3. Right-click testfile on Desktop > Move to Trash
-> gnome-shell crashes in around 50% of instances in my case. I did not
I reported this upstream here: https://github.com/hughsie/lvfs-
website/issues/335
It looks like it's related to the metadata being too big.
** No longer affects: appstream-glib (Ubuntu)
** Bug watch added: github.com/hughsie/lvfs-website/issues #335
That message is coming from appstream-glib, somewhere around here:
https://github.com/hughsie/appstream-
glib/blob/843caabdeca6ae15f400f38536bc666340c30465/libappstream-glib/as-
store.c#L2329
I would recommend to start out with trying a newer appstream-glib to see
if that helps.
** Also affects:
(I still get the "Failed to apply DRM plane", but the immediate
unrotation does not happen anymore. This is at least in Wayland, could
not check X)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I cannot reproduce this anymore on Ubuntu 19.04, gnome-shell 3.32
--
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/1797174
Title:
[Dell XPS 15 9575] gnome-shell unrotates
I had libgegl-0.4-0 from Otto's PPA that was claiming to be newer than
the version in Disco. I used Synaptic to force downgrade to the Disco
version, now everything works fine. It could be this or you have an old
version of libgegl in /usr/local/bin from another install.
--
You received this bug
Public bug reported:
Version: 3.28.3
I managed to format my system drive to NTFS by accident, the UI did
nothing to prevent it or even warn me.
Last week I was formatting a thumb drive to NTFS. I forgot to select it
and my system NVME was selected. I noticed it after I created the NTFS
** Changed in: libxmlb (Ubuntu)
Status: Triaged => Fix Released
** Changed in: libxmlb (Ubuntu Disco)
Status: Won't Fix => Fix Released
** Changed in: libxmlb (Ubuntu)
Assignee: Robert Ancell (robert-ancell) => Mario Limonciello (superm1)
--
You received
FYI, fix for Wayland: bug #1816808
--
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/1760399
Title:
New On-screen keyboard does not appear automatically when selecting
Sorry for spamming, I should have clicked the source link on OMGUbuntu,
experimental is apparently expected:
https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-
in-wayland-landed/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
(Note that adding scale-monitor-framebuffer to experimental mutter
settings was already the workaround mentioned in Bug Description, so not
new)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I have this now on Disco in Wayland and with update to mutter 3.32
(incl. proposed, except gnome-settings-daemon at 3.31.91-1ubuntu1), but
apparently I had to add scale-monitor-framebuffer to the gsettings key
org.gnome.mutter.experimental-features (as mentioned by
I can confirm on Disco that this is definitely better, but not
completely solved for me:
gnome-settings-daemon 3.30.2-2ubuntu1
Screen Keyboard is off in Universal Access settings
* Good in both X and Wayland:
1. Touch Activities on panel
2. Touch "type to search" box
-> OSK comes up.
3. Close
(This is in Disco, nautilus 1:3.31.90-1ubuntu2)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1720089
Title:
Desktop isn't part of "places" (left bar) in artful
To manage
Confirming what Olivier wrote, I see it in X but not Wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1720089
Title:
Desktop isn't part of "places" (left bar) in artful
To
To me this sounds like it's probably Gnome Software not fwupd.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
Yes, confirmed this is still fixed in 3.18.1-0ubuntu4.18.04.8.
** 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
I just downgraded an XPS 9370 and then upgraded it again using gnome-
software 3.28.1-0ubuntu4.18.04.8 and it works like I expected.
** Tags removed: artful verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug
Oopsie, indeed the crash on lid close is gone after disabling extensions. Even
the very act of turning off the overall extension switch in Tweaks crashes the
session.
Will figure out the culprit extension then.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You
@Joe, at least in Wayland (did not test in X yet) the touch does not
register when I touch anywhere right at the edge of the display. That
goes for the whole perimeter of the display. E.g., srollbars of
maximized windows on the right, dock launchers on the left, and the
Gnome panel menu top right
@Joe: Can you confirm that you see the unrotation behavior and the log entry,
"gnome-shell[5422]: Failed to apply DRM plane transform 1: Invalid argument"
only in a Wayland session?
I just realized that this is the case for me. In an X session, the
rotation works perfectly whatever the display
Public bug reported:
In an X session, suspend and wakeup works when initiated either by lid
close or from panel menu.
In a Wayland session, suspend and wakeup works only when initiated from panel
menu.
However, gnome-shell segfaults when suspend is initiated by lid close.
When reopening the
** Description changed:
On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the
available scaling options in the gnome-control-center (version:
1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200,
300, and 400%. This is insufficient as 200% is too small and
iotop is showing systemd-journal writing to disk at around 1MBs while
system-monitor is running. 420 entries per seconds.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
FWIW and FYI, I cannot repro this on Cosmic with Dell XPS 15 9575
--
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/1797178
Title:
gnome-shell activities / application icon
I've upgraded on a bionic machine to 3.28.1-0ubuntu4.18.04.5.
xdg-open FirmwareUpdateLinux_00.00.07.cab opens a composite CAB file in
gnome-software now.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added:
I've tested the fwupd half of this SRU (couldn't test the gnome-software
as it's not yet in place). The fwupd half works properly.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You
I cannot confirm this on my machine. I do not know if what I see it
intended behavior, but what I see is still not what either the Gnome
2.28 release notes or the Ubuntu help say should happen.
When I enable the OSK in universal access, the OSK opens way too often but not
always when it should.
Thanks Efthimios.
I am still a little unclear about what the intended behavior is. Should it auto
open when touching a text field e.g. in Chrome? And are you using X or Wayland
and it you enable the OSK in Universal Access?
Thanks. FWIW, for me on Cosmic it is still as described in the
Thank you. I had written bug #1792813 about the sensors not being found
with kernel 4.18. This is fixed in the mainline 4.19 (see the other
report).
The incorrect automatic back rotation also happens with 4.19. However,
note that what exactly happens depends on whether the keyboard vs
display
1 - 100 of 871 matches
Mail list logo
