This only affects X11, and gnome devs only care about Wayland
(specifically, their implementation of Wayland), so I doubt they're
gonna fix this, even though I'd like them to!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubun
I tested this with the very small patch indicated in #1 and it worked.
I did
"apt-src install mutter"
applied the patch.txt file with "patch -p1 < patch.txt"
"apt-src build mutter"
it fails all the tests but apparently this is expected, so i just went into the
obj directory and did "sudo ninja i
This bug is definitely important to me, being able to restart GNOME
Shell after it locks up, crashes, or updating an extension, _without_
losing any of my work or having to restart a large amount of open
programs, is one of the main reasons I still run it on X11. Luckily I
was testing 23.10 in a V
I just set this up and can confirm, it only sees one monitor (the
"primary"). Very weird. No problem using x0tigervncserver to see them
both.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.lau
I can confirm that (after figuring out which packages I had to force
version on and getting them all installed and restarting my session) the
gtk4 patch does fix the issue. No more weird corrupted borders, yay! I
do not see any issues with libreoffice either just in basic testing of
Writer and Calc
It looks like the gnome bug does acknowledge it only works for 'click'
mode (I use sloppy) so presumably when that gets fixed (and it looks
like they're still thinking about it!) and released then both mine and
yours will too.
--
You received this bug notification because you are a member of Desk
Hmm... unfortunately upgrading (both gnome-shell and mutter) to 44.1 did
not fix the main annoying bug for me where clicking titlebar doesn't
raise the window anymore (on X at least) - #2013216.
Also hitting the weird black bar issue that I didn't see under 44.0
https://gitlab.gnome.org/GNOME/gtk/
Argh, click to raise doesn't get fixed for me with this. Maybe because I
have focus follows mouse also? I still have to click inside the window
somewhere to raise it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https
I've seen this in my logs too, QUITE a lot in fact
sudo journalctl --no-hostname --since "30 days ago" | grep "update stage
views actor" | wc -l
gives me back: 221915
But as far as I can tell it doesn't have any effect (GNOME 44.0
certainly has its problems but I was getting it in 43.x too and
this should be fixed when ubuntu upgrades to gnome 44.1 which will
hopefully be soon! memory leak bugs that were fixed are also affecting
me (as well as this very annoying bug)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubu
Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only
installed it way back in the distant past to stop those stupid warnings
on the command line!)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
http
If it is related to that - you should do
gsettings set org.gnome.desktop.wm.preferences focus-new-windows 'strict'
(see
https://major.io/2015/07/06/allow-new-windows-to-steal-focus-in-gnome-3/
)
I'm here because I type in notification bubbles themselves, and since
gnome 3.34 these notifications
Just hit me, kernel 4.19.8-liquorix-amd64, Ubuntu 18.10. I was running
with modesetting, but decided to change to intel driver (freshly
compiled from git) to see if I run into it again (it seems pretty rare
though so will probably be tough to hit). Has anyone definitely hit it
on xf86-video-inte
please accept into artful-updates. i can't install the dbgsym files to
get a good backtrace for a bug until the dbgsym matches the version i
have installed (and i don't want to upgrade to proposed right now).
--
You received this bug notification because you are a member of Desktop
Packages, whic
Have you tried running with no add-ons or from a new Firefox profile?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1672698
Title:
Broken/Missing font rendering in firefox
Status in
All the other distributions have 52.0.2 released which has critical
security fixes, this should be put into main for zesty before release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/
I don't have the GNOME 3 staging PPA, and Zesty which we're running
includes GTK 3.22.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1664060
Title:
Can't see view message pane in E
I don't have any ideas for you about this bug, but just wondering how
you got firefox 52 with zesty, as only 50.1 is in the zesty release and
51 is in proposed (see https://launchpad.net/ubuntu/+source/firefox).
--
You received this bug notification because you are a member of Desktop
Packages, w
The latest batch of updates today (which included libwebkit2gtk updates)
fixed the Evolution message pane display problem for me, yay!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/16
Switching to Thunderbird is exactly what I did. :) But unlike the Arch
thread I don't have HiDPI enabled (scaling is 1 in gnome-tweak-tool for
both fonts and windows section). Epiphany works for me also. Do you have
HiDPI enabled? Does epiphany work for you? Also, for me evolution seems
to display
If this has been approved for stable series, any reason why it's being
held up in proposed for zesty?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1659922
Title:
Firefox 51.0.1 does
Any chance we can get this moved out of proposed and approved for zesty?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1659922
Title:
Firefox 51.0.1 does not display pages/shows blan
I upgraded to zesty before I saw movement on this, but I can confirm
that 3.22.3 in zesty fixes the problem I was experiencing with inline
images.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad
I'd really like this too. The git_fix-reply-with-inline-images.patch
that is already included in .1 is not working for me - I'm still
experiencing that crash. I'm really hoping that 3.22.2 will fix it but
I'd rather not upgrade to zesty to find that out.
--
You received this bug notification be
bug still occurs on gnome 3.16 w/ gnome-terminal 3.16
transparency can be enabled by editing the profile preferences and changing the
slider a bit
my preferred fix is ... use Konsole :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gno
I was experiencing this exact same bug as well. Based on information I
read in the corresponding RedHat report
(https://bugzilla.redhat.com/show_bug.cgi?id=879773) I was able to get
this to work by removing all the Evolution configuration directories
(which did have some prior attempts at configur
Sorry. :) Unfortunately/fortunately I can no longer reproduce it after
doing a BIOS update on my ASUS motherboard (was about 18 months behind).
Based on your description of the bug as possibly related to the BIOS I
decided to do that update, and even though it's only been about 10
minutes of usage,
I can also reproduce the bug using the new Google Maps (easiest way to
do so seems to be zooming in/out). However it occurs for me even after I
disable semaphores:
root@hawty:~# cat /sys/module/i915/parameters/semaphores
0
(after that):
[614445.590357] [drm:i915_hangcheck_elapsed] *ERROR* stuck o
*** This bug is a duplicate of bug 1034548 ***
https://bugs.launchpad.net/bugs/1034548
When I click on that I get "Bug 1034548 cannot be found"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpa
Sebastien - I'm pretty sure I was able to glean the information from
stuff on the internet, but doing "xinput list" and seeing it there
certainly confirmed it. Finding error messages in xkl functions also
helped. Others say this isn't their issue though.
--
You received this bug notification be
Unfortunately yes, at least for me. In my case it definitely has to do
with the fact that I have a USB hard disk reporting itself as a
keyboard, this is confusing xklavier and causing gsd to crash. I run
the command "xinput --set-prop "Western Digital My Book" "Device
Enabled" 0" in my .xstartup
In my case, I can reproduce it and I included the backtrace above
yesterday. I have found the issue is because an external USB hard disk
(a western digital MyBook 1TB Mirror edition, although other WD MyBook
devices also seem to have the same problem) is announcing itself not
only as a hard disk b
Besides just removing the device, I can also do
xinput --set-prop "Western Digital My Book" "Device Enabled" 0
every time X comes up and then re-start gnome-settings-daemon. I just
wish it could handle this error so I didn't have to!
--
You received this bug notification because you are a memb
Since this is another crash related to xkl_ functions (xklavier) please
see my note in bug 805894 - its possible we are seeing the same issue
with xinput.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
ht
After reading more of a related RedHat bug
(https://bugzilla.redhat.com/show_bug.cgi?id=657726) it would seem that
these crashes are in fact due to some bad messages coming back from
xklavier or xinput, and gnome-settings-daemon not being able to handle
them. Here is a recent stack trace:
mike@ha
35 matches
Mail list logo
