Fixed in 2.22.0-8. Thanks!
** Changed in: lilypond (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912939
Title:
Lilypond messes up file names with accent
Public bug reported:
This summarizes it all:
~/$ lilypond é.ly
GNU LilyPond 2.22.0
warning: cannot find file: `??.ly'
fatal error: failed files: "??.ly"
File names with accentuated characters used to work very well with
Lilypond 2.20. This bug appeared when I upgraded to 2.22.
ProblemType: Bug
I also experience this bug (very frequently) on Ubuntu 20.10.
Unfortunately I can't switch to another graphics driver, my laptop has
an i915 chipset.
$ lsmod|grep i915
i915 2273280 8
drm_kms_helper225280 1 i915
cec53248 2 drm_kms_helper,i915
i2c_algo
Fixed with today's 20.10 update (gedit 3.38.0).
** Changed in: gedit (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871082
Title:
gedit unexpectedly open
Fixed upstream (v3.38).
https://gitlab.gnome.org/GNOME/gedit/issues/177
https://gitlab.gnome.org/GNOME/gedit/-/issues/188
Meanwhile, before v3.38 is released and imported, just updating
get_active_window (in gedit-app.c) fixes the bug. I built gedit from
source and compared before/after, it works
Public bug reported:
I've had this bug for I'd say a couple of weeks, maybe a month or two. I
use a dual screen setup. If the gedit window is on my secondary (right)
screen and I open a recent file, gedit does not open it in the current
window and creates a new one (which is annoying and unexpecte
Public bug reported:
Changing key bindings doesn't work (tested on up-to-date 20.04 as of
today). It seems to work when you set them, it reflects the correct
keys, but once in game the change is not effective. I tried to change
the ABC buttons mapping from "asd" to "qsd" (French keyboard layout) b
Thanks Rocko.
I had this bug too. It used to happen systematically when I moved a Firefox tab
over a LibreOffice Writer window. So now, after the gnome-shell 3.36.0-2ubuntu2
update, I tried again and failed to make it crash. Seems fixed.
--
You received this bug notification because you are a m
I will look into it.
Here is how to reproduce the bug very easily:
- open LibreOffice Writer
- open Firefox
- resize and move the windows so that they don't overlap
- drag the Firefox tab (not window) over LibreOffice
Then you instantly get the crash.
--
You received this bug notification becaus
Here is the backtrace and registers.
At first I couldn't reproduce the bug by just moving youtube videos (in
firefox) around. But then when I had a document in LibreOffice Writer open
(which is the situation I was in over the last few days of crashes), it
happened very easily.
---
Thread 1 "gno
Here is a log with a few crashes. It seems to always come after a few of
these:
Mar 6 01:24:57 wolfenstein rtkit-daemon[1197]: Supervising 9 threads of 5
processes of 1 users.
Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: message repeated 19 times: [
Supervising 9 threads of 5 processes of 1
Got the same bug (GNOME Shell crashed with signal 11 after a short video
freeze) on 20.04. It's pretty recent, it's been crashing my computer a
couple of times a day since March 3 (according to the logs). I keep my
computer updated every day. Seems to happen when I move a video from one
monitor to
12 matches
Mail list logo