** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2923
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2923
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2923
Importance: Unknown
Status: Unknown
** Also affects: inkscape (U
Hello @3v1n0
Still no luck. I added ci-train-ppa-service/4112 ppa and restarted the
session. There are logs (see attachment).
Bellow some info of my hardware:
$ inxi -G
Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 440.100
Display: x11 server: X.Org 1.20.8 dr
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https
Thanks Daniel for referencing that comment, it's indeed also relevant
here.
It seems weird as a whole that the available scaling options appear to
depend on common monitor resolutions. As stated there at 3840x2075
(that's 4k minus the VMware window borders) I see the
100/125/175/175/250 selector,
Reported upstream as
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1539
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1539
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1539
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
@seb128: No, please do not ask folks to report issues upstream when this
was only tested with software versions which are 30 months old. Upstream
does not want such reports as long as issues have not been reproduced
before in a recent and supported software version. Thanks.
--
You received this b
This crash took place after I had been processing six different images
without any problems. I exported the last image (a modified screenshot)
to JPEG and then tried to close GIMP. On clicking close the app crashed.
--
You received this bug notification because you are a member of Ubuntu
Desktop
I believe the real issue is that libsmbclient is still using the
SMB1/NT1 protocol as the maximum, the issue should be solved upstream
since SMB1 is deprecated (disabled by default in newer Samba server
versions).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
Really hope this gets solved soon, have to kill the process after
browsing shares every time I reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list sh
Thanks for reporting upstream and confirming it's still an issue with
the current flatpak
** Changed in: nautilus (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.
Public bug reported:
Hi,
The signature of the following symbols changed from glib-2.39.1 to
glib-2.39.2:
//glib-2.39.1/glib/ghash.h
void g_hash_table_insert(...);
void g_hash_table_replace(...);
void g_hash_table_add(...);
//glib-2.39.2/glib/ghash.h
gboolean g_hash_table_insert(...);
gboolean g
Also, g_utf8_make_valid is introduced in 2.51.0, but changed from 2.51.4
to 2.51.5:
//glib-2.51.4/glib/gunicode.h
gchar *g_utf8_make_valid(const gchar *str);
//glib-2.51.5/glib/gunicode.h
gchar *g_utf8_make_valid(const gchar *str, gssize len);
The minimum version should be 2.51.5, instead of 2.5
Thank you for your bug report. On what version of Ubuntu are you seeing
the issue?
** Package changed: evolution (Ubuntu) => evolution-data-server (Ubuntu)
** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => Low
** Changed in: evolution-data-server (Ubuntu)
Status: N
hello sir please solve it
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1884428
Title:
calculater not open
To manage notifications about this bug go to:
https://bugs.lau
Updating to g-t 3.36.2-1ubuntu1~20.04 and vte 0.60.3-0ubuntu1~20.04
works correctly
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
3.36.3-0ubuntu1 works fine, evolution is behaving without issue with it,
GNOME calendar integration is working, marking as verified
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification becaus
Tesint 3.36.3-0ubuntu1 by adding a new email account, configuring a
google calendar using goa, the different evolution components work as
expected, marking as verified
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You r
Testing 0.30.10-0ubuntu0.1 works without (new) issue. Importing photos,
browsing a collection, login to youtube for publishing.
The actual video publishing to youtube failed on quote error but the
focal version does the same, unsure if the issue is the API key and
number of users or with the accou
The issue still persists in Ubuntu 20.04. Running mate with lightdm and
light-locker configured to lock-on-suspend enabled. After resuming, the
desktop contents before suspend are visible for roughly 5 seconds,
before the lock screen appears.
As this is absolutely unacceptable in terms of security
*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300
The issue still persists in Ubuntu 20.04. Running mate with lightdm and
light-locker configured to lock-on-suspend enabled. After resuming, the
desktop contents before suspend are visible for roughly 5 secon
Public bug reported:
evince reproducabely crashes when opening the file rfc8798.pdf from
https://www.rfc-editor.org/rfc/rfc8798.pdf:
$ evince --version
GNOME Document Viewer 3.28.4
$ evince rfc8798.pdf
Segmentation fault (core dumped)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.0
Yes, the overall daily quota of 100k points is exceeded. Not much I can
do at the moment. But please file a ticket regarding the poor user
experience, this should be clearly visible in the UI
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
*** This bug is a duplicate of bug 1849888 ***
https://bugs.launchpad.net/bugs/1849888
is this duplicate of# 1849888?
** This bug has been marked a duplicate of bug 1849888
evince crashes (segmentation fault) when opening file rfc8655.pdf and other
new-format Internet standards
--
You r
*** This bug is a duplicate of bug 1849888 ***
https://bugs.launchpad.net/bugs/1849888
Thanks for looking at this bug report.
While this crash looks similar, and all the other problematic RFC
documents still crash the evince version in 18.04, there is another
report of issues with this specif
This problem still affects 18.04 ("bionic"), as is obvious from the bug
history.
A similar, but different, problem still affects current evince versions,
including those newer than the version in 19.10, see
https://mailarchive.ietf.org/arch/msg/tools-discuss/hgenvnKeP9zX-
IBX5FyD6zyEkmI/ .
Please
** This bug is no longer a duplicate of bug 1849888
evince crashes (segmentation fault) when opening file rfc8655.pdf and other
new-format Internet standards
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https:/
Apport showed: "evince crashed with SIGSEGV in g_string_free()".
In the other evince crash bug report, I was asked to provide a stack
trace. Here it is for this specific (publicly accessible) file:
Stacktrace:
#0 0x7fda9d0971b0 in g_string_free () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.s
Public bug reported:
Right click on screen background and choose settings.
Then click a different background.
System becomes unresponsive to keyboard input and mouse clicks.
System returns to responsiveness after about 10 minutes.
Description:Ubuntu 20.04 LTS
Release:20.04
CPU: 8-Cor
*** This bug is a duplicate of bug 1882410 ***
https://bugs.launchpad.net/bugs/1882410
** Information type changed from Private to Private Security
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
D
done. hope i didn't just give away too much info
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410
Title:
GNOME Shell crashed with signal 5
To manage notifications about
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
the lock screen is not working (when I press the button it try to lock
the screen bot nothgin happens)
Also, after some updates the wifi hotspot stoped to work :(
ProblemType: Bug
DistroRelease: Ubun
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1884380
Title:
screen lock and wifi hotspot is not w
Encountered this problem two times in 20.04 LTS. Both times were after I
moved away from my computer to go eat, and came back to see this bug.
Tried "Alt+F2" and typed "r", dialog disappeared.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Public bug reported:
It's been happening repeatedly over the last maybe week? I have to
manually kill it about once a day, when I start to feel everything slow
down as the OS starts to swap.
Actually, I tracked down and fixed a few leaks in the code, and it looks
stable so far. I'll submit a patc
(ie is it safe to power on my computer after doing so or should i be
changing the password or something? )
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shel
Queeq, yes I'd be interested in that Python script.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1203592
Title:
Keyboard backlight does not work in Samsung Series 9
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.lau
[Expired for gvfs (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gvfs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/b
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-software (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu
[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-sett
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
Considering that Mutter indeed knows that a monitor is virtual -
shouldn't it just ignore resolution completely for resolving existing
configuration? It changes all the time while dragging windows on the
host machine, maximizing, minimizing etc
--
You received this bug notification because you a
43 matches
Mail list logo
