I have no idea if this is still an issue but this is a very old bug
report. I use MATE and it works fine there. Assuming fixed.
** Changed in: gnome-session (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** Bug 398698 has been marked as a duplicate of this bug. ***
--
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/1767454
Title:
"Other Locations" does not automatically find Samba
3.18.7 is way too old at this point. Please upgrade if you can.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1507764
Title:
metacity crashed with signal 5 in _XEventsQueued() ;
Public bug reported:
First I thought nothing at all happened, but it turns out the loopback device
is created, only this is not visible as Nautilus hides these by default. When I
used nemo though or in Nautilus on 'other places' they are shown and are
mounted if clicked on manually. syslog
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
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/1792807
Title:
Login screen freeze
To manage notifications
1. $ sudo vim /etc/default/grub
2. removed "nomodeset" (leaving emptry string for GRUB_CMDLINE_LINUX
3. $ sudo update-grub
4. $ sudo update-initramfs -u
5. $ sudo vim /etc/gdm3/custom.conf
6. remove # in front of "#WaylandEnable=false", leaving "WaylandEnable=false"
(under "[daemon]")
7. sudo
Stephane, you should file a new bug using “ubuntu-bug
/var/crash/_usr_bin_metacity.1000.crash” command (or whatever path to
.crash file is), attaching the crash file to existing bug does not help.
Also, we do not always have resources for supporting old Ubuntu
versions. Please upgrade to 18.04
I was just hit again with it today, with metacity 1:3.18.7-0ubuntu0.3 on
16.04.
Here is the crash dump.
** Attachment added: "_usr_bin_metacity.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+attachment/5189891/+files/_usr_bin_metacity.1000.crash
--
You
If this bug is about a snap package you should probably open a report
with the snap author.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1791454
Title:
*** This bug is a duplicate of bug 1694076 ***
https://bugs.launchpad.net/bugs/1694076
** This bug has been marked a duplicate of bug 1694076
No error message on firmware update fail
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Since this was in 3-26 and now at 3-28 in bionic, closing this issue.
** Changed in: gnome-software (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-software in Ubuntu.
** Tags added: nvidia
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
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/1792843
Title:
GDM lock screen will
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1792843/+attachment/5189875/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Note: for now I have worked around this by preventing my console from
being locked when the display sleep kicks in. Not ideal but at least I
don't have to reboot after every sleep.
Also, probably not relevant, but this was happening before I switched to
bionic app sources (which I needed for some
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
So yesterday I got the prompt to upgrade my 16LTS system to 18. This
caused a number of issues, but the most frustrating issue out of many
has to be this one.
After a period of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1792843/+attachment/5189876/+files/ProcEnviron.txt
--
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/ubuntu/+source/file-roller/3.30.0-1
** Changed in: file-roller (Ubuntu)
Importance: Undecided => Low
** Changed in: file-roller (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
did anyone try to test mutter 3.30 to see if the issue is fixed or not
I don't want to be shocked that the issue isn't fixed when 18.10 is
released then I'll have to wait for another 6 months for the fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1791433
Title:
Path traversal vulnerability
To manage
Tested this on my system and this has solved the issue for me.
--
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/1767918
Title:
Login password from GDM is shown in plain text on the VT1
Same issue here. Filled up hard drive pretty quickly and I have a 512GB
SSD
Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #0 0x7ffe78ba8ab0 I
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f49884c7780 @ 273)
Sep 16 11:15:27 brix-pro org.gnome.Shell.desktop[26988]: #1
** Changed in: zsh (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 in favor of pcre2
To manage
** Changed in: wget (Ubuntu)
Status: New => Triaged
** Changed in: wget (Ubuntu)
Assignee: Noël Köthe (noel) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
*** This bug is a duplicate of bug 1767918 ***
https://bugs.launchpad.net/bugs/1767918
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1767918, so it is being marked as such. Please
This issue has been fixed upstream. It requires fixes in both gnome-
software and fwupd.
gnome-software fix (on the Gnome Software 3-28 branch):
https://gitlab.gnome.org/GNOME/gnome-software/commit/057eea7cc03d647544b5819ff37951f7bfffb77e
fwupd fix (on the 1_0_X branch):
Public bug reported:
Ubuntu 18.04.1 LTS
gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
Version table:
*** 3.28.2-0ubuntu1.4 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu
** Package changed: xorg (Ubuntu) => gstreamer0.10 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1792900
Title:
help
To manage notifications about this bug go to:
** Package changed: gnome-session (Ubuntu) => firefox (Ubuntu)
--
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/1792910
Title:
Firefox doesn't use the session's theme
To
You have been subscribed to a public bug:
root@chika:~# gst-launch-0.10 tcpclientsrc host=10.0.0.240 port=5000 !
multipartdemux ! jpegdec ! v4l2sink device=/dev/video0
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element
Could you please tell me how to change the setting you mentioned
earlier? Thanks.
I should have said this earlier, but this bug is pretty much the same as
this bug (https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1589240). I read a comment that said a new bug should be
filed, so I
wget builds and works with pcre2 in Debian (uploaded). I cannot change
the Status to Triaged. Maybe somebody with higher privileges can change
the wget status of this bug to Triaged. thx.
** Changed in: wget (Ubuntu)
Assignee: (unassigned) => Noël Köthe (noel)
--
You received this bug
** Attachment added: "Screenshot from 2018-09-17 11-24-08.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1792910/+attachment/5189794/+files/Screenshot%20from%202018-09-17%2011-24-08.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Public bug reported:
Firefox doesn't use Adwaita's theme for it. See the screenshot.
I don't use vanilla GNOME on other distributions so I'm not entirely
sure what the correct behaviour is but pretty sure Firefox is not
supposed to be using the Yaru(?) theme? I have the communitheme snap
(0.1
screenshot of how it looks like right after powering it on from
suspend/sleep mode. (tty2)
** Attachment added: "screenshot of how it looks like right after powering it
on from suspend/sleep mode. (tty2)"
I'll try this first thing I get home!
Can I run the "sudo update-initramfs" during nomodeset? Or should I
remove "nomodeset" first and start in recovery mode? Since otherwise, I
am not able to get a command line.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Please try:
1. Remove "nomodeset" from your kernel command line and `sudo update-
initramfs`; then
2. Edit /etc/gdm3/custom.conf and uncomment the line:
#WaylandEnable=false
3. Reboot
Can you log in now?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You
well when I execute this command a window pops up saying information is
being collected that may help developers to fix this problem! Then it
shows a summary and request my permission to send the collected data
which I press send...
The first time I executed the command, it asked for permission
well when execute this commands a windows pops up saying information is
being collected that may help developers to fix this problem! Then it
shows a summary and request my permission to send the collected data
which I press send...
The first time I executed the command, it asked for permission
** Description changed:
Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is
frozen. I tried both gdm3 and lightdm login managers, with either I
don't get into the system.
I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD
Graphics 2000. I
Still can reproduce this problem with 18.04.1.
** Changed in: gnome-calculator (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
Thanks.
Our next option is to try attaching a few more .crash files to this bug.
Maybe one or two will be more human-readable. So I will make this bug
private from now on so you can do that with some security...
** Information type changed from Public to Private
** Changed in: gnome-shell
Hi Daniel,
I tried with uncommenting WaylandEnabled=false earlier. Then the login
screen remains totally Black on both monitors.
Had to restore by disabling gdm and using lightdm again.
I'm happy to try other suggestions!
Kind regards, Floris
Op ma 17 sep. 2018 09:55 schreef Daniel van Vugt <
OK, let's use bug 1697641 for Chromium. This bug is about GEdit only
now.
** Summary changed:
- On-screen keyboard doesn't work outside of Ubuntu's text fields
+ On-screen keyboard doesn't work for GEdit
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification
That command did not seem to work. It should have added some attachments
to this bug.
Please try again:
apport-collect 1792437
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
Can you please run this command on the machine to send us more
information?
apport-collect 1792702
** Summary changed:
- gnome-shell filling /var/log/syslog
+ gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has
been already finalized. Impossible to set any property
Public bug reported:
Currently, the default value of max-conns-per-host libsoup property is
used, which causes dav backend lockups if two files are opened.
see:
https://gitlab.gnome.org/GNOME/gvfs/commit/7b991137b8a820f018ddaa970d54f91d1f411a0f
I've managed to fix the problem by changig the
Chromium is a special case, you'll have to force-enable accessibility to get
the OSK to show up.
See
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1697641/comments/7.
For other applications (including gedit and libreoffice), the OSK should
show up if you enable the OSK in the
** Bug watch removed: Debian Bug tracker #908769
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908769
--
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/1788691
Title:
** Package changed: xorg (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/1792798
Title:
gdm3 will start in a new tty after suspend
To manage notifications
** Summary changed:
- Xorg freeze
+ Login screen freeze
** Package changed: xorg (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/1792807
Title:
Verification done as package is installable from proposed.
No further tests are needed here.
** 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
You have been subscribed to a public bug:
I'm not sure if there is any related info in log files because there is
no actual crash or error messages.
Im using Ubuntu 18.04 and Gnome3 on Xorg. Also, I have a NVidia GT520M
with nvidia-390 driver installed through ubuntu-drivers utility. Cant
You have been subscribed to a public bug:
Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is
frozen. I tried both gdm3 and lightdm login managers, with either I
don't get into the system.
I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD
Graphics
BTW - I'm running Kubuntu, and doing the upgrade with kubuntu-devel-
release-upgrade works just fine without needing to update appstream to
0.12.2 first.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
It sounds like this problem may be limited to Wayland sessions (which
includes the login screen). Please try this workaround next time you
install 18.04:
Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line:
#WaylandEnable=false
Then reboot.
** Tags added: multi-monit radeon
** Package changed: xorg (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/1792857
Title:
Mouse pointer is the wrong size after resuming from
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1792843
When reporting bugs in the future please use apport by using 'ubuntu-
You have been subscribed to a public bug:
Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
This renders 18.04 useless. Till this is solved will have to stick with
16.04. i.e. this is a pretty critical bug!
After a fresh install from DVD first got a freeze on login screen
You have been subscribed to a public bug:
After resuming from suspend, but mouse pointer is the wrong size when
located in some parts of the screen. Specifically, when mousing over the
left or top bars of the UI (not the desktop or any running programs),
the pointer is too large. A workaround is
** Changed in: gedit (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Have the same issue upgrading from bionic to cosmic. Updating appstream
to the version from cosmic workedaround the problem.
Please backport fix to bionic so that other people will be able to
upgrade using the Ubuntu normal upgrade process.
--
You received this bug notification because you are
61 matches
Mail list logo
