Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
I am seeing this with the (relatively new) Mozilla-provided Firefox deb
package (https://support.mozilla.org/en-US/kb/install-firefox-
linux#w_install-firefox-deb-package-for-debian-based-distributions).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I got it also in recent version, you need then to go to system software
update, and then it is now working. But from a user perspective, not
good.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
Still an issue with current releases. Default GNOME/libinputa doesn't
enable tap-to-click, but Ubuntu does for the GNOME desktop, and
therefore it should also for GDM.
Easy workaround posted in duplicate bug:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1968315/comments/1
--
You received
Ubuntu 23.10 (mantic), and disregard. Reinstalled and it's not any issue
anymore(?)
--
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/2038789
Title:
Password for VPN not
Public bug reported:
Cannot change password of a VPN connection. It doesn't get saved when
you click "Apply".
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: mantic
--
You received this bug notification because you are a member of Ubuntu
Worth noting this looks to be a bug in the official GNOME 45 release?
** Also affects: network-manager-openvpn (Fedora)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
here are some files from apport from the crash on my PC.
** Attachment added: "Gnome-software crash info.zip"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2032119/+attachment/5695077/+files/Gnome-software%20crash%20info.zip
** Tags added: crash
--
You received this bug
** Attachment added: "ProcEnviron"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2032119/+attachment/5695076/+files/ProcEnviron
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
** Attachment added: "Dependencies"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2032119/+attachment/5695075/+files/Dependencies
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
Same problem here, upgraded from 23.04 today and unable to open gnome-
software on Ubuntu 23.10
--
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/2032119
Title:
unable to open
PS: Before I forget, I also tested something else, see attached
screenshot. Going into nvidia-settings and manually setting the
PowerMizer mode to "prefer maximum performance" makes all animations,
the overview and everything related to it super smooth fps-wise. You can
make this permanent by
xrandrv.txt as requested by Dan
** Attachment added: "xrandrv.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688576/+files/xrandrv.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Hi Daniel,
I will follow your suggestion and try to find the time to create a new
bug report for the additional issues that occured. That said, since the
drive on this machine suffered from what I wrote above, I decided to
quickly format and perform the steps that you suggested on a fresh
Ubuntu
** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-01.png"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688204/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-01.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Screenshots: Ubuntu 22.04.2 LTS, partial upgrade option after Nvidia
driver 535 went live.
** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-07.png"
Hello Daniel, I apologize for the huge delay, but I have been
experiencing a number of show stopping issues that I have yet to recover
from.
As written above: After all the issues that I had with Ubuntu 23.04, I
decided to "downgrade" to Ubuntu 22.04.2, which was working just fine at
first, see
Hey there Daniel,
thanks for helping out! I can confirm that what nuked my 23.04 install
is bug 2023946, which I responded to a few days ago. While trying to fix
the issue at hand, before I read your suggestion on how to potentially
fix it, I followed a howto online, which was more or less
This is what Ubuntu wanted to download after the first update attempt
** Attachment added: "Nvidia 530 on 2304 nuke"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5680190/+files/nvidia%20nuke%202304.png
--
You received this bug notification because you are a
Hello Daniel,
thanks for taking a look! Not sure if I am going to be able to test this
after all. I just ran Ubuntu 23.04 updates like I always do, and noticed
that 23.04 now has access to Nvidia driver 530, so I ran Ubuntu updates,
which unfortunately nuked my Ubuntu install.
This is what
> in gtk, kinetic scrolling stops after you put a finger on the touchpad
(zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have
to wait
In GTK 4, and Firefox uses GTK 3. So either someone need to add it to
GTK 3 or Firefox needs to use to GTK 4.
--
You received this bug
Btw, I just noticed that some drop down windows, such as the ones in the
Chromium Snap, also have a little bit of pixelation in them when vsync
is active in nvidia-settings.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
I run Ubuntu 22.04.02 on a Lenovo Legion 5i pro.
There was a bug when I switched on Wayland session.
I followed instructions that are described above and deleted gnome extention
aplication.
And I've got no issues any more with lock my laptop and black screen. It's
fantastic!
My conclusion is,
Resolved since GTK was updated to 3.24.36. (Tested with
3.24.36-1ubuntu1.)
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
Public bug reported:
With GTK 3.24.35, when running under Wayland, it's not possible to copy
and paste from Geany. (Others report the same issue with SciTE, which
also uses the Scintilla editor.)
The Geany upsteam bug isolated the issue to a GTK change
Also note that there is no requirement to have Secure Boot enabled in
Cyber Essentials.
--
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/1987162
Title:
43: New Device
@billdietrich444
Note: my comment is a trolling attempt, and hopefully an obvious one due
to the choice of an obviously unimplementable-in-a-useful-way standard.
Please take only 10% seriously.
It may be a good idea to stop talking about pure security according to
our own set of criteria
*** This bug is a duplicate of bug 1873075 ***
https://bugs.launchpad.net/bugs/1873075
I was also affected by this. From journalctl it looked driver-related.
Updated drivers, logged in and out seemed to fix it.
Will update if it happens again.
--
You received this bug notification because
I'm seeing the same symptoms, screen scaling 125% gives 200%, when
accessing a Ubuntu 20.04 VMware system via xdrp from Windows 10. My
graphics driver is
root@geoff-ubuntu-2004:~# lshw -c video
*-display
description: VGA compatible controller
product: SVGA II
I stand corrected: fractional scaling on/off persists. The scale (100%)
does not, it jumps back to 200% and my Chrome windows that were on the
external screens are back on the internal display.
The latter was already reported as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948
I am
Public bug reported:
My setup:
Dell XPS 13 7390 2-in-1, internal display (3840x2400)
First external monitor: Dell 24" running at 2560x1440 connected via
USB-C/Thunderbolt
Second external monitor: same, connected to the first monitor via DP
Scale of the internal display set to 200%, fractional
I have a Dell XPS 13 7390 2-in-1 with two external monitors.
The first external monitor is connected via USB-C/Thunderbolt, the
second one via DP from the first external monitor.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter
Public bug reported:
What I expect:
Window layout/positioning is identical after resume from sleep.
What I observe:
After resume from sleep, windows appear on a different monitor than
before.
I found this possibly relevant GNOME bug:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1419
Public bug reported:
I don't know if it is the right package against which I opened the bug report.
Unfortunately, under the new Ubuntu version 21.04, it is not possible to share
windows of many applications in videoconferences (due to Wayland?). This is a
big problem considering that many in
Public bug reported:
Segfaults seemingly, I haven't changed any theme stuff and it worked on
a fresh install so I don't know what's causing this.
Also if it's helpful this doesn't seem to be an issue with Ubuntu itself
as it happened on Intel's Clear Linux so it appears to be GNOME.
And here, too:
Section "InputClass"
Identifier "libinput touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Option "InvertY" "true"
Driver "libinput"
EndSection
--
You received this bug notification because you are a member
It was added to the intel_vt blacklist to make the volume buttons work.
`blacklist intel_vbtn`
--
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/1918007
Title:
This happens from
I did the same thing in Chrome Browser.
The Chrome Browser does not select the text well and copies 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/1918007
Title:
This
This is a clean minimal installation. In addition, Yandex Browser was installed
and the command was executed:
sudo apt-get install chrome-gnome-shell.
Installed extensions:
Desktop Icons
Block Caribou 36
Horizontal workspaces
Ubuntu AppIndicators
Ubuntu Dock
User Themes
Window List
Workspace
** Description changed:
- Now it seemed that my car would take off. The fan was spinning long and
- loud, and the three files are _usr_bin_gnome-shell. 1000*were created in
- the var/crash /directory.
+ Now it seemed that my car would take off. The fan was spinning long and loud,
and the three
I had to make a new report: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1918007
--
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/1917660
Title:
This happens from
Public bug reported:
Now it seemed that my car would take off. The fan was spinning long and
loud, and the three files are _usr_bin_gnome-shell. 1000*were created in
the var/crash /directory.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
Thank you, I temporarily lost my account and had to contact customer
support.
--
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/1917660
Title:
This happens from time to time,
** Attachment removed: "monitors.xml.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472220/+files/monitors.xml.txt
** Attachment removed: "ProcCpuinfoMinimal.txt"
** Description changed:
- Now it seemed that my device would take off. The fan was spinning for a
- long time and loudly, and three files _usr_bin_gnome-shell.1000*were
- created in the var/crash/ directory.
+ Теперь казалось, что мой аппарат взлетит. Вентилятор крутился долго и громко,
а три
Public bug reported:
Now it seemed that my device would take off. The fan was spinning for a
long time and loudly, and three files _usr_bin_gnome-shell.1000*were
created in the var/crash/ directory.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
Public bug reported:
This error is not caused by additional software, it occurs in the file manager
even before installing ubuntu in trial mode.
These are black pop-ups that block subsequent input of commands, and that
remain on the screen for too long.
These windows are descriptions of
Opened a bug report on Gnomes Gitlab:
https://gitlab.gnome.org/GNOME/shotwell/-/issues/323
** Bug watch added: gitlab.gnome.org/GNOME/shotwell/-/issues #323
https://gitlab.gnome.org/GNOME/shotwell/-/issues/323
--
You received this bug notification because you are a member of Ubuntu
Desktop
More than ten years later, I still have the same problem. (Ubuntu 20.10;
Shotwell 0.30.10)). Shouldn't such a bug also be marked as a security
issue? Isn't such a memory overflow potentially dangerous?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
-brightness-
controller-utility-in-ubuntu-16-04-higher/ but it had no effect ...)
Could this be related to the above described issue?
Best
Alexander
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https
Thanks for the answer,
you can find the the requested file appended.
Best
Alexander
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5437516/+files/lspci.txt
--
You received this bug notification because you ar
> I can confirm that toggling repeat keys off and on again fixes the
issue temporarily for the current session.
Also changing the repeat speed.
It would be nice if this toggling would be possible from CLI.
This way I wouldn't have to go in the settings every time my computer woke up
from sleep.
Ok,
I booted, waited some minutes where the screen gets stuck black/purple,
powered off and booted to recovery mode to collect `journalctl -b-1`.
You can find the file appended.
Maybe my system is booting correctly but the X Windows System is not
able to load?
Best
Alexander
** Attachment
Sorry, the BTW above was nonsense.
When trying to boot using `Advanced Options` in BIOS and choose Ubuntu
there, the screen shows
`
Loading Linux5.4.0-53-generic ...
Loading initial ramdisk
`
and gets stuck there.
The strange comes now: if I open the bootscript for Ubuntu in BIOS
removing one
** Attachment added: "prevboot2.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435258/+files/prevboot2.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
sorry appended file abve seems not to work.
** Attachment added: "prevboot1.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435257/+files/prevboot1.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
purple screen.
Best
Alexander
** Attachment added: "prevboot"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435256/+files/prevboot
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1904474/+attachment/5435255/+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.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1904474/+attachment/5435254/+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: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1904474/+attachment/5435253/+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.
.
Btw. I have a dual boot with Windows 10, but I do not know if this is
relevant for this issue.
Best
Alexander
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.20
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.04
Bug is still happening on Ubuntu 20.04.1 LTS.
I'm using an external Apple Alu Keyboard.
The interesting thing is, that repeat rate and delay are correct for the
internal keyboard of the notebook but they are wrong for the plugged in
keyboard.
If I go into settings and set it again it is correct
** Changed in: mutter (Ubuntu Bionic)
Assignee: Daniel van Vugt (vanvugt) => Tyler Alexander Driggers (exderia)
** Changed in: mutter (Ubuntu Bionic)
Assignee: Tyler Alexander Driggers (exderia) => (unassigned)
--
You received this bug notification because you are a member of
Public bug reported:
As of a few weeks ago or so, GNOME Shell loses the text scaling factor
(it's set back to 1) when logging out and logging back in again. It is
preserved for other programs, just not the shell (top bar, menus, dash).
Setting it to another value and then back to the desired
As for me this advertised feature of 20.04 was the main factor to
install this OS on my hardware, because previous 3 years the lack of
this feature prevented me from using Ubuntu.
Sadly, this bug affects me too - I am using Nvidia RTX 2070 Super
together with Asrock X570 Taichi and Ryzen 3600.
I have the same issue, and recommend those who haven't tried it out yet,
to look at post #10 (
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792085/comments/10
) and use this application in the meantime. It works reliably for me.
--
You received this bug notification because you are a
Public bug reported:
Added some gnome extensions, but this was always present. Maybe the
multi monitor setup is at fault?
Attached output is from running 'sudo strace -p' on gnome-shell. The
whole FUTEX part in the middle is only observable during one of these
"stutters". The parts before and
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 29 14:34:01 2020
Dependencies:
accountsservice 0.6.55-0ubuntu10
acl 2.2.53-5ubuntu1
adduser 3.118ubuntu1
adwaita-icon-theme 3.34.0-1ubuntu1
apg 2.2.3.dfsg.1-5
apport
alexstrand7@alexstrand7-vmware:~$ lsb_release -a && uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
Codename: focal
Linux alexstrand7-vmware 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC
Public bug reported:
see screenshot
** Affects: gnome-calendar (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
** Attachment added: "Ubuntu 20.04-2020-02-29-14-23-28.png"
@daniel, please reopen, I still have no permission to do that
--
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/1652618
Title:
Impossible to unlock the screen when using
This bug is reproducible on 19.10
--
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/1652618
Title:
Impossible to unlock the screen when using non-English language
To manage
> A secondary problem, which might be an unfixable design choice, is
that it sounds like PulseAudio clients can block the sound of the entire
server.
If that's unfixable, then perhaps it makes sense to remove this behavior
from clients which are bundled with Ubuntu, such as Nautilus. They don't
Does the same thing happen if you try to shift+delete something in Nautilus?
(this also causes a dialog window to pop up)
I have a very similar issue if I play music in foobar2000 through Wine using
its "wasapi shared" output method and do that - the sound stutters for a brief
amount of time.
…and could this issue be related to this one?
https://bugzilla.redhat.com/show_bug.cgi?id=1668808
--
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/1795021
Title:
I'm having the same problem on Ubuntu 18.04.3 LTS.
gsd-xsettings is the reason my system is even fully filling the SWAP. Is there
any possibility to debug this?
** Bug watch added: Red Hat Bugzilla #1668808
https://bugzilla.redhat.com/show_bug.cgi?id=1668808
--
You received this bug
That might be but that doesn't explain why the system goes to the
"desktop" straight after pressing the power-button w/o identification.
I disabled "energy mode if laptop-lid is closed" in "Tweak" (for gnome),
no improvement.
If I let open the lid for 2...3 cm it workes, but then the
Public bug reported:
I have the above described problem, which seems to be very similar to
bug #1716160
- laptop is in docking station and 2 monitors are connected (HDMI, DVI)
- If the lid is closed and I boot the laptop I can input my credentials
in the login screen and after hitting ENTER the
I am very sorry coz after studying many webpages I end up here since
this pages covers my problem most. If it was wrong posting my problem
here just give me a hint and delete my post.
I have the above described problem:
- laptop is in docking station and 2 monitors are connected (HDMI, DVI)
-
Please reopen the bug and change status to Confirmed
--
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/1652618
Title:
Impossible to unlock the screen when using non-English
I still can reproduce it on latest version of Ubuntu - 19.04
--
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/1652618
Title:
Impossible to unlock the screen when using
The same problem
Dell Vostro 5648, i5-7200U
Even more, after pressing any time CTR-ALT-F#
Gnome desktop process terminates and i've got
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO
underrun
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
Public bug reported:
I've got an exFAT-USB-Stick. If I'm plugging the stick it seems to be
mounted (the mounted symbol appears in nautlius). But I'm not able to
open the stick to open files or for writing new files to the stick. Just
if I'm formatting the stick with GNOME Disks and mounting it
Yes, I think it should be backported.
I also noticed that keyboard layout indicator is cleared not only after
suspension but more often.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Please reopen the bug
--
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/1652618
Title:
Impossible to unlock the screen when using non-English language
To manage notifications
This is not 16.10 bug, it's reproducible on all latest Ubuntu versions
including 18.10
--
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/1652618
Title:
Impossible to unlock the
ser)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go t
t;XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug g
(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this
user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go t
RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://
nf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>
--
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine
** Attachment added: "prev_boot.txt"
https://bugs.launc
Affected on Mint 19.1 running i3lock
locks and unlocks fine, but systemd reports:
"pam_ecryptfs: seteuid error"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1085706
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
> mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.l
TERM=xterm-256color
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>> LANG=en_US.UTF-8
>>SHELL=/bin/bash
>> SourcePackage: gdm3
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> mtime.conffile..etc.gdm3.custom.conf: 2019-
Public bug reported:
After a fresh install of Ubuntu 18.04.1, on its first boot, the computer
hung at a purple screen. No login prompt was ever displayed. After
holding the power button, the computer boot into Ubuntu without
difficulty. I applied the workaround described in bug 1727356,
I second comment #48. Ubuntu 16.04 (well, Mint 18.3 Sylvia actually, but
it uses Xenial repositories).
```
$ hexdump -C -n 16 .ts
47 ff ff 50 52 49 56 54 3a 04 00 00 39 04 00 00 |G..PRIVT:...9...|
$ mimetype --all .ts
.ts: text/vnd.trolltech.linguist
.ts:
Public bug reported:
Hi,
On Lenovo Thinkpad X1 Yoga 3rd Gen and many other laptops there is a
Validity fingerprint sensor with id [06cb:009a]. It is not in the
supported drivers list, but I would love to see it amongst the supported
ones.
Here is a list with some of the models using this
Sorry! Has been my fault. The screen rotation lock has been active.
Sorry for disturbing!
--
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/1808752
Title:
Regression: Screen
I'm using Nextcloud as a calandar provider. Syncing is working if I've
got an internet connection. But there is no caching which means that the
calendar entries have to bee reloaded after each restart.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
1 - 100 of 1987 matches
Mail list logo
