Seemed to work when I tested it yesterday (I do not always have access
to the test set-up). So assuming fixed. 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/1803319
Sounds reasonable. Thanks for letting me know.
--
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/1803319
Title:
GNOME Shell task bar menus not updated with external monitor primary
Please let me know when there Ubuntu packages I can test. I have
upgraded to 19.04.
--
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/1803319
Title:
GNOME Shell task bar menus not
Public bug reported:
My set-up: a laptop with an internal screen open and scaled to 150% and
an external monitor at 100% set to act as the primary screen. When I
open the menus in the GNOME Shell task bar (calendar or settings/log-
out/etc menu) they are displayed but not updated when I mouse
After rebooting into 18.10 this morning this seemed to work. I will
assume it is fixed, close the bug and re-open it if necessary.
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Public bug reported:
Quite simple: I start VirtualBox or a virtual machine straight from the
build directory (without installing) and the icon in the dock is a red,
crossed-out circle. After deliberately or due to a timeout locking the
screen and unlocking it, the correct X11 property icon is
Even though 3.28 is due out after the Bionic feature freeze? What about
X.Org 1.20, which is due out a few days later?
--
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/1722725
Do you expect 3.26.3 to end up in Bionic? If not, would it be possible
to back-port the fix?
--
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/1722725
Title:
GNOME Shell
The patches are attached to gnome-bugs #788915.
--
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/1722725
Title:
GNOME Shell disabling wrong screen when docking laptop
To manage
Would it be possible to apply the upstream patches to the version in
Bionic? I am happy to install the updated packages before they hit the
repositories.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I am currently running version 1.8.4-0ubuntu0.17.10.1 of both packages
and have not seen this problem for a while. I have rebooted several
times since installing the packages.
Off-topic, but since yesterday (can't remember it happening earlier) I
have started seeing mouse button freezes after
I must admit that I have not seen this freeze for a while (unless I just
missed it among all the swap-to-death freezes I have had recently), but
I installed the packages. I did not enable proposed, I just manually
installed libinput-bin and libinput10, versions 1.8.4. I probably can't
give any
At least in my case, I think that the sensible approach is to make
wayland-server treat requests for deleted objects non-fatal, as
suggested by Pekka Paalanan in the blog post linked to above.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Just for the sake of adding a comment too... I am getting this in the following
situation. I hope the description is correct.
1) I change the display set-up on my laptop slightly too fast, e.g. close the
lid, re-open, re-close (I did that quite a bit recently trying to work out bug
patterns).
Or a third hypothesis: systemd-logind triggers a suspend on lid close if
there is no external monitor plugged in. Perhaps it looks for a while
too long like there is no monitor, so that systemd-logind suspends the
system and the GNOME Shell wayland output object disappears, causing the
xwayland
Not succeeded in reproducing this again after rebuilding GNOME Shell
with ASAN_OPTIONS=detect_leaks=0 CFLAGS="-fsanitize=address
-fsanitize=return -fsanitize=bounds -fsanitize=object-size". I do now
manage to trigger debian bug 823216 quite reliably now, with the
difference that I can log on
Thinking of it I might be confusing cause and effect here: the
unexpected suspend might be caused somehow by the xwayland and gnome-
shell crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
>From the other bug (this is getting a bit tiring):
I was able to trigger the crash pretty easily with the old library still
in use by opening and closing the lid a few times in quick succession
and then trying to type an update to this bug. After restarting I was
not immediately able to trigger
I have rebuilt libinput10 with the patch in that freedesktop.org bug
report and will see if that helps things before trying to submit
anything to launchpad.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I installed debug symbols for libinput and had a look at the core file,
and it looks very much like this:
https://bugs.freedesktop.org/show_bug.cgi?id=103298
I am missing the top frame in that stack trace, but I am guessing that
is just chance based on when I took the trace. The description of
That won't fix the outdated packages (one of them was curl...) though,
will it? And does disabled mean that Launchpad will refuse to accept
the upload even if my system tries to send it?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I checked and it was the main thread which was using CPU. Uploading a
crash report (Apport would not submit it due to a couple of outdated
packages). Note that this is on a different system with a fresh Ubuntu
17.10 install (not upgraded; but the report should tell you all that).
** Attachment
Thank you. I assume then that my failure to get a crash report was due
to the GNOME Shell process and not to the underlying mechanism. I will
just check the GNOME Shell/Mutter/whatever source next time beforehand.
--
You received this bug notification because you are a member of Ubuntu
Desktop
I will do that next time I see this. A question: is there a signal I
can send to the process (SEGV?) to trigger an Apport bug report in
/var/crash? And would that make things easier for you?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Here is a gdb stacktrace. I tried sending signal 3 to the process in
the hope that it would trigger an apport bug report, but it did not.
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+attachment/4991557/+files/gdb.txt
--
You received
I have definitely observed bug 1716160 as well, even after correcting
the GNOME settings (though it happens less often then). However this
does not match either of the two. I still do not have a good feeling
for exactly when it happens, so if you do not mind I will just update
the bug next time
Public bug reported:
I have an 11K crash report in /var/crash, which Apport refuses to
process due to a lack of "free memory to automatically analyze the
problem and send a report to the developers". So I am attaching it here
in case it is of interest. At least the question of why Apport has so
** Summary changed:
- gnome-shell assert failure: gnome-shell: libinput.c:2157:
libinput_device_destroy: list_empty(>event_listeners)
+ gnome-shell assert failure: gnome-shell: libinput.c:2157: assertion failed:
libinput_device_destroy: list_empty(>event_listeners)
--
You received this bug
Looking at the journald error log, the problem happened after Okt 17
15:27:08. I hoped that apport would take a stack trace of the gnome-
shell process, but I will probably have to do that myself when I get the
chance. Can you retrace a stack trace if the debug packages are not
installed?
--
Public bug reported:
I have been having regular system freezes after switching from using my
laptop stand-alone to waking it up on a docking station with an external
monitor. I have seen this using two identical docking station plus
monitor combinations. I am still trying to find a pattern. I
Public bug reported:
I use GNOME Terminal frequently. I tend (at least since I upgraded) to
start it from GNOME Shell's dash, using the "all applications" category.
For some reason it never makes it to the frequently used list. If it is
of interest:
$ grep terminal
Public bug reported:
I often switch between working with a docking station, closed laptop and
an external monitor, and an open laptop without docking station or
monitor. I noticed since updating to 17.10 that GNOME Shell would not
switch correctly from the setup where the laptop was being used
Update: I see that there are files in /var/crash, but they are all from
October 5. I will try deleting the GNOME Shell one and see if a new one
is created if another crash happens.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I saw something similar again today. Hard to say how similar. For some
reason Apport does not seem to be doing the automatic reporting, though
it looked like it was set up at a quick glance. I will try catching it
myself.
--
You received this bug notification because you are a member of
I overcame my laziness and restarted everything. I was just able to
reconfigure monitors without a crash, so assume this is fixed. I can
always re-open if really necessary. Thanks.
** Changed in: mutter (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification
Gianfranco suggested off-Launchpad that I test the most recent version
of libmutter (3.26.1), as it looks from the source as though this issue
is fixed there. I will report back in a few days (I generally suspend
and resume without restarting my session, so it will be a while until I
start using
Quick fix below. For reasons of time I have done no testing beyond that
GNOME Shell no longer crashes with the patch below. I have not tested
the effect on scaling settings.
** Patch added: "mutter.patch"
Second try with debug symbols for glib2.0 and libmutter.
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0,
width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc)
at
Public bug reported:
When I change the monitor configuration on my newly updated Artful
system I get a desktop crash. A quick reproduction with gdb attached to
gnome-shell gave the following back-trace, unfortunately with symbols
for gnome-shell but not for libmutter (I am still a bit of a
Looks like a case of Problem between Keyboard and Chair. I notice that
middle clicks work when I release the button very quickly. It is hard
to say now of course, I think that that was not necessary previously,
which is what mislead me. I will leave it up to others whether to keep
this open or
Seems to be fixed here too.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1499747
Title:
gedit crashed with SIGABRT in g_assertion_message()
To manage notifications about this bug
I can also reproduce this as described in comment 14, and get it
whenever I start Pidgin and log in to my Jabber account:
$ pidgin
**
GLib-GIO:ERROR:/build/glib2.0-pRoDo9/glib2.0-2.46.0/./gio/gmenuexporter.c:256:g_menu_exporter_menu_items_changed:
assertion failed: (position + removed <=
Update: I noticed that I was unable to select and paste URLs and parts
of URLs from Firefox to Pidgin this morning. I naively assume that it
is the same issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Public bug reported:
Quite often (subjectively nearly always) when I am using my laptop -
Dell Latitude E7440 - undocked with the internal touch pad, after a
while middle click paste stops working in gnome-terminal. I can middle-
click paste in e.g. Firefox, but neither from nor to
Public bug reported:
Happens during a build of VirtualBox. I think that the make output
describes the problem best:
kBuild: Generating
/home/michael/vbox/trunk/out/linux.amd64/debug/obj/vboxjws-gen/jwsgen/jwsglue.list
/home/michael/vbox/trunk/tools/linux.x86/jdk1.6.0_27/bin/wsimport
I would like to draw attention to this issue again. The fix which was
created is somewhat problematic, as it causes clipboard content to be
lost when the screensaver password screen is shown. Relevant to me is
that when that screen is shown in an Ubuntu guest in VirtualBox using
clipboard
Nice little workaround for IRC, and hence for idle (at least it does the
job at a pinch): http://wiki.tcl.tk/3125
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/304889
Title:
Does
Kirill: I am commenting as the member of the VirtualBox development team
in charge of keyboard handling in Linux. My guess is that the locate
pointer tool places a passive grab [1] on the control key. What this
means if it is correct is that as of the point when the grab is placed
no other
48 matches
Mail list logo
