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 Desktop
Packages, which is subscribed to gnome-shell 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 Desktop
Packages, 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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1803319
Title:
GNOME Shell task bar menus not
Update: 4.19.4-041904-generic is affected, 4.20.0-042000rc1-generic is
not.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1805151
Title:
Desktop freeze running VirtualBox, Intel
Public bug reported:
This is identical to bug 1804885, but as requested I am filing this while
running the standard Ubuntu kernel. I will copy and paste my summary below.
Updates since I created that bug:
* This occurs with the mainline PPA 4.18.12-041812-generic kernel.
* The glxinfo
Public bug reported:
When I start a VirtualBox virtual machine (reproducible with the Ubuntu
18.04/VirtualBox 5.2.22 packages from virtualbox.org) with VMSVGA
emulation and 3D pass-through enabled, my system hangs. Sometimes I can
recover if I get to a VT fast enough to kill the process. Also,
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 Desktop
Packages, which is
No desktop files installed: everything running out of the build
directory, and the only thing installed outside is the kernel modules
and a udev rule.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
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 Desktop
Packages, 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1722725
Title:
GNOME Shell disabling
The patches are attached to gnome-bugs #788915.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1722725
Title:
GNOME Shell disabling wrong screen when docking laptop
Status in
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 Desktop
Packages, 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 Desktop
Packages, which is subscribed
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
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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
>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 Desktop
Packages, 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 Desktop
Packages, which is subscribed to
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 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 Desktop
Packages, which is subscribed
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
** 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?
--
*** This bug is a duplicate of bug 1724259 ***
https://bugs.launchpad.net/bugs/1724259
Reported this again using apport as bug 1724259.
** This bug has been marked a duplicate of bug 1724259
System freeze after docking and display configuration change
--
You received this bug
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
Just got this again with 4.13.0-15-generic after suspending and resuming
the laptop. No docking station or screen reconfiguration.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1723075
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
Public bug reported:
Reporting this against network manager for want of better information.
Sorry for the imprecise report - I will be glad to observe and update.
Since upgrading to 16.10 I have had problems with my USB "ethernet"
network connection provided by a tethered Android 2.3 device.
I hope this upstream change set will do the trick:
https://www.virtualbox.org/changeset/62242
Re comment 11, I looked at Mesa to see how they were distinguishing
client and server GL and applied that to my code (see comments in change
set).
To summarise the issue: the tricks that we were
Sorry, that doesn't do it yet. (Shame I didn't manage to fix this for
5.0.0.) However I realised that Mesa has exactly the same problem, so I
have taken a look at their code to see what they do. Also looks like a
bit of a hack, but since nothing relevant can afford not to work with
Mesa it
My apologies, I missed that one, so this is probably my bug! I will fix
that and then get back to you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1599775
Title:
"low-graphics
I was able to reproduce this with the lightdm deb file from that package
installed. I did not install the other deb files built from the
package.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Actually, perhaps I misunderstand the lightdm log rotation and the .1
logfile does contain the relevant log. I assume the lightdm developers
will know.
My uneducated guess is that there is some sort of race here between
lightdm and logind which needs better dependency specification.
And I just
Just checked, I do not have that message in the current log file,
attached the file from yesterday containing the message.
I asked about this on #ubuntu-devel, here are the relevant logs:
(17:09:06) michael-vb: Afternoon. Not sure if this is the right place to ask,
but someone will probably
** Attachment added: "The log file from yesterday."
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+attachment/4696780/+files/lightdm.log.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Public bug reported:
I sometimes get the "low-graphics mode" message when starting an Ubuntu
16.04 virtual machine inside of VirtualBox (current development code
trunk, somewhere past version 5.1 beta 3 and a debug build). When I
switch to VT-7 I find the X server running without any visible
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 Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1499747
Title:
gedit crashed with SIGABRT in g_assertion_message()
Status in gedit package in Ubuntu:
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 <=
Current status: with BIOS A15 and kernel 4.2.0-11-generic I was unable
to get the external screen to connect at all in an X session (a VT
worked more or less fine). Now using kernel 4.3.0-040300rc3-generic and
so far no visible graphical problems at all. I will keep you updated.
--
You
Martin, it might be good to wait for more feedback before closing this.
I suspect that different people may be seeing different issues, and that
some might still have problems. And in defence of upstream, a short
sleep does seem reasonable to me when dealing with timing issues in
black box
Is this alright?
** Patch added: "Fix timing issues on USB3 or fast recent hardware. Back-port
from upstream."
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/+attachment/4465857/+files/usb3_timing_fix.debdiff
--
You received this bug notification because you are a
I am now no longer seeing the flicker and resolution issues much (and
poking the hardware, e.g. by opening the Display control panel usually
gets rid of it). I have a suspicion there might be hardware issues too.
The mouse cursor issue is still present with kernel 4.2.0-7-generic, and
still not
Public bug reported:
After upgrading to Wily, when I change the configuration of screens
attached (specifically: dock the laptop to a docking station with a
vertically larger external screen or open the laptop to activate the
internal screen while correctly running with said external screen) this
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 Desktop
Packages, 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
Got a colleague to test 1:0.9.11.3+14.04.20150122-0ubuntu1 and confirm
that the fix works. Once again, I am unpleasantly surprised at how much
work you offload onto someone who points out an obvious typing mistake
in a line of source code.
** Tags removed: verification-needed
** Tags added:
I no longer run a Trusty system myself - I run Utopic, which already
contains the fix (which I can and have confirmed). I have however added
a note onto the VirtualBox bug tickets, in which this was reported as a
bug in VirtualBox, asking the users to test the fixed Ubuntu package.
--
You
[Impact]
* VirtualBox and other multi-monitor full-screen applications using the
freedesktop.org standard are not displayed in a usable way when running
multi-monitor full-screen in Unity without this fix.
* The bug makes the above set-up unusable. Low regression potential as
this is an
You might want to try a recent test build of VirtualBox1. We are
reworking full-screen mode to use the official freedesktop/EWMH APIs and
having a hard time writing code which all the different window managers
like. The specifications leave quite a bit open to interpretation...
1
By the way, I am not (of course!) saying that it is a bug in VirtualBox.
Realistically there are probably equal chances of it being a problem
with VirtualBox, a problem with Unity or a misunderstanding between the
two.
--
You received this bug notification because you are a member of Desktop
Thank you. I wonder whether your flickering issue will stay fixed, as
I can't think why a reboot would make a difference for VirtualBox
(perhaps for Unity...) I suspect that the menu bar issue is because
this is a generic Linux and not a specific Ubuntu build, but I suggest
that that discussion
Any estimate as to how long this will take to get into Ubuntu, and which
versions it will get into? We have to know whether to provide a work-
around in our software.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
We are re-working multi-monitor full-screen support in VirtualBox, and
the new code, which should be part of the next fails in Compiz because
of this bug. Specifically the top left-hand corners of guest screens
is offset from that of the host screen by an amount related to the
position of the
Public bug reported:
PrivateWindow::setFullscreenMonitors() contains the following:
CompRect fsRect (screen-outputDevs ()[monitors-left].x1 (),
screen-outputDevs ()[monitors-top].y1 (),
screen-outputDevs ()[monitors-right].x2 (),
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
Public bug reported:
In Raring, when pidgin is running with an IRC chat window open and all
others closed, I find no way to get to the main window (Buddy List)
except re-launching the pidgin executable, e.g. via the Dash. Until a
couple of weeks ago this could be done by clicking on the Pidgin
Thank you. Is there also a test build for Quantal? I will not upgrade
before the beta cycle.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1107598
Title:
Blank
Public bug reported:
I was previously reporting this on bug 966744, which is however now
marked as fixed and we are requested to open new reports. This is an
issue which I get very sporadically on resuming my Dell Latitude E6410
whereby the keyboard is still active (I was able to switch to a
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 Desktop
Packages, 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
72 matches
Mail list logo
