Thanks. It sounds like a few different DisplayLink problems.
It appears the display-related crashes are all in Xorg, Xwayland and
DisplayLinkManager. The last one doesn't seem to be part of Ubuntu so
I'll ignore that here. So the remaining two both come from the 'xorg-
server' source package.
Unf
By the way, my "journalctl" is full of this, maybe related, maybe not...
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: Errors:
févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]:
[4886:4886:0205/073611.340319:ERROR:shared_context_state.cc(74)] Skia shader
compilation error
févr. 05 0
Hello,
1. I have 3 crash files in /var/crash but the ubuntu-bug command fail.
Each one has a ".upload" and ".uploaded" file so I think they're already
uploaded. Shall I empty the folder to have a clean start point for next
time the bug appear?
2. Many files in this page. These are the 3 related w
[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:/
Thanks for the bug report. Please try the workaround from bug 1896164.
** Tags added: raspi raspi-gfx
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
> Maybe old bug reports are incorrectly attached to newer packages.
That would certainly explain the weird stack traces and lack of working
debug symbols.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Just an update, for what it's worth.
I solved this problem with a shell script triggered by Network Manager's
"up" hook. Because UU does not update the package list, I had to resort
to a `apt-get update && apt-get dist-upgrade` with
`DEBIAN_FRONTEND=noninteractive` and a whole bunch of options to
** Summary changed:
- UU should work on roaming laptops
+ Unattended upgrades should work on roaming laptops
--
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/1886161
Tit
Maybe old bug reports are incorrectly attached to newer packages.
Focal, Bionic and others also have "zombie updates" : update-notifier on
Focal, gnome-calculator and nautilus on Bionic. Those last two have been
zombified more than one year ago (moreover at the same time it seems).
Have a look her
I wonder if it could be a bug related to the crash reporting software
instead. What looks strange (but maybe I'm not reading it correctly) is
that the publishing history indicates it was brought back to 0% even
before it was put at 10% : https://launchpad.net/ubuntu/groovy/amd64
/gnome-shell
It se
** Description changed:
Add option to enable screen-keyboard icon for panel
- (it help users to open screen keyboard only when necessary, not everytime
when touch on text field or typing field)
- (Currently if enable it through universal access > screen keyboard then it
makes quite annoying
** Description changed:
- Add option to enable screen-keyboard icon in dock
+ Add option to enable screen-keyboard icon for panel
(it help users to open screen keyboard only when necessary, not everytime
when touch on text field or typing field)
(Currently if enable it through universal a
** Information type changed from Public to Public Security
--
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/1914583
Title:
unresponsive gnome de on 20.10
To manage notifications
** Description changed:
- Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz.
- Even with disabled animation and 1 static workspace, gnome de is still
generally not quite responsive: list of apps takes about 5 secs to display,
opening a folder in app list takes about 2 secs, a
Public bug reported:
Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz.
Even with disabled animation and 1 static workspace, gnome de is still
generally not quite responsive: list of apps takes about 5 secs to display,
opening a folder in app list takes about 2 secs, almost ev
Fixed in xenial. This issue can be closed, as not appearing in currently
maintained distributions.
** Changed in: evolution (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubunt
I am also seeing this behaviour on 20.04.1 - it is confusing. I also see it
when I open Cypress from within a terminal inside JetBrains PhpStorm - the
chrome windows opened by that are co-located with the PhpStorm 'pips'.
This makes ctrl-tabbing between open applications difficult.
--
You recei
the upstream report was closed on the basis that blueman was used and
not gnome bluetooth, is it the case here? do you still get the issue and
tried under GNOME?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu
Public bug reported:
The bug is that all at a sudden gnome reset to login screen. When i log
again, the only "sound output" allowed is simulation, my devices are not
displayed.
I'm using
- Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was
present at that moment but i
** Changed in: gnome-bluetooth
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1857891
Title:
Authentication code required for keyboardles
Is there anyone here who is experiencing this bug, or can reproduce it?
--
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/1913672
Title:
gnome-shell 3.38.2-1ubuntu1~20.10.1 is cra
23 matches
Mail list logo
