*** This bug is a duplicate of bug 1679903 ***
https://bugs.launchpad.net/bugs/1679903
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1679903, so is being marked as such.
^^^
I feel conflicted about letting gnome-shell just exit. It will result in some
people logging bug reports that we can't diagnose, but those will be orders of
magnitude fewer than what we see now.
So short term for 18.04, it's a good idea. Slightly beyond that, it's
going to keep hurting us
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
It looks like upstream has a "fix" coming:
https://gitlab.gnome.org/GNOME/mutter/commit/2d80fd02e76bbe17dc52072299dda92ab88c99c0
Although that will just stop the crash reports from occurring and not
fix the root cause. That may be all we need for now...
--
You received this bug notification
*** This is a duplicate of bug 1505409, but is being kept separate so as
to automatically collect duplicate reports since the stack trace
signature has changed recently. Any resolution and discussion should
occur in bug 1505409. ***
--
You received this bug notification because you are a member
Hmmm ok I cannot open the bibliography database. Every time I try, I am
informed I need to restart. Seems like I have to chase a LibreOffice
bug first.
Sorry!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Interesting perhaps that trying to start the bibliography window
required a restart of the LibreOffice window.
--
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/1762035
Title:
mutter
In my /etc/apport/crashdb.conf the offending line is no longer 23, it's
20.
Testing now
--
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/1762035
Title:
mutter crashed while
Restarting didn't help, still was informed I needed to restart. I feel
like Alice...
--
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/1762035
Title:
mutter crashed while selecting a
** No longer affects: gnome-disk-utility (Ubuntu)
** Summary changed:
- thin red lines around "Format" button in gnome-disks
+ Thin red lines around red headerbar buttons
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-disk-utility (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-themes (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
I'm seeing the same bug with red headerbar buttons in other apps. I
think colorhug-client was where I saw it last.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1763417
*** This bug is a duplicate of bug 1763878 ***
https://bugs.launchpad.net/bugs/1763878
** This bug is no longer a duplicate of private bug 1764763
** This bug has been marked a duplicate of bug 1763878
[regression] Many programs crashing at exit with assert failure:
Did some testing on bionic.
It appears to me as if the feature is designed solely for Wayland. Yes,
on Wayland with GTK_IM_MODULE unset it seems to work without issues. On
Wayland with GTK_IM_MODULE=ibus I can reproduce the issues as described
above.
On Xorg the feature works very poorly
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
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/1764643
Title:
Logout after console use freezes GUI
To manage
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=794734
Importance: Unknown
Status: Unknown
--
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/1758563
** Changed in: gnome-control-center
Status: Confirmed => Expired
--
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/1019047
Title:
Wacom settings icon is present
After having read one of Carlos' comments in the upstream issue, I
switched to a German XKB layout and was then able to type ü via the
screen keyboard.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1764763 ***
https://bugs.launchpad.net/bugs/1764763
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1764763, so is being marked as such.
Hmm.. I now see that the issue is present in 17.10 too, so it's probably
due to something else but the latest IBus changes which affected
Ctrl+Shift+U.
I also see that some extended characters work. For instance, the letters
å, ä and ö, which are in the Swedish alphabet, work for me. Weird.
--
@Jeremy: Your workaround with not setting GTK_IM_MODULE makes me think
of bug #1760308, where that would have been an alternative solution (see
comment #6). Now Sebastien fixed it in IBus instead.
To stop setting GTK_IM_MODULE would be an easy thing in im-config, of
course. I'm hesitating since
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
Public bug reported:
When in fullscreen, the buttons that should appear when hovering the
mouse cursor centered on the top of the display don't appear. They still
have the function but, as it's impossible to see them, it's not possible
to see if the button will close or minimize the session.
I'm
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-menus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-menus in Ubuntu.
Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.
The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require
Trying to reproduce on different system (laptop).
Same Ubuntu release and GNOME/my desktop system, GDM packages.
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate: 3.26.1-3ubuntu3
Version table:
***
You have been subscribed to a public bug:
I'm working on libvirt/kvm hypervisor
I user 2 bondind interfaces:
eno1 + eno2 => bond0 via "netplan" ("service" interface for hypervisor)
eno3 + eno4 => bond1 via "ifupdown" ("virtualization" interface for libvirt)
Since last upgrade (today), i got
This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.
** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
udisks2 2.7.6-2ubuntu6 "suggests" libblockdev-crypto2;
that needs to be set to "recommends" at least.
** Changed in: udisks
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in
You have been subscribed to a public bug:
Not 100% sure if this is a networkd bug or a nplan bug, but...
On new install of 17.10 systemd-networkd loops with:
Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained
I can confirm what Sebastien proposed. Installing libblockdev-crypto2 and
restarting the udisks2.service did the trick.
Also it maybe worth mention that in my case the installation of Ubuntu
18.04(beta2) performed with the new "minimal installation" option.
--
You received this bug
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
Hi Sebastien, yeah actually I did it right after reporting this bug.
Installing libblockdev-crypto2 and restarting udisks2 service made it
work!
Do you think we should categorize this under udisks2?
** Also affects: udisks
Importance: Undecided
Status: New
--
You received this bug
Glad to see that this bug is about to be squished...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
To manage
*** This bug is a duplicate of bug 1760620 ***
https://bugs.launchpad.net/bugs/1760620
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1760620, so is being marked as such.
Trying to pin this bug down, I deactivated nVIDIA's driver, reactivated
nouveau and rebooted.
Sadly, the problem still persists.
--
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/1764643
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: gjs (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1724188
Title:
gnome-software crashed with SIGSEGV in
gtk_stack_set_visible_child_name →
Gunnar, please see my comments at https://gitlab.gnome.org/GNOME/gnome-
shell/issues/109#note_98033
Can we stop setting GTK_IM_MODULE=ibus at least in the GNOME and Ubuntu
sessions?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 1724188 ***
https://bugs.launchpad.net/bugs/1724188
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1724188, so is being marked as such.
*** This bug is a duplicate of bug 1712961 ***
https://bugs.launchpad.net/bugs/1712961
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1712961, so is being marked as such.
*** This bug is a duplicate of bug 1679903 ***
https://bugs.launchpad.net/bugs/1679903
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1679903, so is being marked as such.
** Changed in: gnome-calendar (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1757058
Title:
gnome-calendar (11)
*** This bug is a duplicate of bug 1731256 ***
https://bugs.launchpad.net/bugs/1731256
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1731256, so is being marked as such.
MIR approved.
The new version synced from debian in bionic (UNAPPROVED) looks good
now, and appears to have corrected test suite issues:
18057438 | X- | volume-key | 0.3.9-4 | 6 hours
| * volume-key/0.3.9-4 Component: universe Section: misc
** Changed in:
Thanks, that's worth fixing but not really a release blocked issue,
tagging rls-bb-notfixing
** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
This bug was fixed in the package gnome-control-center -
1:3.28.1-0ubuntu1
---
gnome-control-center (1:3.28.1-0ubuntu1) bionic; urgency=medium
* New upstream release (LP: #1764591)
* Drop Build-Depends on network-manager-dev, no longer necessary
* Cherry-pick
That’s great news! Will the fix still make it into 18.04 LTS?
--
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/1419523
Title:
GVFS MTP paths are not stable
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Hi Sebastien, just gave that a try and it didn't help for me. Thank you
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1761995
Title:
Error Formatting luks device
To
Thanks, It seems I cannot reproduce.
--
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/1764436
Title:
gnome-control-center crashed with SIGSEGV
To manage notifications
the issue was in gtk and fixed in the recent update
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop
does it work if you install libblockdev-crypto2 ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1761995
Title:
Error Formatting luks device
To manage notifications
Public bug reported:
"logn" is common notation for log base n, e.g. log2(x) is log base 2 of
x.
gnome-calculator appears to always parse this notation as log(n)(x).
So, log10(2) is log(10)(2) = 2, rather than log10(2) ~= 0.301.
Arbitrary bases are already supported if the base is input as a
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
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/1764591
Title:
update
Indeed the file search feature got improved in bionic
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
I'm happy to assist in what capacity I can. Currently I'm not using the
computer for anything else, so I can format the drive and reinstall
ubuntu again, if some more details are required.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Thank you, Jeremey! It seems that this is now no longer an issue. I'm on
the Ubuntu Bionic Beaver (development branch) and updated this morning.
(April 17th, 2018).
Dropbox folders are now being indexed properly and I can search for
files within Dropbox folders.
--
You received this bug
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1762952 ***
https://bugs.launchpad.net/bugs/1762952
@Daniel, yes, this is a duplicate of this, although I never noticed the
input language changed as well! Can be closed as a duplicate.
** This bug has been marked a duplicate of bug 1762952
Switching
Yep. GNOME Shell 3.28.1 fixed this issue for me.
--
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/1758563
Title:
Blocked at gdm login screen on 18.04 if user password has a
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
>From the logs it seems that even if the locale is set to a non-english
language, the config variable xkb-keymap introduced in 17.10 is set to
'us' and Ubiquity uses this value to update the UI.
Apr 17 08:55:11 debconf (filter): <-- GET debian-installer/locale
debconf (developer): <-- GET
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu3
---
gnome-software (3.28.1-0ubuntu3) bionic; urgency=medium
* Merge change from Debian:
- Drop icon-download APT config snippet, depend on shared apt-config-icons
instead (LP: #1764589)
-- Jeremy Bicha
jibel is looking at this one but it looks like a console-setup issue at
this point
** Changed in: ubiquity (Ubuntu Bionic)
Assignee: Sebastien Bacher (seb128) => Jean-Baptiste Lallement (jibel)
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
--
You
Thanks.
I uninstalled LIRC, just to be on the safe side.
Orca is necessary for my using the computer.
I uncommented the line #WaylandEnable=false and rebooted.
The problem still persists.
Then, without logging in graphically, I switched to tty3 (Ctrl+Alt+F3).
Logged in, executed a single command
Thanks.
Those bugs show you're using nvidia-384, which might be related.
Although I could not find anything that was obviously frozen.
If you edit /etc/gdm3/custom.conf and uncomment this line:
#WaylandEnable=false
does that fix it?
Also you seem to have a lot of these errors (in case
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 1653153 ***
https://bugs.launchpad.net/bugs/1653153
** This bug has been marked a duplicate of bug 1653153
Windows not always drawn in correct places in AO when under Wayland
--
You received this bug notification because you are a member of Ubuntu
The fix is in 3.28.1
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Fix Released
--
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/1754924
Public bug reported:
Screencast of the issue:
https://bugzilla.gnome.org/attachment.cgi?id=367080
When using DnD to open a window that might be repositioned just after
being opened causes the window not to be properly positioned nor in the
workspace spread and in the workspace thumnail.
**
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu.
https://bugs.launchpad.net/bugs/1764675
Title:
package xdg-user-dirs 0.15-2ubuntu6.16.04.1 failed to install/upgrade:
Public bug reported:
during update i get this error
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xdg-user-dirs 0.15-2ubuntu6.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
As requested, I killed both gdm3 and gnome-shell.
The bug-ids are #1764672 and #1764674 respectively.
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/1764643
Title:
Logout
the new version has been accepted
** Changed in: gtk+3.0 (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 1754445 ***
https://bugs.launchpad.net/bugs/1754445
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
it's synced now, so never mind "pre-upload"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to volume-key in Ubuntu.
https://bugs.launchpad.net/bugs/1754422
Title:
[MIR] volume-key
To manage notifications about this bug go to:
Same issue on 3.28.1 on ubuntu 18.04 and using an exchange calendar
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1573581
Title:
Showing wrong times for imported calendars
Thank you for your new comment but that bug has been closed for almost
10 years, please open a new bug instead of reopening the old one, the
issue might be different and a new report is going to include updated
information
** Changed in: file-roller (Ubuntu)
Status: New => Invalid
--
You
In that case, maybe the gdm3 (or gnome-shell) process is hung. Can you
please try forcing it to dump core in that state?
killall -ABRT gdm3
killall -ABRT gnome-shell
Then wait a while and check for crash files again.
--
You received this bug notification because you are a member of Ubuntu
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1513160.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Thank you for information. nvidia-driver-390 driver have problems too, i hope
you can fix before the 18.04 final release.
(https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1762200)
Last question; mutter 3.28.1 not released when it will release and will you put
in
** Package changed: gdm3 (Ubuntu) => mesa (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/1760201
Title:
ubuntu 18.04 GDM - missing icons and letters on login screen
Also, if anyone can reproduce the problem again, do you find nouveau
errors in your kernel log around the time of the missing rendering?
Run 'dmesg' to see it all.
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
I followed your instructions; commented out the line in
/etc/apport/crashdb.conf, reproduced the problem, but there are no
crash-files in /var/crash.
Sorry.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Well using nvidia proprietary driver is solving for me (nothing changed
in gdm3 custum.conf).
I switched to the nouveau driver when, a couple on month ago, nvidia
driver stop working with the new linux kernel version. But it seems they
have some other issue at now (i just filed a new bug report
*** This bug is a duplicate of bug 1754623 ***
https://bugs.launchpad.net/bugs/1754623
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1754623, so is being marked as such.
The problem may not be Wayland as much as forcing X allows the Nvidia
driver to work and avoids Nouveau and its bugs.
It's too late to consider changing the default. We have only 2 days to
final freeze.
** Summary changed:
- ubuntu 18.04 GDM - missing icons and letters on login screen
+ ubuntu
Seems to be related to some kind of race condition between number of
monitors changing (decreasing?), system sleep and screensaver
activation?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
It sounds like some component has crashed. Please:
1. Apply the workaround from bug 994921.
2. Reproduce the problem.
3. Look in /var/crash for crash files and then run:
ubuntu-bug /var/crash/YOURFILE.crash
4. Tell us here the ID of the new bug created.
** Changed in: gdm3 (Ubuntu)
WaylandEnable=false solved my problem. Thank you.
Ubuntu 18.04 using default xorg, why gdm using wayland?
Will you set gdm default xorg?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Does bug 1762952 explain what you see?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
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/1764642
Title:
Public bug reported:
Hello,
Ubuntu 17.10 64 bit
GNOME 3.26.2
nVIDIA GeForce GT620 driver 384.111
X-server 11.0, v1.19.5
Orca + braille enabled
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate:
1 - 100 of 106 matches
Mail list logo
