** Changed in: pango1.0 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1869716
Title:
Removing libpango1.0-0 broke Minecraft Launcher
Public bug reported:
[Summary]
Attach a monitor and output from Nvidia dGPU.
The Dell logo(BGRT image) pops up for a while before hand over to x session.
[Steps to reproduce]
* Prerequisite: Disable the auto-login
1. Power on the system
2. Enter the password
3. Check if the Dell logo pops
4. Susp
*** This bug is a duplicate of bug 1858316 ***
https://bugs.launchpad.net/bugs/1858316
** This bug is no longer a duplicate of private bug 1868700
** This bug has been marked a duplicate of private bug 1858316
--
You received this bug notification because you are a member of Ubuntu
Desktop B
*** This bug is a duplicate of bug 1715222 ***
https://bugs.launchpad.net/bugs/1715222
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
tracker. This problem was most recently seen with package version 2.3.0-1, the
problem page at
https://
*** This bug is a duplicate of bug 1715222 ***
https://bugs.launchpad.net/bugs/1715222
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
tracker-miners. This problem was most recently seen with package version
2.0.4-2, the problem page at
h
*** This bug is a duplicate of bug 1715222 ***
https://bugs.launchpad.net/bugs/1715222
** This bug has been marked a duplicate of bug 1724061
tracker-extract crashed with signal 31 in g_assertion_message()
** This bug is no longer a duplicate of bug 1724061
tracker-extract crashed with
Sounds like plymouthd is kicking in?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1916850
Title:
Dell logo pops up for a while before gdm hand over to X session
To manage notificat
No crashes after 19.10.
** Summary changed:
- tracker-extract crashed with SIGABRT in g_assertion_message()
+ tracker-extract crashed with SIGABRT in g_assertion_message() in
gst_audio_decoder_push_buffers: "assertion failed: (offset + len <= av)"
** Tags removed: artful
** Tags added: bionic
Hello Daniel,
I remembered the small running circle before the login page is plymouth,
but BRGT is plotted by fbcon driver, but I didn't remember it very
clearly.
My question is if gdm can help to blank FB before hand over to x
session?
Currently, I only see the issue on NV card but not i915 and
** Changed in: libhandy-1 (Debian)
Status: Unknown => Fix Released
--
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/1913934
Title:
Wrong current option in Screen
https://launchpad.net/ubuntu/+source/libhandy-1/1.0.3-2
** Changed in: libhandy-1 (Ubuntu)
Status: Fix Committed => Fix Released
--
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.launc
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
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/188
Someone wrote, not to me: "Then log out and in again to verify the bug
still occurs without extensions.".
However my ubuntu 20.10 is in default release state, I added *no*
extension to it (I disbled a few kbd shortcuts, added two kbd shortcuts,
so it is basically in release state).
And I have the
Public bug reported:
each maximisation + un-maximisation cycle of a gnome-termial windows
will shrink the terminal by 1 row and by 1 column
two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks
from 80x42 to 78x40:
prohlep@pc56:~$ resize
COLUMNS=80;
LINES=42;
export COLUMNS LINE
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gdm (Ubuntu Focal)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gdm (Ubuntu)
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu-seeds/+git/ubuntu-seeds/+merge/398722
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcar
Hi there. I'm quite new to launchpad and don't know if my behavior is the right
way now. I experience this same problem on actually five Lenovo P15s with
Ubuntu 20.04 running on kernel 5.8.0-44-generic. My problem is, that I can't
hand out those systems to our developers in their remote-offices
Workaround
Use the Terminal and set this options:
gsettings set org.gnome.desktop.wm.preferences auto-raise 'true'
gsettings set org.gnome.desktop.wm.preferences focus-new-windows 'strict'
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*** This bug is a duplicate of bug 1841826 ***
https://bugs.launchpad.net/bugs/1841826
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
This bug was fixed in the package gnome-settings-daemon -
3.38.1-3ubuntu3
---
gnome-settings-daemon (3.38.1-3ubuntu3) hirsute; urgency=medium
* debian/patches: Support smartcard reders via p11kit API (LP: #1865226)
* debian/control: Build depend on libgck-1-dev and remove nss depe
** Changed in: gdm3 (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1691357
Title:
User switch not possible, login screen black
To ma
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
** Summary changed:
- xvfb fails when building mutter in hirsute-proposed
+ mutter fails to run using wayland with glib2.0 2.67.4-1
** Description changed:
When hirsute-proposed is enabled (works fine in hirsute), mutter fails
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2332
https://gitlab.gnome.org/GNOME/glib/-/issues/2332
** Also affects: xorg-server via
https://gitlab.gnome.org/GNOME/glib/-/issues/2332
Importance: Unknown
Status: Unknown
** Changed in: glib2.0 (Ubuntu)
Status: Ne
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: glib2.0 (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
*** This bug is a duplicate of bug 1916701 ***
https://bugs.launchpad.net/bugs/1916701
** This bug has been marked a duplicate of bug 1916701
[glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
eventually comes up without Wayland support (only Xorg sessions offered)
--
Thanks, those stack traces are exactly what we needed. I can't find any
other reports of those crashes, but that's likely just because nobody
else had debugged it with GDK_SYNCHRONIZE yet...
Next please report the bug to the developers at
https://gitlab.gnome.org/GNOME/gtk/-/issues and remember to
*** This bug is a duplicate of bug 1288655 ***
https://bugs.launchpad.net/bugs/1288655
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 1288655, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1288655 ***
https://bugs.launchpad.net/bugs/1288655
** This bug has been marked a duplicate of bug 1288655
Terminal height shrinks - repeatedly restored shorter than the previous
height
--
You received this bug notification because you are a member of U
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #140
https://gitlab.gnome.org/GNOME/mutter/-/issues/140
** Changed in: mutter
Importance: Undecided => Unknown
** Changed in: mutter
Status: New => Unknown
** Changed in: mutter
Remote watch: None => gitlab.gnome.org/GNOME/
The first thing to check is whether it's plymouth displaying the logo.
It is meant to do so at certain times, but usually fails on Nvidia due
to bug 1868240. Try booting with the 'nosplash' kernel parameter as that
should remove plymouth from the equation.
** Also affects: plymouth (Ubuntu)
Im
Hi Daniel,
The problem happens again today.
I follow the instructions in comments #1 and #3, yet the issue not solved.
I'm attaching the files and screenshots if this helps you to figure out the
problem.
Note: the screenshot and rfkill.txt and iwconfig files taken while I'm
facing the issue.
Sol
** Summary changed:
- Wifi adapter installed but can't be found in Settings
+ Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260
[8086:24f3]) installed but can't be found in Settings
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => New
** Also affects: ne
Thanks. The iwconfig output seems to show the wifi adapter is missing at
the kernel level. When it was working your kernel log shows the adapter
was called 'wlp1s0'... Next time the problem happens, please run this
while it is happening:
dmesg > dmesg.txt
and attach the resulting text file here
FYI other bugs with the same wifi chip: bug 1838836, bug 1880426
** No longer affects: gnome-control-center (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Please tell us which version of Ubuntu is still affected by this bug.
Please also run this command:
lspci -kv > lspci.txt
and attach the resulting text file here.
** Tags removed: bionic
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
** Bug watch added: gitlab.gno
If it's still happening then I'm thinking https://gitlab.gnome.org/GNOME
/gnome-settings-daemon/-/issues/595 might be related, which some have
suggested is specific to AMD.
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #595
https://gitlab.gnome.org/GNOME/gnome-sett
The lock screen runs as a different user so it will use the system
default settings rather than your own. You should be able to configure
your preferences to make them system wide, in
Settings >
Language & Region >
Manage Installed Languages >
Regional Formats >
Apply System-Wide.
As for:
b'or
Public bug reported:
```
GNU Image Manipulation Program version 2.10.22
git-describe: GIMP_2_10_20-217-g0c8a7891f7
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFF
> The lock screen runs as a different user so it will use the system
default settings rather than your own.
Actually I can't remember if that's strictly true for 18.04. But rather
than test 18.04 I've just checked on 20.04 and can confirm that:
gsettings set 'org.gnome.desktop.interface' 'clock
40 matches
Mail list logo
