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
** Also affects: gnome-boxes via
https://gitlab.gnome.org/GNOME/gnome-boxes/issues/338
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822328
Title:
https://gitlab.gnome.org/GNOME/gnome-boxes/issues/338
** Information type changed from Private to Public
** Description changed:
+ https://gitlab.gnome.org/GNOME/gnome-boxes/issues/338
+
+ ---
+
Installing ubuntustudio-19.04-beta-dvd-amd64.iso, after installation
asked the installer to
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
** 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
@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810316
Title:
gnome-control-center SIGABRT
** 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
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: gen9_mfd.c:649:
** 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:#1821525
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818862
Title:
Totem player hangs when seeking video due to [gen9_mfd.c:649:
See LP: #1821525
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818862
Title:
Totem player hangs when seeking video due to [gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: Assertion `0'
See LP: #1818862
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821525
Title:
totem assert failure: totem: totem: gen9_mfd.c:649:
gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** No longer affects: totem
** No longer affects: mesa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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)
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810316
Title:
gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
(object))
To manage
** 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
** 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/baobab/issues/20
** Bug watch added: gitlab.gnome.org/GNOME/baobab/issues #20
https://gitlab.gnome.org/GNOME/baobab/issues/20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ By opening the 'baobab' program and choosing to set up a u...@gmail.com
basin, and then setting up the gmail account. And I hit a click to open a
folder of u...@gmail.com crashes 'baobab'.
+
+ [Test Case]
+ 1. Open baobab
+ 2. Mount u...@gmail.com
+ 3. Wait
** Description changed:
- https://gitlab.gnome.org/GNOME/gnome-boxes/issues/338
+ https://gitlab.gnome.org/GNOME/gnome-boxes/issues/338 (No GNOME)
---
Installing ubuntustudio-19.04-beta-dvd-amd64.iso, after installation
asked the installer to restart and crashed gnome-boxes.
** Changed in: gnome-boxes (Ubuntu)
Status: New => Invalid
** Changed in: gnome-boxes (Ubuntu)
Status: Invalid => New
** Changed in: gnome-boxes (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I'm working with gnome-boxes and install ubuntu disco(20190326.2) more
update of proposed.
dmesg:
[3.559133] pciehp :00:02.4:pcie004: Failed to check link status
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-8-generic 5.0.0-8.9
Public bug reported:
Mesa 19.0.1 is a bug fix release which fixes bugs found since the 19.0.0
release.
Mesa 19.0.1 implements the OpenGL 4.5 API, but the version reported by
glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
glGetIntegerv(GL_MINOR_VERSION) depends on the particular
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
Bugs, which is subscribed to Ubuntu.
@Timo:
And for publicity?
Ubuntu 19.04 works with:
Kernel 5
GNOME 3.32
Wayland 1.17
Not everything is technical. Big Boss,,,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821318
Title:
FFe:
@Timo:
And for publicity?
Ubuntu 19.04 works with:
* Kernel 5
* GNOME 3.32
* Wayland 1.17
Not everything is technical. Big Boss...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821318
Title:
ok I understand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821318
Title:
FFe: Wayland 1.17 for disco
To manage notifications about this bug go to:
Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821318
Title:
FFe: Wayland 1.17 for disco
To manage notifications about this bug go to:
'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,
** 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
Bugs, which is subscribed to Ubuntu.
'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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To manage notifications about this bug go to:
'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
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
---
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
---
- 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816458
Title:
Full load
To manage notifications about this bug go to:
** 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
** 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]
** Summary changed:
- systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code
2.
+ Unable to mount USB hard drive
** Description changed:
The USB hard drive does not appear in Nautilus.
+
+ The error that appears in journalctl is:
+ systemd-udevd[3453]: Process 'ata_id
# /etc/udev/udev.conf
#
# udev_log=debug
$ journalctl -f
** Attachment added: "journalctl_-f_v2.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+attachment/5246716/+files/journalctl_-f_v2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
+ https://github.com/systemd/systemd/issues/12019
+
+ ---
+
The USB hard drive does not appear in Nautilus.
The error that appears in journalctl is:
systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code
2.
ProblemType: Bug
** 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
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:
** 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
https://github.com/systemd/systemd/issues/12019#issuecomment-473578815
"Please, close report. The hard disc, it had no format."
** Bug watch added: github.com/systemd/systemd/issues #12019
https://github.com/systemd/systemd/issues/12019
--
You received this bug notification because you are
** 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
Thanks for helping build a better Ubuntu. Could you run the following
command in the terminal?
$ sudo apt-get install --install-recommends linux-generic-hwe-18.04
xserver-xorg-hwe-18.04
Restart your computer, and tell us if it works now.
Thanks.
** Changed in: alsa-driver (Ubuntu)
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796606
Title:
gnome-shell crashed with SIGSEGV in st_widget_get_theme_node →
ffi_call_unix64 → ffi_call →
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:
** Description changed:
- I was working with RDP and Windows 10 Professional.
+ 1° Open gnome-boxes
+ 2° Clicked in 'New'
+ 3° Clicked in 'Connect to remote box'
+ 4° Data: rdp://MyIP.Windows10Professional
+ 5° Login to 'Remote Host'
+ 6° Clicked in '<'
+ 7° Crash gnome-boxes
+
ProblemType:
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-boxes/issues/326
---
I have been working for more than half a year with Wayland, and overall
- it has worked well with my environment GNOME ~3.30 and Ubuntu 19.04
+ it has worked well with my environment GNOME ~3.32 and
Public bug reported:
I created a remote box to enter windows 10. The first time, I could
enter by entering the username and password. But then I change the
password of the Windows 10 user and try to enter again with gnome-boxes
and crash gnome-boxes. (attached gdb)
ProblemType: Bug
** Summary changed:
- gnome-boxes crashed with SIGSEGV in convert_alpha()
+ [RDP] gnome-boxes crashed with SIGSEGV in convert_alpha()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820694
Title:
Public bug reported:
https://gitlab.gnome.org/GNOME/gnome-boxes/issues/326
---
I have been working for more than half a year with Wayland, and overall
it has worked well with my environment GNOME ~3.30 and Ubuntu 19.04
Development.
But recently I was testing gnome-boxes (3.31.90-2) and setting
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
Bugs, which is subscribed to 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
@Iain:
https://bugs.freedesktop.org/show_bug.cgi?id=109535
** Bug watch added: freedesktop.org Bugzilla #109535
https://bugs.freedesktop.org/show_bug.cgi?id=109535
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@laney:
https://bugs.freedesktop.org/show_bug.cgi?id=109535
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818516
Title:
FFe: Mesa 19.0.x for disco
To manage notifications about this bug go to:
@lain:
https://bugs.freedesktop.org/show_bug.cgi?id=109535
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818516
Title:
FFe: Mesa 19.0.x for disco
To manage notifications about this bug go to:
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
@Timo
1) Close LP: #1819277
2) For me, this new version of 'mesa' works well
Thanks!
** Attachment added: "$ dpkg -l | grep mesa | grep 19"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+attachment/5246287/+files/mesa_19.0.0-1ubuntu1.txt
--
You received this bug notification
Public bug reported:
The USB hard drive does not appear in Nautilus.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu1
Uname: Linux 5.0.2-050002-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 15 20:26:26
Forget this report, my system in general was in trouble. I followed [0]this
guide, and everything went back to normal.
[0] http://www.webupd8.org/2013/11/how-to-downgrade-proposed-repository.html
** Changed in: gstreamer-vaapi (Ubuntu)
Status: New => Invalid
--
You received this bug
Public bug reported:
https://wayland.freedesktop.org/releases.html
https://lists.freedesktop.org/archives/wayland-devel/2019-March/040335.html
---
Please upload the new version of Wayland (1.17) published on March 20,
2019, as it is complementary in the graphic, if there are usability
problems
> Is there anything that's useful for disco?
> I don't see it.
August 24, 2018 -> Wayland 1.16
March 20, 2019 -> Wayland 1.17
~6.8 months of work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821385
Title:
Xwayland crashed with SIGABRT in wl_proxy_destroy()
To manage notifications about
** Bug watch added: freedesktop.org Bugzilla #110226
https://bugs.freedesktop.org/show_bug.cgi?id=110226
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=110226
Importance: Unknown
Status: Unknown
** Description changed:
+
** 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814885
Title:
packagekitd crashed with SIGABRT in std::terminate()
To manage notifications about
** 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
** 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://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:
** 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
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
*** 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
Bugs, which is subscribed to 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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816392
Title:
The notebook
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
** Bug watch added: Linux Kernel Bug Tracker #202581
https://bugzilla.kernel.org/show_bug.cgi?id=202581
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=202581
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
This happens on kernel 5.0.0-05rc6-generic
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815952
Title:
Mute key LED does not work on HP Pavilion x360
Public bug reported:
Description of problem:
The F6/mute key on the keyboard of HP notebooks often has a built in LED
indicator to show if the sound is muted. The LED state is never toggled. It
will just retain its state, even though the audio is succesfully muted/unmuted.
Tested with HP
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/pci/hda/patch_conexant.c?id=v5.0-rc6#n934
SND_PCI_QUIRK(0x103c, 0x837f, "HP ProBook 470 G5",
CXT_FIXUP_MUTE_LED_GPIO),
What values are those that replace "0x837f"?
Where does that information come from?
--
You
$ lspci
-> Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71]
(rev 21)?
Add line(?):
+ SND_PCI_QUIRK(0x103c, 0x8086, "HP Pavilion x360", CXT_FIXUP_MUTE_LED_GPIO),
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815963
Title:
telepathy-idle crashed with SIGSEGV in tp_handle_inspect()
To manage notifications
Ok.
My first patch for the linux kernel:
https://github.com/caravena/linux/commit/c540283416a7756dedaa72aa66a00c897517b113#diff-f52b6863505adc3b972c64d4a22195cc
I would like to have credits for this patch (:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
1 - 100 of 351 matches
Mail list logo
