Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
If your "mouse works fine" then Xorg is still working and it's only
gnome-shell that's frozen, so reassigning...
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Summary changed:
- Xorg freeze
+ gnome-shell freeze
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Next time the problem happens, log into a tty and find the PID of the
frozen gnome-shell process. Then run:
apport-cli --hanging -P PID
where PID is the process ID of the frozen gnome-shell process (which is
the one running as your own user ID, not gdm).
That should create a new bug/crash
** No longer affects: ubuntu
** Tags added: performance
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1836960
Title:
Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently
** Tags added: xrandr-scaling
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1793496
Title:
scaling changes when closing/re-opening the lid
Status in Mutter:
New
Status in mutter
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
In that same update, I also upgraded the Mesa package:
2019-07-07 06:50:41 upgrade libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:41 status half-configured libegl-mesa0:amd64
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:41 status unpacked libegl-mesa0:amd64
Public bug reported:
I’m not exactly sure if this belongs here, libva, mesa, or upstream
somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program
is.
Kodi has worked just fine on my system, as recently as July 7th of this
year, but yesterday (July 16) I tried Kodi again: I got a
The problem should be fixed in git, and available in the 1.14.0.
I don't think there's a workaround other than building from source; but it
should be possible to address it that way.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Bug solved!
In my case, the Laine gnome-shell extension was causing all the problems.
when I turned the Laine extension off both google-chrome and chromium
versions 75 (newest updates) worked again. Both video and audio playback
ran normally again.
On Tue, Jul 16, 2019 at 2:51 PM BavarianPH
Bug solved!
In my case, the Laine gnome-shell extension was causing all the problems. when
I turned the Laine extension off both google-chrome and chromium versions 75
(newest updates) worked again.
Both video and audio playback ran normally again.
--
You received this bug notification
I am currently doing improvements on the test script, making them
available here:
https://code.launchpad.net/~till-kamppeter/network-manager/+git/network-
manager/+merge/369586
I already added timrout s to the GLIb main loops so that in case of a
failure here nm.py continues with the other tests
** Tags added: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1603324
Title:
file-roller crashed with SIGSEGV in confirmation_dialog_response()
Status in file-roller
@Khurshid:
Maybe I'm missing something, but to me these desired 18.04 uploads don't
seem to be very sponsor friendly.
* I see a 18.04 repository for unity-control-center (just created a
link to it), but it does not seem to include the changelog update.
* As regards unity-settings-daemon I see
** Changed in: gupnp-dlna (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gupnp-dlna in Ubuntu.
https://bugs.launchpad.net/bugs/1785649
Title:
[MIR] gupnp-dlna
Status in gupnp-dlna package in
I'm testing now, and will report later.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1832123
Title:
[SRU] Bugfix release 1.14.5
Status in gst-libav1.0 package in
** Changed in: libreoffice-l10n (Ubuntu)
Status: In Progress => Fix Released
** Changed in: libreoffice (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Hi Sebastien.
Thank You for an answer. And I apologize for such a long time without my
answer. (An accident, nothing serious).
So Sebastien, please tell me, which informations exactly do you need?
I'm thinking about a `journalctl -b 0` command, of course. Is there
something specific, that you
This bug was fixed in the package libreoffice - 1:6.2.5-0ubuntu0.19.04.1
---
libreoffice (1:6.2.5-0ubuntu0.19.04.1) disco-security; urgency=medium
* New upstream release (LP: #1836759)
* Fixes CVE-2019-9848: LibreLogo arbitrary script execution
* Fixes CVE-2019-9849: Remote
This bug was fixed in the package libreoffice-l10n -
1:6.2.5-0ubuntu0.19.04.1
---
libreoffice-l10n (1:6.2.5-0ubuntu0.19.04.1) disco-security; urgency=medium
* New upstream release (LP: #1836759)
* Fixes CVE-2019-9848: LibreLogo arbitrary script execution
* Fixes CVE-2019-9849:
** Changed in: libreoffice-l10n (Ubuntu Disco)
Status: New => In Progress
** Changed in: libreoffice-l10n (Ubuntu)
Status: New => In Progress
** Changed in: libreoffice (Ubuntu Disco)
Status: New => In Progress
** Changed in: libreoffice (Ubuntu)
Status: New => In
** Summary changed:
- PDF files do not open. 'Failed to load backend for 'application/pdf':
libpdfdocument.so' and 'Invalid ELF header'.
+ PDF files don't open; "Failed to load backend for 'application/pdf':
libpdfdocument.so" and "Invalid ELF header".
** Description changed:
Hello.
On
Comments #17, #18, #19 are false positives - there aren't any
regressions.
Amr Ibrahim, if you wanted to test this that'd be appreciated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu.
@Ninad
It needs to be sponsored (who has merge access) for 18.04. I have asked
in the mailing list here
https://lists.launchpad.net/unity7maintainers/msg00026.html, You can
also ask in #ubuntu-desktop on irc.freenode.net but be polite. Meanwhile
you can use unity-7 maintainers PPA.
--
You
No reply to comment #2 from reporter
Report did not expire due to bug watch
Issue refers to the old interface
Aspect ratios changed in new interface
Upstream report closed 2018-02-10 "RESOLVED OBSOLETE"
Closing as report is no longer valid
** Changed in: gtk+2.0 (Ubuntu)
Status:
** Package changed: calendar (Ubuntu) => gnome-calendar (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1577527
Title:
Calendar Theme Issue
Status in gnome-calendar
** Package changed: calendar (Ubuntu) => gnome-calendar (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1405005
Title:
GNOME Calendar doesn't show correct first day of
You have been subscribed to a public bug:
When search for Calendar in Dash and then open Calendar there are little white
edges at the egde of the calendar with
Ambiance theme enabled? But when change the theme to Radiance or a community
created theme the white edges are gone?
This issue is in
You have been subscribed to a public bug:
Hi,
I'm using the PT-pt version of Ubuntu and since the beginning I noticed
that Ubuntu's Calendar starts with the wrong day. Instead of starting
with Sunday it starts with Monday. That is more a cultural issue than
other thing, but it's also a mistake.
May as well join the fun. Believed I tried every suggested work around
above, still got crackling.
In my case the crackling is present on the line-in 3.5mm jack plug and
not a microphone.
I run:
X470 GAMING PRO (MS-7B79) motherboard with a ALC892, Ryzen 2700, Radeon
RX Vega 54. Running Ubuntu
Maybe it's because of dpkg, apt, bad connection, unexpected interrupts,
etc. This error happens with any packages in the error messages but
it's never by bugs from those packages.
** Changed in: fonts-unfonts-core (Ubuntu)
Status: New => Invalid
--
You received this bug notification
See https://github.com/libhangul/ibus-hangul/issues/70
tl;dr
It cannot be fixed in ibus-hangul. Qt should be fixed.
** Bug watch added: github.com/libhangul/ibus-hangul/issues #70
https://github.com/libhangul/ibus-hangul/issues/70
** Changed in: ibus-hangul (Ubuntu)
Status: New =>
In the absence of a reply to comment #65, I can confirm that this is
still an issue with Thunderbird 60.8.0, tested in Ubuntu 19.10 (dev).
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
fyi, with the packages provided by Marco I still can reproduce the issue
with bionic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1793496
Title:
scaling changes when
** Package changed: ubuntu => gdm3 (Ubuntu)
** Tags added: disco
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1836805
Title:
screen frozen after reboot
Status in gdm3 package in
You have been subscribed to a public bug:
After I installed Ubuntu 19.04 (fresh install with hard drive erasing),
I was able to login once just after install. But then after reboot, the
screen freezes in the middle of the boot process and I never get the
login banner.
I was able to launch the
So mate used to be great but doesn't seem to be a solution anymore
either, type-ahead-find seemingly has been replaced for search-as-you-
type in mate sometimes this summer as well, too.
+1 for replacement, it could at least be a configuration option
--
You received this bug notification
Sorry for the delay.
I see what you mean, it seems true that firefox (suddenly?) adheres to
the documentation (and hasn't done so in the past?).
So in future we have to keep in mind that
$firefox -private
does not open a private window (anymore!) if another instance of firefox is
already
New version uploaded
https://launchpad.net/ubuntu/+source/duplicity/0.8.01-0ubuntu1
Some tests are failing on ppc64el though now, help with those would be
welcome
** Changed in: duplicity (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because
Public bug reported:
My gnome session freezes, mouse works fine but cannot start
applications. I am able to enter one of the tty terminals and kill the
session. This happens a few times a day and started a week ago probably.
Douglas
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg
The official fix landed upstream last night. It is fixed in mutter
version 3.33.4 and later.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1809407
Title:
[nvidia] Corrupted wallpaper
Hello,
A few weeks ago we fixed this bug with this script:
https://slimbook.es/tutoriales/linux/422-fixing-the-broken-desktop-
after-resuming-from-a-suspension-in-gnome
I hope it helps someone.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Also happens in X11 with Ubuntu 19.04. Often moving anything in the
desktop to trash restarts the shell or simply hangs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
I don't understand how we're getting two instances of this crash in
version 1:11.1-1ubuntu7.3.
It sounds like either someone built their own package by the same name,
or errors.ubuntu.com is not grouping the crashes correctly.
I say this because the fix does:
+++
** Changed in: network-manager (Ubuntu)
Importance: Low => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
https://lkml.org/lkml/2019/7/17/116
** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
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/1832988
*** This bug is a duplicate of bug 1690052 ***
https://bugs.launchpad.net/bugs/1690052
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pulseaudio. This problem was most recently seen with package version
1:11.1-1ubuntu7.2, the problem
*** This bug is a duplicate of bug 1690052 ***
https://bugs.launchpad.net/bugs/1690052
** This bug has been marked a duplicate of bug 1690052
pulseaudio crashed with SIGABRT in transport_state_changed_cb() from
pa_hook_fire() from pa_bluetooth_transport_set_state()
--
You received this
** Summary changed:
- pulseaudio crashed with SIGABRT in transport_state_changed_cb() from
pa_hook_fire() from pa_bluetooth_transport_set_state() from
endpoint_set_configuration() from endpoint_handler()
+ pulseaudio crashed with SIGABRT in transport_state_changed_cb() from
pa_hook_fire() from
*** This bug is a duplicate of bug 1690052 ***
https://bugs.launchpad.net/bugs/1690052
** This bug has been marked a duplicate of bug 1690052
pulseaudio crashed with SIGABRT in transport_state_changed_cb() from
pa_hook_fire() from pa_bluetooth_transport_set_state()
--
You received this
*** This bug is a duplicate of bug 1690052 ***
https://bugs.launchpad.net/bugs/1690052
** This bug has been marked a duplicate of bug 1690052
pulseaudio crashed with SIGABRT in transport_state_changed_cb() from
pa_hook_fire() from pa_bluetooth_transport_set_state()
--
You received this
*** This bug is a duplicate of bug 1690052 ***
https://bugs.launchpad.net/bugs/1690052
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pulseaudio. This problem was most recently seen with package version
1:12.2-0ubuntu5, the problem page
*** This bug is a duplicate of bug 1690052 ***
https://bugs.launchpad.net/bugs/1690052
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pulseaudio. This problem was most recently seen with package version
1:12.2-0ubuntu5, the problem page
I have HP Spectre X360 13" 2019 Model, and have the same problem.
After the touch pen/stylus is detected, finger touch stops working. Is
there any workaround or command to get it working again?
--
You received this bug notification because you are a member of Desktop
Packages, which is
56 matches
Mail list logo
