*** This bug is a duplicate of bug 723841 ***
https://bugs.launchpad.net/bugs/723841
** This bug has been marked a duplicate of bug 723841
file-roller crashed with SIGSEGV in
egg_tree_multi_drag_button_release_event()
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 723841 ***
https://bugs.launchpad.net/bugs/723841
** This bug is no longer a duplicate of bug 2037767
file-roller crashed with SIGSEGV in
egg_tree_multi_drag_button_release_event()
** This bug has been marked a duplicate of bug 723841
file-roller
Any update available on this bug report?
--
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/2043591
Title:
Starting gnome-control-center resets icon theme
To manage
Public bug reported:
Release: 23.10
Expect to happen: Run a flatpak app and it displays on the screen
What happens instead: Some flatpaks fail to display when using Wayland and
Nvidia card. The icon for the app shows in the dash and I can interact with the
icon (i.e. right click and quit) but
This bug is still present in Ubuntu 23.10
--
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/1968213
Title:
Icon theme reverts to Yaru when entering Appearance settings
Public bug reported:
How to reproduce this bug:
1. Install a new icon theme like the papirus icon theme
(https://github.com/PapirusDevelopmentTeam/papirus-icon-theme) or the Tela icon
theme (https://github.com/vinceliuice/Tela-icon-theme) and activate it via
Gnome Tweaks.
2. Click on the
Public bug reported:
Archive Manager (file-roller) often crashes when I open Qt source
archives. I usually build (most of) Qt modules myself from the source
archive "qt-everywhere-src-X.Y.Z.tar.xz". When I open the archive to
select the directories I wish to extract, Archive Manager often crashes
I have the same issue.
22.04 LTS (though Pop!_OS 22.04)
Display server: X11
Display driver: Nvidia 515.48.07
gjs is already installed.
OS is installed on an iMac 14,2 from late 2013 (not dual boot, Linux is
the sole operating system)
‘xset dpms force off’ does not turn off the monitor, it just
Public bug reported:
rlsyslogd is a runaway process hogging one of my CPUs.
The following is repeatedly logged in my syslog:
Aug 22 20:41:00 alonzo gnome-shell[369997]: The offending callback was
SourceFunc().
Aug 22 20:41:00 alonzo gnome-shell[369997]: Attempting to run a JS callback
during
I confirm the fix. My system: Intel i5-3570K CPU / Ivy Bridge / Mesa Intel® HD
Graphics 4000 (IVB GT2)
Pre-release updates(jammy-proposed): enabled
Ubuntu 22.04 fresh install + gstreamer1.0-vaapi(1.20.1-ubuntu1) +
libgstreamer-plugins-bad1.0-0(1.20.3-0ubuntu1)+ ubuntu-restricted-extras
Video
I confirm the fix. My system: Intel i5-3570K CPU / Ivy Bridge / Mesa
Intel® HD Graphics 4000 (IVB GT2)
Ubuntu 22.10 live CD 2022-06-25 + ubuntu-restricted-extras(gstreamer1.0-vaapi
version 1.20.3):(Install gstreamer1.0-vaapi produces video only, no sound)
Wayland: works
X11: works
Ubuntu 22.04:
Public bug reported:
This crash happens when starting Gnome Extensions.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
I believe I have the same behavior with different hardware, and no
docking station: I have a Dell Latitude 7480 which I typically use with
an external monitor (via HDMI), USB mouse, and USB keyboard, while the
laptop sits behind a desk with its lid closed.
Up until April 2021, I was running
I should probably clarify - I know that these three packages were part
of the core extensions. However, I noticed that the timestamps for all
of the core extensions were the same _except_ for those three. I
reinstalled the gnome-shell-extensions package make sure they were
correct, but those three
This issue appears to be resolved for me.
I used `apt purge gnome-shell-extensions` to remove gnome-shell-
extensions and noticed that 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-
d...@ubuntu.com', and 'desktop-icons@csoriano' remained in /usr/share
/gnome-shell/extensions/. I manually removed
In my original bug report (https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1924625) I was asked to remove many extensions;
however, many of those extensions are ones that I installed at one time
but have since removed and they do not appear under ~/.local/share
Before removing any extensions, I followed the instructions in #11. The
bug report can be found here: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1924753.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Public bug reported:
This is a repeat of bug 1886059 with "MUTTER_SYNC=1" added to
/etc/environment.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
Public bug reported:
Yesterday (2021-04-14) I ran apt update/upgrade, then rebooted my laptop
overnight. With the upgrade Linux 5.4.0-71 was installed. Now I have an
issue where gnome-shell restarts repeatedly. Looking in the logs, I see
that gnome-shell is core dumping when this occurs. I have
Any idea when Focal will be completed ?
Regards,
Eric
--
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/1865226
Title:
gdm-smartcard pam config needs to be updated for Ubuntu
(I have ping sil2100 internally for him to provide his 2 cents on this
bug.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to be
Lukasz (sil2100) can we have your SRU team input on this bug with regard
to Bionic/18.04lTS ?
--
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/1865226
Title:
gdm-smartcard pam config
The problem goes away after the screen times out and I have to log back
in.
--
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/1896091
Title:
[i915] Noise-like lines of graphics
I'm on 20.10 using KDE, 5.8.0-26-generic, on a dell xps 13 2-in-1 and
the problem is rather severe.
--
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/1896091
Title:
[i915] Noise-like
uot;
I think we should 'mimic' this (at least as a starting point) without
the selinux and other RHEL specific bits.
- Eric
--
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/1865226
Title:
# git clone https://gitlab.gnome.org/GNOME/gdm.git
# find . -name "gdm-smartcard*"
./data/pam-arch/gdm-smartcard.pam
./data/pam-redhat/gdm-smartcard.pam
./data/pam-exherbo/gdm-smartcard.pam
./data/pam-lfs/gdm-smartcard.pam
It seems like Ubuntu/Debian will have to start by having a 'compatible'
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Medium => High
** Also affects: pam (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Bionic)
Importance: Undecided
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Low => Medium
--
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/1865226
Title:
gdm-smartcard pam config needs to be updated for Ubuntu
It has been brought to my attention by a UA customer that they are
suffering from which seems a similar situation:
"
Our only currently working SmartCard access from Linux, over SSSD, to AD, is on
RHEL7.
I was able to get SSH access on Ubuntu 20.04LTS, after adding
"ad_gpo_access_control =
I am seeing the same issue on 18.04.5 LTS
--
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/1766230
Title:
Strange window matching behaviour between Slack and Chrome
To manage
This happened to me just now on a fresh installation of 20.04. Exactly
as reported - first attempt at calibration with a Spyder 3 fails, on the
second attempt gnome-control-center crashes hard.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
For me it affects IMAP mail retrieval from imap.aol.com.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake:
Thanks for letting me know. Is it advisable to provide any of the data
collected here to a third party?
--
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/1872461
Title:
Nevermind. I figured out that if I hover over the message text it is
hidden so I can see the file names.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
** Attachment removed: "Screenshot of issue"
Public bug reported:
Selecting one or more files in nautilus shows a message at the bottom
right (i.e. 6 folders selected (containing a total of...). This message
overlays the name of the file or folder items at the bottom of the
window making it impossible to see the names. See attachment to see
Public bug reported:
Steps to reproduce:
1. Create a new file in the folder "~/Desktop".
2. Right-click -> Properties -> change the icon to some other icon from
/usr/share/icons/Yaru/48x48.
3. Close the "Properties" dialogue.
When viewing the Desktop folder in Nautilus directly, the icon is
** Tags added: theme
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1853185
Title:
Evolution dark theme + 'save' imposes dark theme in message
To manage notifications about
** Attachment added: "Screenshots of a message being sent and received without
dark formatting; Screenshot of a message being saved and reopened with dark
formatting"
Public bug reported:
1)The release of Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
2)The version of the package
evolution:
Installed: 3.28.5-0ubuntu0.18.04.1
Candidate: 3.28.5-0ubuntu0.18.04.1
Version table:
*** 3.28.5-0ubuntu0.18.04.1 500
500
Removed incorrectly attached file and attached correct screenshot of the
issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1853185
Title:
Evolution dark theme + 'save'
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1832138
Title:
Login screen never appears on
The testing phase where the kernel will land in bionic-proposed pocket is due
around :
08-Jul - 19-Jul Bug verification & Regression testing
This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.
- Eric
--
You received this bug notifica
Just got the 2 required ACK from kernel team for the patch I have submitted.
Everything looks good for the patch to be part of the next kernel cycle as
described in previous comment.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Todd, The fix will land in the next kernel cycle.
--
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/1832138
Title:
Login screen never appears on vmwgfx using bionic kernel 4.15
To
kernel-team archive ML:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland,
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
the testing phase of bionic-proposed in a couple of weeks.
- Eric
** Tags added: sts
--
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/1832138
Title:
Login screen never appears on vmwgfx
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Great for the quick feedback.
I have until June 26th to submit the patch for the next cycle[0]
It's giving me a couple of more days to get other impacted users
feedback.
[0] - https://kernel.ubuntu.com/
- Eric
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Detailled instructions on how to use my ppa :
$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic
then reboot, and once login you can confirm if
** Description changed:
+ [Impact]
+
+ With most recent version of mutter installed.
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive)
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at
After building and testing:
"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"
the above seems to do the trick ^ which will make the SRU easier (only one
commit).
I just don't know why the kernel git bisect testing found another commit, but
I already did that test ^ using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.
But based on last duflu update, I as I said I will now give a try again
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.
--
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/1832138
Title:
Login
to pick 'vmwgfx' video kernel driver. (you can confirm with 'lspci
-nnvv' command.
4) apt-get dist-upgrade
Then reboot and the login screen won't be shown again using v4.15 kernel.
Switch to 4.18 will work.
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really
as an fyi ...
It has been brought to my attention that this could impact other system
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce
behaviour change and break the interaction with certain part of the 4.15 kernel.
Do we know if the recent point
of if we identify the offending userspace change, then we can look at
the kernel again and try to find what bit are missing, and if we limit
the kernel change then maybe the side-effect won't be present too.
I think the next step is really to find what userspace change started
all this so we can
or if we identify the offending userspace change, then we can look at
the kernel again with and try to find what bit are missing, and if we
limit the kernel change then maybe the side-effect might not be present
again. (assumption here)
I think the next step is really to find what userspace
option (since a kernel fix might be not end up being
trivial) does a revert of the change could be a possibility here ? or
else.
Ideally, I agree I would have prefer to fix the kernel and I'm also
going to pursue that direction, but just looking other avenues in case
of ...
Thanks
- Eric
The patchset is significant already without knowing yet what is missing to
address the side-effect.
I would need kernel team review/approval before thinking to SRU this into
Ubuntu 4.15.
I can't SRU this as-is, now knowing this will introduce a regression.
I'll keep you guys posted.
- Eric
Do you have the same display resizing situation with the hwe kernel 4.18
?
--
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/1832138
Title:
Login screen never appears on vmwgfx but
My test kernel can be found here, if one want to test:
sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update
version: 4.15.0-53.57+hf231164v20190618b9
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
It's working if I apply the whole chain of commit on top of Ubuntu-4.15
I'll need to talk with kernel team and see if this is feasible for an
SRU.
52a59da2c439 drm/vmwgfx: Send the correct nonblock option for atomic_commit
cfffdaad3db9 drm/vmwgfx: Move the stdu vblank event to atomic function
This commit has most likely other 'drm/vmwgfx' commit deps. I'll work at
finding what other bits are missing.
--
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/1832138
Title:
Login
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I'll do my best to provide a test kernel by tomorrow, for impacted user
to test, and confirm it works before I submit it to the Ubuntu kernel
team.
Stay tuned.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't.
So the kernel bisection is completed and found the right good commit
which is:
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f
--
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/1832138
Title:
Login screen never appears on vmwgfx
wbug: With Bug
wnbug: With No Bug
git bisect start '--term-old=wbug' '--term-new=wnbug' '--'
'drivers/gpu/drm/vmwgfx'
# wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18
git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254
# wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a]
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
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/1832138
Title:
Login screen never appears on vmwgfx but
"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.
--
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/1832138
Title:
Login screen never appears on
Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.
I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f"
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
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/1832138
Title:
Login screen ne
e now know the fix is amongst the commits listed above ^
- Eric
--
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/1832138
Title:
Login screen never appears on vmwgfx but setting WaylandEn
Thanks Pat.
Glad you had the same result as I did.
I will start the kernel bisect to find out the commit which introduce the fix
and confirm my potential good candidate that I found by doing a git log
inspection.
Will keep you guys posted.
--
You received this bug notification because you
I marked this bug affect the kernel 'linux' project, but I can't 'target
to series' and choose Bionic, it's not in the option list (something
went wrong with that bug I think, but we can figure this out later
(when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
I marked this bug affecting the kernel 'linux', but I can't 'target to
series' and choose Bionic. It's not in the option list anymore
(something went wrong with that bug I think, but we can figure this out
later (when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
*** This bug is a duplicate of bug 1832138 ***
https://bugs.launchpad.net/bugs/1832138
Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but I need to run a bisection to confirm my assumption :
can someone impacted try v4.18 hwr kernel ? and let me know if it works
fine (without workarounds) just like it did for me ? I will perform the
kernel bisect next week to see what v4.15 is missing that 4.18 has to
fix this bug.
--
You received this bug notification because you are a member of
I reported the exact same problem and was able to reproduce.
Only using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but need to run a bisection to confirm my assumption :
commit
my bug report :
https://bugs.launchpad.net/bugs/1832903
--
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/1832138
Title:
Login screen never appears on vmwgfx but setting
I was able to reproduce the problem with 4.15.0-51, but problem seems to
be gone using the hwe kernel 4.18.0-21-generic.
I'll do a kernel bisection and try to find the commit which fixes the situation.
I'll also ask another impacted user to confirm if v4.18 works fine too, to
double-check my
Public bug reported:
After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
screen doesn't work if 'Wayland' is in use (default) and if video kernel
driver is 'vgwfx'.
It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of
Hi Marco,
No, the warning/dialog shows repeatedly.
I think if I'm debugging a program, ubuntu and gnome-shell should never
tell me the window is not responding. I might focus the window to use
it, or to set it above all others so I can watch it.
Thanks
--
You received this bug notification
Public bug reported:
I believe this is a regression for
#1740869 is not responding window is constantly showing when
debugging a program
I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
this window shows up and I can't get it to stop asking me to close the
program.
I'm also affected by this bug
➜ ~ debsums gnome-control-center
/usr/bin/gnome-control-center OK
/usr/lib/gnome-control-center/cc-remote-login-helper OK
/usr/lib/gnome-control-center/gnome-control-center-search-provider
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546
The same thing just happened to me after an update.
Running `sudo kbd_mode -s` fixed it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Daniel,
As requested, Here is the prevboot.txt file. Please let me know if
there's anything else I can do to assist. Thanks.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824661/+attachment/5255919/+files/prevboot.txt
--
You received this bug
https://launchpad.net/ubuntu/+source/gdm3/+publishinghistory
Deleted Bionic proposedmaingnome 3.28.3-0ubuntu18.04.5
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
@vicamo,
Seems like you are experiencing the same problem as I experience when being on
VT-1.
Which was part of the reason why we SRU'd this change to avoid gmd3 to use VT-1
by default.
The problem can't be reproduce using other VT.
Seems like something acquires VT-1 (systemd ? gdm3 ?) and
** Tags added: sts
--
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/1637988
Title:
gvfsd-nfs not present in gvfs-backends, why?
To manage notifications about this bug go to:
Uploaded in bionic by desktop team. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1817738
Title:
Can't change virtual terminal when auto-login is enabled
To manage
Note: Desktop team kindly offered to update the vcs and do the upload in
bionic on my behalf.
Thanks !
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
#
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
#
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
#
1 - 100 of 931 matches
Mail list logo
