Today it was experimental.refresh-app-awareness expiry time. It claimed
it had waited long enough and did the refresh anyway without consulting
me.
Immediately my fonts broke. And, as usual, the red dot in the Ubuntu
Dock (the "running applications indicator") next to the Chromium icon
Okay. That experimental.refresh-app-awareness did not fix it.
This morning (16 March), while switching tabs, the font "change"
occurred visibly again. Apparently I'm not looking at a fresh Chromium.
Yet still there is _something_ that messed up the fonts.
Here's some system info:
$ snap list
I suspect OP suffers from this:
www.osso.nl/blog/chromium-snap-wrong-fonts
Clearing out the font cache `rm /var/snap/chromium/common/fontconfig/*`
and restarting chromium is the only thing that reliably works for me.
I think "Refresh App Awareness" might be a workable workaround, as
Chromium
Confirmed with 98.0.4758.54:
- the pasting of content in an unrelated X window is _fixed_;
- the sorting is _fixed_;
- the moving of Tabs is _fixed_.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Personally, I think it's a waste of space to setup timeshift just
because Ubuntu snapcraft cannot keep more than two versions alive... I
think there is something wrong in the snap ecosystem if we cannot choose
between more than two versions which are both broken.
My two cents.
--
You received
See also https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1956888/comments/10 for downgrading instructions and
possible upstream bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
I think the relevant bug report is:
https://bugs.chromium.org/p/chromium/issues/detail?id=1279532
It causes havoc with Tab moving, and broken sortable lists (like the
bookmarks), and with pasting stuff to the wrong (X11) window. (See my
previous comment.)
Downgrading to a previous version
Is this related to https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1956838/comments/4 perhaps?
That bug reared its head for me when I was using a drag-drop widget in a
website.
If it is, it is even uglier than you think.
> As a workaround, it's too bad we can't restore a
I'm really unhappy with this, because it appears to paste text into the
window below it:
https://junk.devs.nu/2022/bugs/chromium_98.0.4758.9_snap_pastes_in_gedit.mp4
"""This is a video with two gedit windows side by side, and this bug report on
top. When dragging and dropping text INSIDE the
Hi Oliver, thanks for checking.
That's not what I meant though:
> chromium-codecs-ffmpeg are actual files
Yes, they are. So I *do* have *a* changelog.
But the chromium-browser files are not real files, and they point to the
wrong files, making it harder to find the chromium-browser changelog.
Public bug reported:
Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
which has to do with saving space, for some reason, the chromium-browser
has its changelog symlinked to an optional package.
Version: 72.0.3626.119-0ubuntu0.18
Right now, I have chromium-codecs-ffmpeg
For the record, now that I've moved from Artful 17.10 to Bionic 18.04,
this bug is not affecting me anymore, but now bug #1724439 is.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I just upgraded to Ubuntu 18.04 with libmutter 3.28.0-2 and ran into
this; monitor poweroff/poweron yields a crash of gnome-shell. The good
news is that the applications are not killed like they were in 17.10
(with wayland?). But waiting for the ubuntu-bug crash file to get
generated isn't a good
Hi Olivier,
I'm sorry, I must've missed your reply. Apparently I did not auto-
subscribe to the bug-updates.
It crashed again today with 64.0.3282.167-0ubuntu0.17.10.1, so I went
here, saw your response and tried to reproduce: before upgrading it
crashed as expected, but with the latest version
I've seen a crash with that exact backtrace on Artful just now.
Both on 64.0.3282.140-0ubuntu0.17.10.1 and on
64.0.3282.167-0ubuntu0.17.10.1.
For 140 I did not get a full backtrace because I could not locate the
dbgsym at the time. For 167 the backtrace ends in AsLocatedEvent() <-
@3v1n0: I suspect that this changeset -- which should be in 3.26.3 -- does the
same:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
By the way, upstream appears to have a fix for this too:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/
Cheers,
Walter Doekes
OSSO B.V.
--
You received this bug notification because you are a member of
In my case, applying just [3] wasn't enough.
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557
[2] https://bugzilla.gnome.org/show_bug.cgi?id=788764
[3] https://bug788764.bugzilla-attachments.gnome.org/attachment.cgi?id=361654
I also had to apply [6] to fix [5]:
[4]
Stack trace looks like https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1724557 here too. Guessing this is a duplicate.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Yes. Also experiencing these crashes since I switched from Zesty to
Artful yesterday. A lock-screen reproduces the crash, as does turning
the monitor off.
I have a UWQHD (3440×1440) resolution, if that matters, on my Dell
monitor. I'll try to gather some more debug info.
This is highly annoying,
I have the same problem, but with gpg-agent, which also reverse-depends
on graphical-session-pre.target.
Also upgraded from 17.04 (clean install) to 17.10.
I'm not sure where when the --user graphical-session-pre.target is
supposed to get started (and by whom), but it appears it never does. If
I
Yeap, that fixes things. Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1710789
Title:
chromium does not open downloaded files
Status in chromium-browser package in
s/the broken Xenial version is lower/the fixed Xenial version is lower/
(sorry)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser:
Okay, that didn't take long. My slack windows started to "Aw snap!"
within another 10 minutes.
Both the Xenial [*1] version and the version from Haw Loeung (hloeung)
[*2] work fine though. Where the second is better because the broken
Xenial version is lower and would be auto-replaced with the
54.0.2840.100-0ubuntu0.16.10.1326 from 'ppa:canonical-chromium-
builds/stage' (on Yakkety) hasn't crashed yet. (Running for 10 minutes
now.) Beats having to switch to FF for some pages.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Confirmed. No strange behaviour with 38.0.2125.111. Only expected and
working behaviour.
Good.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1309145
Title:
Chromium 34+
So. Apparently this has been fixed somewhere along the road to Ubuntu
14.04.
The patch is commented out in the debian/patches/series file in version
1.3.0-0ubuntu2.
However, the debian/changelog doesn't tell me when that happened (or when it
was added, for that matter).
--
You received this
Nope. Not fixed there either. I get exactly this:
https://code.google.com/p/chromium/issues/detail?id=351230#c64
(the gdk_window_set_user_time called on non-toplevel error)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
Funny, but that gives me completely different broken behaviour.
im-config writes to ~/.xinputrc:
# im-config(8) generated on Thu, 07 Aug 2014 08:26:49 +0200
run_im xim
# im-config signiture: 89512b7941127eeda7d3e3ac5703f05e -
And then I indeed get the same environment variables as you.
** Summary changed:
- Chromium 34 ignores ComposeKey
+ Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1309145
I can refute it. Over here is it *not* fixed with:
Version 36.0.1985.125 Ubuntu 14.04 (283153)
I did a full restart, to be on the safe side.
My config:
$ tail -n1 .profile
export GTK_IM_MODULE=xim # Compose key stuffs
$ cat .XCompose
include %L # import the default Compose file
Confirming: I switched to xim input method yesterday (for custom compose
combinations), and today I noticed that indeed the compose key does not
work in Chromium.
http://code.google.com/p/chromium/issues/detail?id=351230
Browser: Version 34.0.1847.116 Ubuntu 14.04 aura (260972)
Thanks for that detailed explanation Michael.
I'm not sure why the other apps didn't pose any problems without the
indicator-appmenu. But it's all moot now.
The desktops have been upgraded to 14.04. Let's focus on the problems of
the future!
Closing. (If I have the power to do so.)
** Changed
Did you see the workaround on my site? Using dconf-editor to switch the
mode?
(And hit the this bug affects me to increase its visibility.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
Public bug reported:
The Ubuntu's new Enhanced Menu project[1] aims to add the option of
choosing whether you want the Global menu or not.
Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be
missing the indicator-appmenu (and dependencies). And without those,
there was no global
36 matches
Mail list logo
