I too ran
sudo add-apt-repository ppa:ci-train-ppa-service/3801
sudo apt-get update
(new system d was installed)
I can second it had no effect; can't login after autologin has been
turned on and it sure does no automic login, the only option i know from
there is to boot from recovery mode and
This this might be worth tracking and working on as a bug rather than a
wishlist item; adding rls-incoming tags to request this is considered by
the team.
Rationale: this bug means that clicking notifications often doesn't do
anything, which is both a regression and kind of annoying / confusing.
Thanks for your bug report, indeed it doesn't use the removable-media
interface
** Changed in: evince (Ubuntu)
Status: New => Confirmed
** Changed in: evince (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Looking to the backtrace of the other report
font_name =
Looks like font_name can be null but the code doesn't handle that case
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
The issue was fixed upstream with that commit
https://gitlab.gnome.org/GNOME/evince/commit/29e8e55f
** Changed in: evince (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
It looks like it was fixed upstream with that commit
https://sourceforge.net/p/djvu/djvulibre-git/ci/8407dd34
** Changed in: evince (Ubuntu)
Status: New => Invalid
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: djvulibre (Ubuntu)
Importance: Undecided =>
The segfault is in the code of the patch added by Julian to fix bug
#1830473
Julian, could you have a look to this regression?
** Tags added: lts-desktop-wishlist
** Changed in: evince (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification
Julian, could you also add one of those OCR generated PDF that created
the initial issue to launchpad? would make easier to test the patch in
newer versions
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1870
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1870
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Public bug reported:
Crashed with Xorg crashed when resume the system from suspend when using
dual screen with nvidia-driver
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.4-0~ubuntu18.04.4
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux
** Tags added: 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/1844026
Title:
nautilus crashed with SIGSEGV
To manage notifications about this bug go to:
>What webbrowser do you use?
Chrome
>Did you try to install from gnome-software instead?
It doesn't work in gnome-software either. Additional behaviors observed
in gnome-software:
1) When I try to _uninstall_ the extension from inside gnome-software,
it says it can't uninstall it, but it
The extension won't turn on in Wayland either.
--
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/1851554
Title:
can't install gnome shell extensions
To manage notifications
Public bug reported:
Here's what I'm trying to do:
1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/
2. Click the toggle switch to install it.
3. Use the extension after it is installed.
Here's what should happen:
1. I am prompted for confirmation to install the
Oh no the bug happens again with the desktop icons properly set, so it
is not the root cause, pfff
I'm setting up at work and home the same Linux setup, at home this is
the focus bug fest, at work the bug never happened a single time ! Every
click success and I do not have the problems I have at
*** This bug is a duplicate of bug 1844026 ***
https://bugs.launchpad.net/bugs/1844026
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1844026, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
Public bug reported:
This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have
logs going back to mid august. The message is repeated for each
calendar at various times.
Nov 06 13:49:13 dipper gnome-calendar[8681]:
source_credentials_required_cb: Failed to authenticate 'Kai
Thank you for your bug report. What webbrowser do you use? Did you try
to install from gnome-software instead?
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Public bug reported:
I have an ultrawide monitor plugged into my laptop. When I log into a
Wayland session, my monitor configuration (resolution, relative
position, which monitor is the primary) is not restored correctly. When
I unplug the monitor cable after logging in and plug it in again, the
Can't reproduce this one but a variant easy to trigger here is
- click on a snap in gnome-software
- click install
- enter password
- go back to the apps list
- select the snap again
while it's installing the bar is not there anymore but it has an
'install' button, which gives an error stating
Public bug reported:
1) I use SecureCRT (Session Manager) and this program have float windows
"Session Manager"
It will dissapper when lost focus for this windows and not showing by click on
button in program.
2) Same in wine with MSO2007 (popup menu for office is dissappear after first
click)
Christoph, is your device a Yubikey? If not would you mind filing a new
bug report with all the details by running `ubuntu-bug chromium-browser`
?
The relevant denial seems to be:
[ 7049.256201] audit: type=1400 audit(1572541725.870:246):
apparmor="DENIED" operation="open"
Is there a bug for the Debian side of things?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1819779
Title:
Stick to the 3.30 serie still?
To manage notifications about
Public bug reported:
I was trying to bring my Firefox window to front by pressing Super+2
(it's my second pinned launcher), and gnome-shell crashed.
journalctl shows this:
lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed
UTF-8 character sequence at offset 0
Nevermind, I hadn't realized you had filed bug #1851211 already. Let's
continue the discussion there.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap]
** Changed in: gnome-software
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1843698
Title:
gnome-software crashed with SIGSEGV in
So I just upgraded to 19.10 and I am _STILL_ having this issue. I have
had this issue now through two whole major releases! SMB1 being turned
off _SHOULD NOT BREAK THIS_. SMB1 is a _MAJOR_ security threat, and this
really needs to get fixed!
I've been reporting this failure since April of 2019 :/
And as a reminder, my "solution" is to:
1. trigger the error by trying to browse to an SMB share with SMB1 disabled on
the server-side
2. "pidof gvfsd-smb-browse"
3. "kill $PID" from above (regular kill, not -9)
It then works, I can actually get to shares.
I have to do this after _every_
apport information
** Tags added: apport-collected
** Description changed:
With the upgrade to eoan, my GNOME and Ubuntu sessions started locking
up hard when under load (i.e. when I start my session and start a bunch
of applications).
I couldn't find anything special in gdb, whether
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1850615/+attachment/5303381/+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.
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1850615/+attachment/5303378/+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.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1850615/+attachment/5303382/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1850615/+attachment/5303379/+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.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1850615/+attachment/5303380/+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.
I just had it locked up a number of times with all the extensions
disabled. Trace looked basically the same. It seems to be launching
Thunderbird (it takes a while due to calendars…) that's triggering this
most often.
--
You received this bug notification because you are a member of Ubuntu
If it's any bit of helpful information, I occasionally have this issue
(on 18.04) and it is fixed by a proper shutdown and boot. It seems to
happen for me when one of the servers that I sshfs to crashes/becomes
unavailable (or something else server side) and the issue persists past
the time in
Public bug reported:
gnome-terminal writes debug messages to stderr every time it starts up:
# _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for
‘gio-vfs’
# _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
#
apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace
/var/crash/_usr_bin_gnome-shell.1000.crash
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Toks failas
The JS traceback points to this line:
https://gitlab.gnome.org/GNOME/gnome-shell/blob/3913fa5044b2cd1d5abadc9b4254d06215491458/js/ui/windowManager.js#L1771
(GitLab commit doesn't match gnome-shell from Ubuntu 19.10, sorry! I
didn't have the time to go hunt for the exact commit that corresponds
I would rather not getting involved into too many bugtrackers, and as a
Ubuntu user, remain on Launchpad and provide the required information to
let you investigate.
Also, as you are a member of Ubuntu teams, you have more
authority/credibility than me, so that bug can be taken seriously by
Public bug reported:
gnome-terminal -e 'command...' emits a warning:
# Option “-e” is deprecated and might be removed in a later version of
gnome-terminal.
# Use “-- ” to terminate the options and put the command line to execute after
it.
However this is contrary to the man page, which says
Issue is still in Ubuntu 19.10 with vmware workstation player 15.5.
One workaround I found is to use gnome-tweaks to select the wallpaper (under
Appearance), and select an Adjustment option of "Wallpaper". Any other
adjustment option causes the white background. Works best with a
I experience this bug, too. What is interesting is that even if:
1. I hide the top bar of gnome shell with extension,
2. Disable dash-to-dock and
3. Bring a window so it occupies the most top-left corner (or maximize it),
the windows does not react if I click the corner. In this case the
44 matches
Mail list logo
