Thank you Jeremy, I filed
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060659
Title:
X11 fractional scaling support is missing in 46.0
Public bug reported:
X11
GNOME
NVIDIA 4080 with their driver
->
GNOME settings has a "ghost" display called "Unknown Display", its
resolution is 1024 x 768
I only have one display attached - a 4K 27" DELL plugged into the NVIDIA
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg
FWIW - I'm also using GNOME 46 in another distro - Manjaro - and this
issue does not exist there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063222
Title:
Ghost "unknown display" since upgrading
Fractional scaling is available again after today's updates
However the ghost "Unknown Display" is still there
** Attachment added: "Screenshot from 2024-04-23 08-25-39.png"
Public bug reported:
Two issues with GNOME Display Settings since upgrading to Ubuntu 24.04
beta
1 - I am unable to select Fractional Scaling and set it to 150%.
The Fractional Scaling checkbox appears to do nothing - 1) selecting it
does not enable the Apply button 2) does not update the list
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975394/+attachment/5591878/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975394
Title:
** Attachment added: "worked_wifi_dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975394/+attachment/5591877/+files/worked_wifi_dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "failed_wifi_dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975394/+attachment/5591876/+files/failed_wifi_dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello,
Sometimes, about every 10 boot, the iwlwifi driver fails to initialize
the hardware and WiFi connectivity is not available.
dmesg from failed boot:
[4.316757] iwlwifi :00:14.3: enabling device ( -> 0002)
...
[4.400950] iwlwifi :00:14.3: CSR_RESET
*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243
Same thing here after upgrading from 21.10 to 24.04 yesterday.
My GPU is an AMD and 21.10 defaulted to Wayland.
With 22.04 - the session is X11 and there is no "gears" icon to select
Wayland.
--
You
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559895/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559894/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559891/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559892/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559893/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559890/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559889/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559888/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559887/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559886/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559883/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
USB
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559882/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559885/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559884/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559881/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
USB
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559880/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected impish
** Description changed:
I use two monitors with USB hub feature. My keyboard and mouse are
plugged into one of those monitors.
After Ubuntu boots, the keyboard and the mouse are dead. I have to
unplug the monitor's USB cable
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1959514/+attachment/5559879/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
USB
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959514/+attachment/5558276/+files/lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959514
Title:
Public bug reported:
I use two monitors with USB hub feature. My keyboard and mouse are
plugged into one of those monitors.
After Ubuntu boots, the keyboard and the mouse are dead. I have to
unplug the monitor's USB cable from the computer and plug it back in,
then the keyboard and the mouse are
The bug is between amdgpu and mesa:
https://gitlab.freedesktop.org/drm/amd/-/issues/1808
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1808
https://gitlab.freedesktop.org/drm/amd/-/issues/1808
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Still happens after yesterday's update of linux-firmware to 1.201.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948563
Title:
amdgpu errors, desktop freezes
To manage notifications about this
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948563/+attachment/5535498/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948563
Title:
Public bug reported:
With Ubuntu 21.10, I consistently get freezes in GNOME desktop (X11)
5-10 minutes after logging in.
I can still Ctrl+Alt+Fx to the console and reboot, but the graphical
desktop is completely frozen.
The system log contains amdgpu errors like this:
[ 1030.245628]
After the above error happened, I'm getting these on subsequent attempts
to do apt-get update / dist-upgrade:
Reading package lists... Done
W: https://repo.skype.com/deb/dists/stable/InRelease: No system certificates
available. Try installing
Removed core dump from the crash report, for security / privacy reasons.
Feel free to request by email.
** Attachment added: 01_opt_google_chrome_chrome.1000.crash.nocore
Public bug reported:
Since installing the Ubuntu 14.10 beta update, I see Google Chrome crash
on startup.
This happens about 1/3 of the time.
The issue doesn't exist with same Chrome version, on same hardware, in
Fedora 20 -- and did not exist prior to updating to Ubuntu 14.10 beta
(i.e.
Oh wunder, wunder!
Fixed by an update/dist-upgrade just now, which pulled down:
libqscintilla2-9 libqscintilla2-l10n python-qscintilla2
Thank you, Ubuntu developers!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to python-qt4 in Ubuntu.
A possible packaging issue (or two) on an amd64 system.
1 - Per the suggestion in the Bitbucket tracker, I tried to install i386
versions of libraries required by TortoiseHG:
https://bitbucket.org/tortoisehg/thg/issue/3349
$sudo apt-get install python-qscintilla2:i386 libqscintilla2-9:i386
FWIW -- I've been running TortoiseHG and Mercurial from these PPAs, they
need to be installed together (thg requires a certain range of hg
verisons)...
https://launchpad.net/~tortoisehg-ppa/+archive/stable-snapshots
https://launchpad.net/~mercurial-ppa/+archive/stable-snapshots
There are no
Possibly related to this:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1162855
First Thunar crashed, immediately afterwards I was logged out of XFCE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Think I see what's going on: the version of gtk-greeter included in
Ubuntu 13.04 uses the user profile's desktop background if there is one.
At least one thing is still wrong -- my desktop background is a small
image (from subtlepatterns.com) set to tile. The greeter does not tile.
Two small
Public bug reported:
Was trying to use lightdm-webkit-greeter on Ubuntu 13.04, installed from
apt-get
/etc/lightdm/lightdm.conf:
[SeatDefaults]
user-session=ubuntu
greeter-session=lightdm-webkit-greeter
/etc/lightdm/lightdm-webkit-greeter.conf:
[greeter]
Public bug reported:
I am running ubuntu with XFCE, and here is the content of my /etc/xdg
/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf
#
# background = Background file to use, either an image path or a color (e.g.
#772953)
# theme-name = GTK+ theme to use
# icon-theme-name = Icon theme to use
Same here. Ubuntu 12.10 upgraded to 13.04 beta.
Also tried more recent mercurial / thg from https://launchpad.net
/~tortoisehg-ppa, didn't make any difference.
Curiously enough, commands that don't launch a GUI -- thg version,
thg help -- work fine. Trying to launch the GUI fails.
Attaching the
Diagnosed the issue:
Caused by a dependency check for Qt 4.6 and PyQt 4.7 in
tortoisehg/hgqt/qtlib.py.
if PYQT_VERSION_STR.split('.') ['4', '7'] or \
QT_VERSION_STR.split('.') ['4', '6']:
sys.stderr.write('TortoiseHg requires Qt 4.6 and PyQt 4.7\n')
sys.stderr.write('You have Qt %s
46 matches
Mail list logo
