** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3451
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451
Importance: Unknown
Status: Unknown
--
You received this bug notification because
*** This bug is a duplicate of bug 2063049 ***
https://bugs.launchpad.net/bugs/2063049
(Confirming that I have ozone-platform-hint set to Auto instead of
Default in chrome://flags.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The syscall=330, the mknod denial, the /etc/vulkan/ denials are also
produced by the working chromium snap.
The /etc/igfx_user_feature.txt denial only shows up with the broken
chromium snap.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
(sorry, copy/paste fail)
> dmesg has a bunch of repeated
bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20243):
apparmor="DENIED" operation="open" class="file"
profile="snap.firefox.firefox" name="/etc/igfx_user_feature.txt" pid=7070
comm="FSBroker7944"
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769956/+files/Snap.Info.gtk-common-themes.txt
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which is
dmesg has a bunch of repeated
`snap revert chromium` reverted to 123.0.6312.122, which works fine.
--
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/2063304
Title:
chromium
apport information
** Attachment added: "Snap.Info.gnome-42-2204.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769955/+files/Snap.Info.gnome-42-2204.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
apport information
** Attachment added: "Snap.Info.core20.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769953/+files/Snap.Info.core20.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.cups.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769954/+files/Snap.Info.cups.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769952/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769949/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769951/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769947/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769950/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769948/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "HookError_chromium_browser.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769946/+files/HookError_chromium_browser.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769945/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At
I have the same problem but with Intel video. Chromium 124.0.6367.60
shows up camouflaged as my desktop wallpaper after the last snap update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Debian reverted the change to isolate these low quality fonts from the
rest of the system in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=883973, and now this bug is back in Ubuntu 23.10.
** Bug watch added: Debian Bug tracker #883973
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-
calculator/-/issues/359
Upstream says the actual bug is in libsoup:
https://gitlab.gnome.org/GNOME/libsoup/-/issues/361.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/-/issues #359
I backported Andrey Kudinov's suggested change (replacing Ubuntu's
openssl3-compat.patch with gentoo's version) and built a transmission
package in a PPA for jammy (Andrey's PPA only has packages for kinetic
and lunar).
I've been testing the patched transmission-gtk for the last 24 hours and
the
This appears to have been fixed in transmission 4.0 packages in 23.10
(mantic) and Debian sid.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1775434
Title:
Wrong ExecStop in
*** This bug is a duplicate of bug 1973084 ***
https://bugs.launchpad.net/bugs/1973084
** This bug has been marked a duplicate of bug 1973084
transmission-daemon high RAM usage
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The memory leak makes transmission unusable, so this bug should qualify
for a SRU. All we need is for someone to prepare a debdiff and request
sponsorship for the upload, as described in
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member
I'm also seeing memory leaks in transmission-gtk after upgrading to
22.04 LTS. In 48 hours it eats up all the RAM and Swap and gets killed
by systemd-oomd.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
Looking through upstream bug tracker I wonder if this might be caused by
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487#note_1553836?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Public bug reported:
If you have ~/Pictures/Screenshots open in Nautilus and you take new
screenshots, some of them will get tiny thumbnails instead of regular
size thumbnails.
See attached picture of the end result: some images have full size
thumbnails, some have tiny ones.
ProblemType: Bug
I'm now using Xephyr to confine my ChromeDriver-based Selenium tests
Xephyr :2 -screen 1300x720
export DISPLAY=:2
unset WAYLAND_DISPLAY
This works fine for me on Ubuntu 22.10 in a Wayland session (and it also
worked on 22.04 LTS).
As a bonus, the Chromium window doesn't steal focus
This was fixed upstream in version 42.beta:
https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/commit/371a1260630035724e20972ae5bda7098e2928a7
Ubuntu explicitly reverts that in debian/patches/ubuntu/Revert-media-
keys-fix-gnome-settings-desktop-file.patch with the rationale
> Ubuntu isn't
Public bug reported:
There's a default keybinding of XF86Tools to launch gnome-control-
center. On my ThinkPad X390's keyboard it is Fn-F9. This keybinding no
longer works in Ubuntu 22.10. Instead I see this error in my journal:
spal. 22 20:27:34 blynas gsd-media-keys[3793]: Could not
I suspect upstream commit
https://gitlab.gnome.org/GNOME/nautilus/-/commit/c72e6def48e47454d4b620f58c93753a8a1b6a3f
fixes this, which would explain why I couldn't reproduce using gnome-
nightly.
(There are several sorting-related upstream commits after the 43.0 tag.)
--
You received this bug
Public bug reported:
Steps to reproduce:
1. Open Nautilus
2. Switch to list view
3. Sort by size or mtime by clicking on the relevant heading
4. Press F5 to refresh the view
Expectation:
- Nautilus remembers the sort order
Actual behavior:
- the list is now sorted by name (in ascending
Public bug reported:
1. Open Chromium
2. Press Ctrl+Shift+P
What happens: a print dialog pops up (presumably from xdg-desktop-
portal-gnome), and both the dialog and the main Chromium window become
non-responsive. After a few seconds GNOME Shell pops up a "this app is
unresponsive" dialog with
Happened to me today, when I unplugged the USB C cable connecting my
ThinkPad to the dock with an external monitor plugged in, and then
closed the laptop lid to put it to sleep.
journalctl shows
```
geg. 27 15:53:39 blynas gnome-shell[3815]:
meta_monitor_manager_get_logical_monitor_from_number:
I can no longer observe this on Ubuntu 22.04 LTS (Wayland session) with
chromium snap 101.0.4951.64 (1993).
(An xeyes test confirms that the selenium-driven chromium is using
Xwayland.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This bug also affects 21.10, FWIW.
--
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/1930371
Title:
top bar displayed on top of a fullscreen window that gets moved from
one
I've seen this three times now on Ubuntu 21.10 (GNOME 40). I don't
recall ever seeing it on Ubuntu 20.10.
--
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/1532508
Title:
Screen
Filed upstream at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4351
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4351
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4351
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
I have two monitors: the laptop's internal one (primary), and an
external LCD positioned above the it.
I have configured mpv to be the default video player in Nautilus. I
have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'.
Steps to reproduce:
- click on a
My laptop with Ubuntu 20.10 automatically switches to the HDMI output
when I plug in my monitor (via a USB C cable connected to a dock station
connected to the monitor via a HDMI cable).
And then, a second later, it switches to the USB dock's audio output
(which has nothing plugged in), but
I don't know if you need more confirmations, but upgrading to mutter +
libmitter from groovy-proposed fixed my chromium problem too.
(The only weird bit was how I was unconsensually logged out during the
upgrade, but that could've been plymouth or some other package.)
--
You received this bug
I do not currently have access to the machine, due to COVID lockdowns.
I haven't changed the theme, so it _should_ be the default for Ubuntu
sessions, i.e. Yaru.
(My current machine doesn't exhibit the problem. Firefox also didn't
have the problem on the machine where I took this screenshot.)
Feels fixed to me too!
--
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/1858636
Title:
snapd generates incomplete fontconfig caches, result in emoji
rendering issue in
I've just upgraded to groovy and hit this bug. For now I'm using socat
as a workaround:
socat abstract-listen:/tmp/.X11-unix/X0,reuseaddr,fork
unix:/tmp/.X11-unix/X0
This works, but is rather slow (and probably also opens a security hole
on multiuser machines).
--
You received this bug
Public bug reported:
When I upgrade Firefox via apt upgrade (or, more often, Update Manager)
and open a new tab, Firefox shows a page telling me that it's been
upgraded and I need to restart it before I can continue browsing.
There's a "Restart Firefox" button. I press it, Firefox quits, and
Public bug reported:
This is a freshly installed Ubuntu 20.04 LTS system. I apt installed
chromium-browser, which pulled in the snap. I'm in an Ubuntu on Wayland
session.
The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing all
of the icons (see screenshot).
ProblemType: Bug
I once had trouble getting full native resolution on an external
2560x1080 monitor. It turned out to be a problem with the DisplayPort
-> HDMI monitor cable I had (not enough bandwidth without using a custom
reduced frequency mode via xrandr/way harded custom EDID hacks for
wayland), and
I ended up adding
if [ -n "$PS1" ]; then
# only for interactive sessions please
if [ -f /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-le64.cache-7
]; then
echo "color emoji will be broken in Chromium again (LP: #1858636) unless
you"
echo "sudo rm
Maybe not.
ls -ld /snap/*/current/usr/share/fonts/truetype/noto shows that only one
snap has that directory (gnome-3-34-1804), and instead of containing all
the fonts but NotoColorEmoji.ttf it's the exact opposite: it contains
one font only, and that is NotoColorEmoji.ttf.
--
You received this
Curiously, fc-cat /var/cache/fontconfig
/0bd3dc0958fa22058ebb13e2872b-le64.cache-7.bork does not complain
about the cache file being invalid. It shows information about a bunch
of Noto fonts BUT! not the ColorEmoji one!
diff -u <(fc-cat /var/cache/fontconfig/*.bork|cut -d'"' -f2|sort) <(ls
FWIW 0bd3dc0958fa22058ebb13e2872b is MD5 of
"/usr/share/fonts/truetype/noto". fontconfig keeps one cache file per
font directory.
The timestamp of the broken fontconfig cache file is May 15, 10:37. I
wonder what my computer was doing at the time.
'last reboot' indicates that I rebooted on
This time I successfully resurrected color emoji by manually removing
the file that fc-cache used to complain about. Or, rather, I moved it
aside, for study:
sudo mv /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-
le64.cache-7{,.bork}
Then I restarted Chromium and emoji are now colorful
FWIW rebooting also makes the problem reappear. snap info shows that I
last refreshed chromium 13 days ago, but I rebooted today to install a
kernel update, and color emoji disappeared.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Another experiment: while emoji are broken, I can do sudo fc-cache -s
-v, and it doesn't find any invalid cache files, and when I restart
chromium, I don't get color emoji.
But then I do sudo apt install --reinstall fonts-noto-color-emoji, and I
see a /var/log/fontconfig.log with an up-to-date
Yesterday I saw a notification about chromium being auto-refreshed,
restarted it, and today I noticed that color emoji are gone again.
I suspect the two facts are related.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
I tired to figure out what exactly happens when I reinstall fonts-noto-
color-emoji. According to dpkg's output, fontconfig's triggers run.
fontconfig's postinst runs
# Force regeneration of all fontconfig cache files.
mkdir -p /var/cache/fontconfig
fc-cache -s -v 1>/var/log/fontconfig.log
Unfortunately the workaround is temporary. I rebooted and the emoji are
gone again.
--
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/1858636
Title:
[snap] color emoji not
The workaround worked for me too. I used the simplified version
sudo apt install --reinstall fonts-noto-color-emoji
--
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/1858636
This is interesting information!
I have the chromium and chromium-chromedriver packages installed via
apt. I wonder if that is why my example (headless) can work without
overriding executable_path? chromium-chromedriver ships a
/usr/bin/chromedriver that's a shell script that exec's
Here's my minimal example:
#!/usr/bin/env python3
import time
import sys
from selenium import webdriver
options = webdriver.chrome.options.Options()
if '--headless' in sys.argv:
options.add_argument("headless")
driver = webdriver.Chrome(options=options)
driver.get("https://ubuntu.com;)
Public bug reported:
Since I upgraded my Ubuntu 19.04 laptop to Ubuntu 19.10 I've been unable
to run Robot Framework tests using SeleniumLibrary with Chrome. I keep
getting errors from chromedriver:
Parent suite setup failed:
WebDriverException: Message: unknown error: Chrome failed to start:
The workaround I now use is to modify the cp -a command in /etc/ppp/ip-
up.d/usepeerdns to look like this:
cp -a "$REALRESOLVCONF" "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" || {
rm -f "$REALRESOLVCONF.pppd-backup.$PPP_IFACE" "$REALRESOLVCONF.tmp"
exit 1
}
--
You received this bug
Unfortunately the fix doesn't work and Ubuntu 19.10 with ppp
2.4.7-2+4.1ubuntu4.1 is still affected. I've added a bunch of
logger -t usepeerdns -- doing stuff
commands to /etc/ppp/ip-up.d/usepeerdns and /etc/ppp/ip-
down.d/usepeerdns.
Here's what I see when /etc/resolv.conf is
*** This bug is a duplicate of bug 1778946 ***
https://bugs.launchpad.net/bugs/1778946
** This bug has been marked a duplicate of bug 1778946
No dns resolution after closing a vpn/pptp connection
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1778946 ***
https://bugs.launchpad.net/bugs/1778946
I've the same problem with a L2TP VPN. This still happens on Ubuntu
19.10.
** Also affects: network-manager-l2tp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318199/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318196/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318197/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318195/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318203/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318192/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318207/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318198/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318204/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318193/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318205/+files/Snap.Info.core18.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318202/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318206/+files/Snap.Info.gtk-common-themes.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318201/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318194/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318200/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1598995
(same steps to reproduce, and I see the same "runtime check failed:
(impl->staging_cairo_surface != cairo_surface)" errors in my journal
that correspond to Firefox crashes)
** Bug watch added: Mozilla Bugzilla #1598995
Public bug reported:
Steps to reproduce:
- make sure Firefox is not running
- export MOZ_ENABLE_WAYLAND=1
- firefox
then in a new terminal
- export MOZ_ENABLE_WAYLAND=1
- firefox www.google.com
Expectation:
- a new tab opens in the Firefox window, loading google
Actual result:
- firefox
Public bug reported:
I see this on my machine when I try to report a Firefox bug:
$ ubuntu-bug firefox
ERROR: hook /usr/share/apport/package-hooks/source_firefox.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook
Unfortunately I was unable to reproduce the bug.
--
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/1851528
Title:
JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1870
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1870
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870
--
You received this bug notification because you are a member of Desktop
Packages, which is
The JS traceback points to this line:
https://gitlab.gnome.org/GNOME/gnome-shell/blob/3913fa5044b2cd1d5abadc9b4254d06215491458/js/ui/windowManager.js#L1771
(GitLab commit doesn't match gnome-shell from Ubuntu 19.10, sorry! I
didn't have the time to go hunt for the exact commit that corresponds
apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace
/var/crash/_usr_bin_gnome-shell.1000.crash
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Toks failas
Public bug reported:
I was trying to bring my Firefox window to front by pressing Super+2
(it's my second pinned launcher), and gnome-shell crashed.
journalctl shows this:
lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed
UTF-8 character sequence at offset 0
I can confirm that the fix works with chromium snap 78.0.3904.70 (rev
909).
--
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/1849105
Title:
[snap] cannot pause video with
I've been googling, and it appears that Chromium should enable the mpris
interface in the snapcraft YAML for this to work:
https://snapcraft.io/docs/mpris-interface
Except if Chromium actually uses what looks like a dynamic part
("instance" + pid) in the dbus interface name, can it be made to
I'm seeing this in journalctl -b -g chromium:
spal. 19 15:00:35 blynas dbus-daemon[4473]: apparmor="DENIED"
operation="dbus_bind" bus="session"
name="org.mpris.MediaPlayer2.chromium.instance5306" mask="bind" pid=5306
label="snap.chromium.chromium"
spal. 19 15:00:35 blynas
Public bug reported:
On Ubuntu 19.04 I could press the button on my Bluetooth headset and the
YouTube video playing in my Chromium would pause/resume. This no longer
works in 19.10. What happens instead is I get an OSD popup with a NO
ENTRY symbol (circle with a diagonal backslash) from
Possibly related to https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/17
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #17
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17
--
You received this bug notification because you are a member of
The gnome-bugs link is broken. Working links:
- https://bugzilla.gnome.org/show_bug.cgi?id=525574 (old bugzilla)
- https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5 (new gitlab)
** Bug watch added: bugzilla.gnome.org/ #525574
https://bugzilla.gnome.org/show_bug.cgi?id=525574
** Bug
Tried this again on Ubuntu 18.10, and I'm happy to report that almost
everything works fine!
- "Other locations" in Nautilus shows my Samba server (after a couple of
seconds)
- I can click on it, get an authentication dialog, then see the shares
- I can click on a share and see the files
- I can
Public bug reported:
Whenever cups-daemon is upgraded (by unattended-upgrades usually), it
stops cups-browsed as a side effect of the upgrade. While cups.service
itself is restarted by the time the upgrade process is done, cups-
browsed.service remains stopped until manual admin intervention,
** Attachment added: "after-update-later.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+attachment/5220141/+files/after-update-later.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in
1 - 100 of 266 matches
Mail list logo
