Public bug reported:
$ journalctl -b
[...]
gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error:
Error invoking IBus.set_global_engine_async: Expected function for callback
argument callback, got undefined
** Description changed:
https://gitlab.gnome.org/GNOME/evince/issues/1120
---
- Click in 'File options->Dual' my PDF.
+ Click in 'File options->Dual' in my PDF.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: evince 3.32.0-1
Uname: Linux 5.0.5-050005-generic x86_64
https://gitlab.gnome.org/GNOME/evince/issues/1120
** Description changed:
Click in 'File options->Dual' my PDF.
+
+ JournalErrors.txt:
+ mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to
'EvWindow'
+ mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: **
+ mar 29
@Till
I do not see it crashing:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432#note_475636
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1810316
** Attachment added: "$ ll /var/crash"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810316/+attachment/5249520/+files/ll_var-crash.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
(moved of freedesktop to GNOME)
+
** Also affects: intel-vaapi-driver (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem:
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/totem/issues/315
+
+ ---
+
Watching movie 4k.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem 3.32.0-1ubuntu1
Uname: Linux 5.0.4-050004-generic x86_64
** Description changed:
+ https://github.com/intel/intel-vaapi-driver/issues/451
https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
---
Watching movie 4k.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package:
** Summary changed:
- totem assert failure: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
+ totem assert failure: totem: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
--
You received this bug
** Description changed:
https://github.com/intel/intel-vaapi-driver/issues/451
https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem)
---
- Watching movie 4k.
+ Watching movie 4k, forward and back.
+
ProblemType:
** Description changed:
- https://gitlab.gnome.org/GNOME/totem/issues/315
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://gitlab.gnome.org/GNOME/totem/issues/315 (Not totem)
---
Watching movie 4k.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem
See LP: #1818862
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id:
** No longer affects: totem
** No longer affects: mesa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
https://github.com/intel/intel-vaapi-driver/issues/451
- https://bugzilla.freedesktop.org/show_bug.cgi?id=110232
+ https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa)
** Description changed:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
---
+ [Impact]
+ gnome-control-center goes crash when I try to work with two USB WiFi cards.
+
+ [Test Case]
+ I have a wireless card connected and then I connect 'another' wireless card
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
#143
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
** Also affects: gnome-control-center via
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
Importance:
** Description changed:
+ https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
---
[Impact]
gnome-control-center goes crash when I try to work with two USB WiFi cards.
-
+
[Test Case]
I have a
I'm connecting 2 WiFi USB in ubuntu disco.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1810316
Title:
gnome-control-center SIGABRT when n-m is not working
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
(moved to GNOME)
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
(moved of freedesktop to GNOME)
---
https://gitlab.gnome.org/GNOME/nautilus/issues/980
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #980
https://gitlab.gnome.org/GNOME/nautilus/issues/980
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
't a a bt' worked. Do you need any other information? Please, just let
him know.
(gdb) t a a bt
Thread 5 (Thread 0x7f3c397af700 (LWP 3618)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f3c3bf8aa3a in g_cond_wait_until (cond=cond@entry=0x5570a0d86c08,
't a a bt' worked. Do you need any other information? Please, just let
him know.
** Attachment added: "gdb-gnome-keyring-deamon.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240204/+files/gdb-gnome-keyring-deamon.txt
--
You received this bug
** Attachment added: "gdb-gnome-keyring-deamon-v2.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240206/+files/gdb-gnome-keyring-deamon-v2.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
't a a bt' worked. Do you need any other information?
** Attachment added: "gdb-gnome-keyring-daemon-v4.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240218/+files/gdb-gnome-keyring-daemon-v4.txt
--
You received this bug notification because you are
't a a bt' worked. Do you need any other information? Please, just let
him know.
** Attachment added: "gdb-gnome-keyring-daemon-v3.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240207/+files/gdb-gnome-keyring-daemon-v3.txt
--
You received this bug
*daemon
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To manage notifications about this bug go to:
The problem still occurs in 'gnome-keyring 3.31.90-1ubuntu1'.
** Attachment added: "gdb-gnome-keyring_3.31.90-1ubuntu1_v2.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5240611/+files/gdb-gnome-keyring_3.31.90-1ubuntu1_v2.txt
** Summary changed:
- Full
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
---
- I do not know what happens, but the gnome-keyring process occupies the
- entire processor for a long time.
+ Description of problem:
+ After logging into my session, the gnome-keyring-daemon process
** No longer affects: libdrm (Ubuntu)
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** Bug watch added: freedesktop.org Bugzilla #109594
https://bugs.freedesktop.org/show_bug.cgi?id=109594
** Also affects: totem via
https://bugs.freedesktop.org/show_bug.cgi?id=109594
Never stop the process 'gnome-keyring-daemon', I must close it with
'kill -9 '.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To manage
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
+
+ ---
+
I do not know what happened.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.30.2-2ubuntu2
Uname: Linux
Sebastien Bacher, could you create a [0]package with the version of [1
]"gnome-keyring 3.31.90"? My intention is to confirm or inform what
happens with this version of the application. Thanks!
[0] https://people.canonical.com/~seb128/lp1816458
[1]
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/mutter/issues/506
Importance: Unknown
Status: Unknown
** Description changed:
- https://gitlab.gnome.org/GNOME/mutter/issues/506
-
- ---
-
In the last
** Description changed:
+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070
+
+ ---
+
In the last few weeks, gnome-shell has been crashing almost every time I
open my laptop to wake it from suspend. The rapid pace of package
updates has stopped Apport from letting me report it until
Of:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070
To:
https://gitlab.gnome.org/GNOME/mutter/issues/506
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
** Bug watch added:
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/totem/issues/312
+
+ ---
+
I do not know how this happened.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem 3.32.0-1ubuntu1
Uname: Linux 5.0.1-050001-generic
** Information type changed from Private to Public
** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu)
** Description changed:
- Open video in desktop.
+ Open video in desktop. This occurred when mixing packages of proposed.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
** Tags added: rls-dd-incoming
--
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/1796606
Title:
gnome-shell crashed with SIGSEGV in st_widget_get_theme_node →
ffi_call_unix64 →
https://gitlab.gnome.org/GNOME/totem/issues/307#note_455803
"Bug in mesa, duplicate of #264 (closed)"
** Description changed:
https://gitlab.gnome.org/GNOME/totem/issues/307
---
When I open a movie in totem, it looks like a window. But then I enlarge
it to full screen. It is seen
Public bug reported:
https://gitlab.gnome.org/GNOME/totem/issues/307
---
When I open a movie in totem, it looks like a window. But then I enlarge
it to full screen. It is seen in the lower part, a strip of lead.
Attached screenshot image.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package:
I am looking for if the patch was included before the release of mesa
"19.0.0-rc7"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1815236
Title:
totem assert failure: totem:
They could pass to [1]mesa_19.0.0~rc7
[1]
https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog
https://bugs.freedesktop.org/show_bug.cgi?id=109535
The error is corrected in master.
** Bug watch added: freedesktop.org Bugzilla #109535
mesa (19.0.0-1ubuntu1) disco; urgency=medium
* Merge from Debian. (LP: #1818516)
* revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889)
-- Timo Aaltonen Thu, 14 Mar 2019 18:48:18 +0200
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Released
--
You received
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/gvfs/issues/371
+
+ ---
+
I do not know how this happened.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gvfs-backends 1.38.1-1ubuntu2
Uname: Linux
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/totem/issues/297
+
+ ---
+
I'm not sure, but this happened after updating to gstreamer
1.15.1-1ubuntu1
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem
** Description changed:
https://gitlab.gnome.org/GNOME/totem/issues/297
---
- I'm not sure, but this happened after updating to gstreamer
- 1.15.1-1ubuntu1
+ I'm not sure, but this happened after updating to gstreamer 1.15.1
ProblemType: Crash
DistroRelease: Ubuntu 19.04
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel)
+
+ ---
+
https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
---
https://gitlab.gnome.org/GNOME/totem/issues/297#note_432608
Bastien Nocera:
"Looks like a crash inside the application side intel driver inside Mesa. It's
going to be a driver problem rather than something that totem can deal with."
** Also affects: mesa (Ubuntu)
Importance: Undecided
** Description changed:
+ https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa)
+
+ ---
+
https://gitlab.gnome.org/GNOME/totem/issues/297
---
I'm not sure, but this happened after updating to gstreamer 1.15.1
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package:
*** This bug is a duplicate of bug 1816415 ***
https://bugs.launchpad.net/bugs/1816415
** This bug has been marked a duplicate of private bug 1816415
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/gjs/issues/227
+
+ ---
+
I have performance problems, after updating.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gjs 1.54.3-1build1
Uname: Linux
Public bug reported:
Attach image of top.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.30.2-2ubuntu2
Uname: Linux 5.0.0-05rc7-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 18 08:06:10 2019
DisplayManager:
** Attachment added: "Captura de pantalla de 2019-02-18 08-07-52.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816392/+attachment/5239489/+files/Captura%20de%20pantalla%20de%202019-02-18%2008-07-52.png
--
You received this bug notification because you are a member of
** Summary changed:
- The notebook runs slow after updating
+ The notebook runs slow after updating (In Wayland and Xorg)
--
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/1816392
Public bug reported:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
---
I do not know what happens, but the gnome-keyring process occupies the
entire processor for a long time.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-keyring 3.28.2-3ubuntu1
Uname: Linux
** Description changed:
- I do not know how this happened.
+ In gdm I changed the login from Wayland to Xorg.
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.30.2-2ubuntu2
ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
Uname: Linux
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
---
Description of problem:
After logging, the gnome-keyring-daemon process overloads the notebook. With
this I have a drop in performance.
Version-Release number of selected component (if
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
---
- Description of problem:
+ Description of Problem:
After logging, the gnome-keyring-daemon process overloads the notebook. With
this I have a drop in performance.
Version-Release number of
https://wiki.ubuntu.com/Backtrace#Already_running_programs
In point 5: I can not freeze the process with 'ctrl+c'
** Attachment added: "gdb-gnome-keyring.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5239962/+files/gdb-gnome-keyring.txt
--
You
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25
---
Description of problem:
After logging, the gnome-keyring-daemon process overloads the notebook. With
this I have a drop in performance.
Version-Release number of selected component (if
Do you know of any guidelines for reporting a problem in an application
when it stays in a loop?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To
** Description changed:
+ [Impact]
+ After opening nautilus, I open 'another' tab with the mouse wheel button
(middle mouse button) in 'Other Locations' and nautilius crashes.
+
+ [Test Case]
+ 1. Open nautilus
+ 2. Click with the middle mouse button on 'Other Locations'
+ 3. Crash nautilus
+
** Description changed:
[Impact]
After opening nautilus, I open 'another' tab with the mouse wheel button
(middle mouse button) in 'Other Locations' and nautilius crashes.
[Test Case]
1. Open nautilus
- 2. Click with the middle mouse button on 'Other Locations'
+ 2. Click with the
** Description changed:
+ https://gitlab.gnome.org/GNOME/nautilus/issues/980
+
+ ---
+
[Impact]
After opening nautilus, I open 'another' tab with the mouse wheel button
(middle mouse button) in 'Other Locations' and nautilius crashes.
[Test Case]
1. Open nautilus
- 2. Click with the
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #342
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
** Description changed:
- https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432
+
** Description changed:
+ The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-control-center. This problem was most recently seen with package version
1:3.30.0-0ubuntu1, the problem page at
https://bugs.freedesktop.org/show_bug.cgi?id=110452
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: freedesktop.org Bugzilla #110452
https://bugs.freedesktop.org/show_bug.cgi?id=110452
** Also affects: mesa via
** Project changed: totem => gstreamer
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
To
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Description changed:
-
Public bug reported:
It always happens when I start the notebook. I must close it with 'kill
-u ProcessNumber'
Please indicate that more information is needed to repair this error.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: tracker 2.1.8-2
Uname: Linux 5.0.7-050007-generic x86_64
** Description changed:
+ https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea
+
+ ---
+
.
+
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
And bionic?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1774587
Title:
nautilus crashes in recent_thread_func -> is_file_valid_recursive ->
g_local_file_query_info ->
Thanks for your work!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1774587
Title:
nautilus crashes in recent_thread_func -> is_file_valid_recursive ->
g_local_file_query_info
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1726129
Title:
nautilus crashed with SIGSEGV in widget_needs_widget_path
To manage notifications about this
** Description changed:
https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea
-
- ---
-
- .
-
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1723181
Title:
shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
To manage notifications about this
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
https://gitlab.gnome.org/GNOME/gnome-shell/issues/804
+ ---
+
[ Impact ]
- - GNOME Shell crashes in st_widget_get_theme_node
-
+ - GNOME Shell crashes in st_widget_get_theme_node
[ Test Case ]
-
Public bug reported:
[Impact]
'tracker-miner-f' works a lot when I download with chrome
[Fix]
tracker-miner-f work with much less intencity
[Test Case]
1. Open Chrome
2. Download
http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso
3. Open gnome-terminal and run top
4.
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
---
[Impact]
When I try to set the pen on my touch screen. gnome-control-center crashes.
[Fix]
That you can configure the pencil to later occupy it with my touch screen.
[Test Case]
1. Open
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1827154
Title:
gnome-control-center
** Attachment added: "$ journalctl -b"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825449/+attachment/5256863/+files/journalctl_-b.txt
** Description changed:
- $ journalctl -f
- abr 18 20:03:18 localhost gnome-shell[1779]: Object Gio.Settings
(0x5563611f1ba0), has been
Public bug reported:
gnome-shell[1779]: Object Gio.Settings (0x5563611f1ba0), has been
already deallocated — impossible to access it. This might be caused by
the object having been destroyed from C code using something such as
destroy(), dispose(), or remove() vfuncs.
== Stack trace for context
Public bug reported:
[Impact]
A device that is manipulated through the graphical interface appears. But
nothing can be done.
[Test Case]
1. Open gnome-control-center
2. Then go to 'Power'
3. The device appears
Review attached image.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package:
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1826918
Title:
gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay()
from detach_pixmap() from
** Information type changed from Private to Public
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1082
https://gitlab.gnome.org/GNOME/nautilus/issues/1082
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/1082
Importance: Unknown
Status:
** Description changed:
- https://gitlab.gnome.org/GNOME/nautilus/issues/1082
-
- ---
-
- I was moving movies from one directory to another directory.
+ I was moving movies from one directory to another directory with mouse.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1836070
Title:
seahorse crashed with signal 5
To manage notifications about
This still happens in eoan.
** Changed in: nautilus (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1726129
Title:
nautilus crashed
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
- https://bugs.freedesktop.org/show_bug.cgi?id=110452
+ https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #153
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Also affects: gstreamer via
** Changed in: totem (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
** No longer affects: mesa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
To manage
I changed the name of the gmail account to USER.
** Attachment added: "$ gio mount -li"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825167/+attachment/5256545/+files/gio_mount_-liV2.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
https://gitlab.gnome.org/GNOME/nautilus/issues/991
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1825167
Title:
It does not correctly display the hard drive icon
To manage
Public bug reported:
https://gitlab.gnome.org/GNOME/nautilus/issues/991
---
The icon of my hard drive is SSD (Attach image).
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
Uname: Linux 5.0.8-050008-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture:
** Description changed:
https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce
---
the gnome video application crashed twice while attempting to browse a
upnp media server. at first I tried to play a video which failed to
play, then twice afterwards the
** Description changed:
https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce
---
the gnome video application crashed twice while attempting to browse a
upnp media server. at first I tried to play a video which failed to
play, then twice afterwards the
*** This bug is a duplicate of bug 1501049 ***
https://bugs.launchpad.net/bugs/1501049
** Description changed:
$ LANGUAGE=C totem
Click 'Channels'
- Click 'MyCloudEX2Ultra'
+ Click 'ServerDLNA'
Click 'Photos'
Click 'All Photos'
In console:
**
1 - 100 of 168 matches
Mail list logo
