** Also affects: gnome-software (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-software (Ubuntu Eoan)
Importance: Medium
Assignee: Robert Ancell (robert-ancell)
Status: Confirmed
** Also affects: gnome-software (Ubuntu Bionic)
Importance:
** Changed in: gnome-shell
Status: Unknown => 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/1825710
Title:
Remove "Application is ready" notification
To manage
Sounds good. Thanks.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
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/1832449
Title:
Right click menu
I think gnome-shell could do better at ignoring programs being debugged.
It appears you can detect this by looking at the process state like in
/proc/PID/status. It will show:
State: t (tracing stop)
Or easier to parse: Look at /proc/PID/stat and the third field will be a
lowercase 't'.
This
Thanks for those logs. They show the problem happening immediately, as
soon as 2.5 seconds after the kernel starts.
This bug is now assigned to the kernel ('linux' component). I believe
this is a kernel bug, if not a hardware fault.
--
You received this bug notification because you are a member
Tracking upstream in: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/358
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #358
https://gitlab.gnome.org/GNOME/gnome-shell/issues/358
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/358
Oh my goodness. I just found out the culprit was the Gnome extension
"Multi Monitors Add-On". I had originally installed this extension so
that I can have the top bar on both monitors. But after disabling it,
right click menus works fine !
I'm going to file a bug report with the author of that
I'm not sure if this is relevant, but I'm adding that my laptop's
display resolution has been set to 1368 x 768 even though it supports
1920 x 1080.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Thanks for helping to resolve this problem. I've notice that it's not
just nautilus, right click menus are all other apps appear at an offset
as well. And it happens to be the offset that is the distance between
the cursor's y position and the top of the smaller monitor. Here it is
described in a
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1832449/+attachment/5270474/+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.
apport information
** Tags added: apport-collected disco
** Description changed:
I have an external monitor connected to a laptop via HDMI. If I set up
the laptop display's position like this:
https://imgur.com/oFbqnBm
And open a new nautilus windows on my external monitor (which
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1832449/+attachment/5270473/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This bug was fixed in the package gedit - 3.28.1-1ubuntu1.2
---
gedit (3.28.1-1ubuntu1.2) bionic; urgency=medium
* debian/oatches/gitlab_idle_handling.patch:
- use gitlab pr#34's patch to fix an incorrect handling of idle
callbacks, thanks Andrea Azzarone (lp: #1646762)
** Attachment added: "journalctl -b0 from successful screen activation"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.
** Attachment added: "dmesg from functional boot"
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:
Trying to build gtk+3.0-3.22.30 from source fails.
I got the source using package gtk-3-examples.
$ apt policy gtk-3-examples
gtk-3-examples:
Installed: 3.22.30-1ubuntu3
Candidate: 3.22.30-1ubuntu3
Version table:
*** 3.22.30-1ubuntu3 500
500
** Changed in: gnome-settings-daemon
Status: Unknown => New
--
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/1832374
Title:
Media keys stop working due to
** Tags added: eoan
--
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/1726129
Title:
nautilus crashed with SIGSEGV in widget_needs_widget_path
To manage notifications about this
Note that the gnome-shell-extension-no-annoyance extension exists
(presumably as a workaround rather than a solution to this bug).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
This window that keeps appearing is very annoying.
Can't a setting be created in the OS with a CheckBox gadget to
enable/disable the warning?
"blah blah is ready" is very annoying.
:-(
** Attachment added: "Screenshot"
Hi Sebastian,
This issue was partially fixed in GSD 3.30.2. See
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/45
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #415
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/415
** Also affects:
Mh, if the warning is just showing once and when you unfocus such dialog
you don't get any problem, I don't think this is an issue.
Maybe the fix would be to delay the presentation of such dialog until
the hanging window is focused?
--
You received this bug notification because you are a member
Public bug reported:
When setting window control layout to the left hand side rather than the
right, GNOME Disks (gnome-disk-utility) does not show the 'Close'
button, however the 'Minimize' and 'Maximize' buttons are still present.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package:
Hello! My first comment here on this forum. This bug consistently occurs
everytime my system is rebooted. Since I have absolutely no idea what
goes on behind the scenes, I'd like to mention that I use NVIDIA
drivers. Hoping to find a solution.
--
You received this bug notification because you
This bug occurred for me with a fresh installation of Ubuntu 19.04.
I created a new installation of Ubuntu 19.04 on a empty disk and checked the
box to encrypt the installation. After the installation I tried to change the
password and got locked out.
This is the output of sudo cryptsetup
On 2019-06-12 13:34, Sebastien Bacher wrote:
> Can you type "bt" in gdb after hitting the segfault?
New attachment.
** Attachment added: "bt-output.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+attachment/5270343/+files/bt-output.txt
--
You received this
** Changed in: gnome-shell
Status: Unknown => New
--
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/1826918
Title:
gnome-shell crashed with SIGSEGV in
Can you type "bt" in gdb after hitting the segfault?
--
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/1831356
Title:
Settings crashes when I click "Devices"(Enheter in
On 2019-06-12 08:47, Sebastien Bacher wrote:
> Can you use gdb to get details on the segfault?
Please see attachment.
** Attachment added: "g-c-c_segfault_gdb-output.txt"
disco in queue, will sync eoan once lp picks it up
--
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/1832457
Title:
[SRU] 2.60.4
To manage notifications about this bug go to:
The issue is in python-defaults, maybe on systemd where the default
python was changed
Setting up python-gtk2-dev (2.24.0-5.1ubuntu2) ...
File "/usr/bin/pyversions", line 20
except IOError, msg:
** Package changed: pygtk (Ubuntu) => python-defaults (Ubuntu)
** Changed in: python-defaults
the issue was a local I/O problem rather than a package bug
** Changed in: pygtk (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in Ubuntu.
https://bugs.launchpad.net/bugs/1317884
Title:
** Changed in: pygtk (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in Ubuntu.
https://bugs.launchpad.net/bugs/1615438
Title:
package python-gtk2-dev 2.24.0-3ubuntu3 failed to
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Public bug reported:
On ubuntu 18.04 using gdm3 and gnome-shell, getting into virtual
consoles works well when the laptop is not on the docking station. After
putting it on the docking station (getting then 2 monitors), using
CTRL+ALT+F{3,4,5,6} freezes the GUI. I can come back to GUI using
*** This bug is a duplicate of bug 1808979 ***
https://bugs.launchpad.net/bugs/1808979
** This bug has been marked a duplicate of bug 1808979
package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade:
installed python-gtk2-dev package post-installation script subprocess returned
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pygtk (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in Ubuntu.
*** This bug is a duplicate of bug 1808979 ***
https://bugs.launchpad.net/bugs/1808979
** This bug has been marked a duplicate of bug 1808979
package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade:
installed python-gtk2-dev package post-installation script subprocess returned
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 1832449
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for your bug report. What Ubuntu version do you use? Are you
on wayland or xorg session?
** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New =>
OK. I will not reopen this bug.
Instead I have separated bug 1826918. Please look there.
--
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/1813716
Title:
gnome-shell crashed with
Ooh...
It seems the explanation is that the above versions were short lived.
The subsequent version 3.32.2-1ubuntu1 is experiencing the crash still
in eoan:
https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f
--
You received this bug notification because you are a member
Weird I can still reproduce this crash using mutter master from git
(https://gitlab.gnome.org/GNOME/mutter/issues/629), but there is no
evidence of Ubuntu crashing since the above fix.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #629
This sounds like it's probably a problem at a lower level than nautilus,
but I don't know that stack well enough, so I'm just moving this bug a
bit closer to where it ought to be.
** Project changed: launchpad => nautilus (Ubuntu)
--
You received this bug notification because you are a member
This is a continuation of bug 1813716, which wasn't quite fixed.
** This bug is no longer a duplicate of bug 1813716
gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay →
detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref →
ObjectInstance → → release_native_object
You have been subscribed to a public bug:
I have an external monitor connected to a laptop via HDMI. If I set up
the laptop display's position like this:
https://imgur.com/oFbqnBm
And open a new nautilus windows on my external monitor (which I've set
to be primary), the right click context menu
Public bug reported:
[ Description ]
New stable release in the 2.60 series.
[ QA ]
Upstream release, so QA already performed by maintainers
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.
Pretty
** Changed in: evince
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1832442
Title:
Evince Not printing Font
To manage notifications about this bug
18.04.2LTS as guest of course. Here is dmesg listing after I bring up
the gnome via safe mode on the local WS 15 Pro.
** Attachment added: "dmesg_wspro15.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+attachment/5270271/+files/dmesg_wspro15.txt
--
You received this bug
This workaround of commenting out the Wayland does not work on both my
setups, W10 Enterprise running WMvare 15 Pro and remote ESXi 6.5. with
18.04.2LTS host.
I am able to login via safe mode -> login as root -> return to grub ->
resume and keep VMware in windowed mode. Attempt to switch to full
** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1165
https://gitlab.gnome.org/GNOME/evince/issues/1165
** Also affects: evince via
https://gitlab.gnome.org/GNOME/evince/issues/1165
Importance: Unknown
Status: Unknown
** Tags added: bionic
--
You received this bug
** Description changed:
The attached pdf file only prints the lines of the form all text are
- missing. I also attached a scan of how the printout looks.
+ missing. I also attached a scan of how the printout looks. The problem
+ do not show at first start, some factor during the day is the
Can you use gdb to get details on the segfault?
--
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/1831356
Title:
Settings crashes when I click "Devices"(Enheter in
Public bug reported:
The attached pdf file only prints the lines of the form all text are
missing. I also attached a scan of how the printout looks.
Document was created on Google Sheets. The print process created the
pdf.
If I print the document via Firefox it prints correct.
System Info
55 matches
Mail list logo
