** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+attachment/5299096/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+attachment/5299095/+files/dmesg.txt
--
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.
Public bug reported:
I tried to change my monospace font to "Noto Sans Mono Bold" in
/etc/fonts/local.conf but that didn't have an effect so I did a little digging.
First I ran
$ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config
Which succeeded, then:
$ fc-list :style=
[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:/
Dropped the bionic task until such time as this becomes a reproducible
and testable bug there.
** No longer affects: mutter (Ubuntu 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/b
*** This bug is a duplicate of bug 1849249 ***
https://bugs.launchpad.net/bugs/1849249
** This bug has been marked a duplicate of bug 1849249
gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed:
(workspace == NULL)
--
You receiv
*** This bug is a duplicate of bug 1849249 ***
https://bugs.launchpad.net/bugs/1849249
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.34.1-1ubuntu1, the problem page
Thanks for the bug report. Tracking in:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
** Summary changed:
- gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed:
(workspace
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing gno
Thanks for the bug report and screenshot. That does confirm it is
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
** Tags added: eoan
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
Importance: Unknown
Status: Unknown
** Changed in: gno
*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1847570, so it is being marked as such. Please look
** Package changed: alsa-driver (Ubuntu) => gnome-control-center
(Ubuntu)
** Also affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a mem
I will need to debug this more in detail. If we find it is Xorg giving
us the negative pointer coordinates then it should be fixed there. But
it might just be a mutter bug...
** Tags added: rls-ee-incoming
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt
You have been subscribed to a public bug:
When System Starts, first time Bluetooth devices(Say headphones) get
connected smoothly. But after a point when headphones get disconnected,
If I tried to reconnect Bluetooth settings don't list the devices. I
turned it on/off multiple times but doesn't wo
*** This bug is a duplicate of bug 1845801 ***
https://bugs.launchpad.net/bugs/1845801
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1845801, so it is being marked as such. Please look
Thanks but that didn't attach as much info as I had hoped.
Please run:
lspci -k > lspcik.txt
dmesg > dmesg.txt
and then attach the files 'lspcik.txt' and 'dmesg.txt'.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell i
** Tags added: eoan
** Package changed: ubuntu => gdm (Ubuntu)
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1849050
Title:
19.10 f
I think this is a duplicate of bug 1847570. If you agree, will you mark
it as a duplicate?
--
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/1849157
Title:
Default sound output d
You are absolutely right. See bug 701186 :)
--
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/1782425
Title:
Unable to change Power off timeout from 60 seconds ("The system will
You have been subscribed to a public bug:
BUG - based on clean install 19.10 desktop x86-64
If user selects "Log me in Automatically" on install, then they can
never login from the desktop login prompt.
The system appears to login the use, but not actually show the session.
Dropping to a differe
It was already reported.
Here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
And here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1601
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1649
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1649
** Bug watch added:
It has been fixed in Fedora and Arch, where is the fix for Ubuntu?
--
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/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color profil
Thanks for testing a GNOME session, it would be nice to report it upstream as
well since it doesn't seem to be due to some extension or Ubuntu specific
components
https://gitlab.gnome.org/GNOME/gnome-shell/issues
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You rece
What's the output of `gcc --version`?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865
Title:
Xubuntu 18.04 sometimes freezes when turned on on logo
To manage notifications abo
On 2019-10-21 19:27, Sebastien Bacher wrote:
> The sync is failing due to 'ConditionFileIsExecutable=!/usr/sbin/ntpd'
That file would be provided by the universe package ntp. Are there
reasons to move it back to main?
--
You received this bug notification because you are a member of Ubuntu
Deskt
The sync is failing due to 'ConditionFileIsExecutable=!/usr/sbin/ntpd'
--
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/1848309
Title:
"Automatic Date & Time" is broken
Public bug reported:
According to this page:
https://wiki.ubuntu.com/Sound#Primary_sound_output, "if you manually
choose an output device in the “Sound” settings panel or a similar
utility, that choice should be followed". Well, despite me having
explicitly selected the headset as the output devic
sudo systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
└─disable-with-time-d
No extensions were installed. Also, I'm using the native AMDGPU drivers,
not the proprietary ones.
I've tested the vanilla GNOME session as you suggested, and the bug is
there too. Due to the hover highlighting of the panel items, I had a
visual cue to test with. The highlighting does not happen a
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
Thank you for your bug report? Do you have any extension installed?
Could you test if that's also happening in a GNOME session (you need to
install 'gnome-session:' to have the session listed on the login
screen)?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You receiv
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
--
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
the sudo error is known, nautilus isn't meant to be used as superuser
--
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/1849106
Title:
After upgrading to 19.10, files crashes when I
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
- Impor
Public bug reported:
Updated bug #1817073 about this, but it's not really the same since this
does not crash the shell fully.
When speaking in discord there is supposed to be an icon change on the
appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to
lookup icon for discord1_40
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
+ Impor
Too quick on that one, was not fixed just by reinstalling
gnome-shell-extension-appindicator. Now i also noticed that this isn't just in
the game, the whole desktop freezes for a moment when talking in discord if the
appindicator package is installed.
Easily reproduced by joining a voice channel
Public bug reported:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It is unresponsive to
clicks to open the overlay, BUT it responds to clicks to close it.
The unclickable spot is exactly one pixel large.
Specs:
- Graphics: AMD
Tried it again and it didn't give me a crash report, then i tried it and it
launched but the game frooze, was able to open gnome activities and close the
game but then the main screen in the game was still on half of the screen
frozen.
However if i click to launch the game, then directly open th
** Attachment added: "Journalctl logs"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849135/+attachment/5298947/+files/journalctl.txt
** Description changed:
Starting from Ubuntu 19.10, the top-left corner of the screen is
unclickable. It's where the Activities button is. It
So that's consistent with the switch status.
Can you change the status in the setting and do
$ systemctl status systemd-timesyncd.service
and copy the log here?
What happens if you try then to enable sync with that command instead of the
settings?
$ timedatectl set-ntp true
--
You received thi
$ timedatectl status
Local time: Mon 2019-10-21 15:46:41 CEST
Universal time: Mon 2019-10-21 13:46:41 UTC
RTC time: Mon 2019-10-21 13:46:37
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
NTP service: inac
what's the output of 'timedatectl status'?
--
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/1848309
Title:
"Automatic Date & Time" is broken
To manage notifications abo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-app
Sorry if I'm being naughty, but on this case the proper status should
not be "Won't fix"?
--
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/1782425
Title:
Unable to change Power o
Public bug reported:
After upgrading to 19.10, files crashes when I try to move some items to
trash.
Then I opened nautilus with 'sudo nautilus' in the terminal and there I
was able to delete items, but when I go to the trash folder, it says
'This location could not be displayed.
Sorry, could n
As I wrote, I was using the very latest Eoan packages for the past
months as this bug occurred and persisted. Therefore I could not provide
any specific Ubuntu version as the version number was just "latest
development".
## related jounrnalctl messages
Oct 21 12:37:19 sun dbus-daemon[
The bug only happens if a file with an equal prefix exists, e.g. after
`vim 'A123$B123#asdasd'`.
I am using bash, but the problem also happens in zsh if I enter
`A123\$B123\#`, hit tab, enter `<` and than hit tab again. It does not
happen in zsh if I hit tab again and again and it switches between
Autocompletion is done by the shell and its configs, not by the
terminal.
** Also affects: bash-completion (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Public bug reported:
The autocompletion of the terminal does not work correct for some
special signs, e.g. if I edit a file by
vim "A123\$B123#_asd"
it is not possible to get it for autocompletion afterwards.
If I enter cat `A123\$B123#` and then hit tab two times, the file is
display corre
apport information
** Tags added: apport-collected
** Description changed:
- I have graphics artefacts: screan tearing, pieces of the previous window
- appear in the newly opened window.
+ I have graphics artefacts: screan tearing, pieces of the previous window
appear in the newly opened window
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1848741/+attachment/5298854/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1848741/+attachment/5298851/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1848741/+attachment/5298853/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
Some of those I enabled at one point but am no longer using.
On 10/20/19 11:39 PM, Daniel van Vugt wrote:
> Thanks. It seems you have a number of extensions. Do they all have the
> problem or just some?
>
> 'ubuntu-d...@ubuntu.com'
> 'activities-button-text@nls1729'
> 'dynamictop...@gnomeshell.fei
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1848741/+attachment/5298852/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
We know. That's just a Launchpad bug where it doesn't know the
difference.
--
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/1782425
Title:
Unable to change Power off timeout from
@vanvugt: Not sure if I'm missing something, but the bug was not fixed
in Gnome, just closed.
--
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/1782425
Title:
Unable to change Pow
*** This bug is a duplicate of bug 1817128 ***
https://bugs.launchpad.net/bugs/1817128
I've summarized my investigation so far in this new bug report:
It seems a combination of ZSH, Oh-My-Zsh and possibly Powerlevel10k
break the login screen somehow.
https://bugs.launchpad.net/ubuntu/+source
** Changed in: nautilus
Status: Unknown => New
--
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/1800043
Title:
nautilus cannot write on nfs file share base dir
To manage not
Thanks,
I've raised several issues to try to fix this problem:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081
https://github.com/robbyrussell/oh-my-zsh/issues/8296
https://github.com/romkatv/powerlevel10k/issues/280
** Bug watch added: github.com/robbyrussell/oh-my-zsh/issue
I've cross-posted this issue in the related tools since it's unclear
which one causes it, but it's severe enough to make it worth triaging
it.
https://github.com/robbyrussell/oh-my-zsh/issues/8296
https://github.com/romkatv/powerlevel10k/issues/280
** Bug watch added: github.com/robbyrussell/oh-
Public bug reported:
There's a bug that affects gnome-keyring, and i'll describe the steps i've done
to reproduce it twice, although i don't have
full details as to what exactly is causing it.
Issue can be summarized as follows:
On Ubuntu 19.10, but not at least 18.04 (another computer i have u
You mean doing upstream work to add support for it? No, I don't think
so.
** Summary changed:
- HDR support for Ubuntu 20.04
+ HDR support for Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.laun
It?? could be the open-weather extension which is causing the error.
On 10/21/19 1:29 AM, Daniel van Vugt wrote:
> Yes, gnome-shell kicks them out if they have errors. And definitely some
> have errors (see the log in comment #7).
>
> It sounds like maybe it's kicking out multiple extensions based
Yes, gnome-shell kicks them out if they have errors. And definitely some
have errors (see the log in comment #7).
It sounds like maybe it's kicking out multiple extensions based on them
being loaded together?...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
*** This bug is a duplicate of bug 1847974 ***
https://bugs.launchpad.net/bugs/1847974
** This bug is no longer a duplicate of bug 1426851
Power button shuts down computer if a Qt application is running
** This bug has been marked a duplicate of bug 1847974
Qt apps terminate on Power-Off
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => Low
--
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
** Summary changed:
- Some apps terminates on Power-Off dialog
+ Qt apps terminate on Power-Off dialog
** Package changed: gnome-shell (Ubuntu) => qtbase-opensource-src
(Ubuntu)
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Opinion => Confirmed
--
You received this bug notificat
The extensions do load when I enable them.?? The problem is that after a
reboot
they are not enabled and I need to do it by hand. This does not happen
after
every reboot but occurs often enough when I start up the computer that
it's annoying.
On 10/21/19 12:59 AM, Daniel van Vugt wrote:
>
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/1031
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https:
The issue was resolved in Ubuntu 19.10, the dock lists devices now. If
you have problems with the implementation best to open a new report
describing the details
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notificat
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
--
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/1844650
Title:
No authentication window pops up if thunderbolt
The log in comment #7 shows a number of your extensions are failing to
load because they are not yet compatible with Gnome 3.34 or at least
Ubuntu's Gnome 3.34.
Please try them one-by-one to see which ones work and which don't. If
it's only a subset of them then we should use bug 1835706 instead,
** Also affects: gnome-shell-extension-weather (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs/1835706
T
@Rex
The link is on also-affect project list.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1794
--
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/1844650
Title:
No authenti
@cktenn please kindly provide the link of the issue on gnome-shell
project. Thanks
--
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/1844650
Title:
No authentication window pops u
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Invalid
--
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/1848940
Title:
gnome-control-center doe
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #884
https://gitlab.gnome.org/GNOME/nautilus/issues/884
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/884
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
The report lack basic informations, please submit using ubuntu-bug. Like the
Ubuntu version used isn't even specified.
Could you also add your 'journalctl -b 0' log?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you ar
** Changed in: xorg-server
Status: Unknown => New
--
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/1846398
Title:
Fractional scaling has significant visible refreshes on a 4k d
82 matches
Mail list logo
