[Desktop-packages] [Bug 1961857] Re: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r30
It appears this crash has only been reported twice, ever. It's also in an unsupported package (compiz). If you are using a desktop then I would recommend replacing the graphics card so as to get a different driver. Otherwise please use GNOME (regular Ubuntu). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1961857 Title: compiz crashed with SIGSEGV in nir_lower_uniforms_to_ubo() from draw_create_vs_llvm() from draw_create_vertex_shader() from r300_draw_init_vertex_shader() from r300_create_vs_state() Status in compiz package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding compiz. This problem was most recently seen with package version 1:0.9.14.1+20.04.20200211-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/253612f74aa79d2e52b8f27505f04cb72de285c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1961857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
+ https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
[Desktop-packages] [Bug 1964080] Re: /usr/lib/xorg/Xorg:6:OsAbort:AbortServer:FatalError:dix_main:__libc_start_call_main
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
The details in
https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007
currently show this is bug 1543192. Although that may change in future
if errors.ubuntu.com changes which crash report and error message it
displays.
** This bug has been marked a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1964080
Title:
/usr/lib/xorg/Xorg:6:OsAbort:AbortServer:FatalError:dix_main:__libc_start_call_main
Status in xorg-server package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:21.1.3-2ubuntu2, the problem page at
https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1964080/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964080] [NEW] /usr/lib/xorg/Xorg:6:OsAbort:AbortServer:FatalError:dix_main:__libc_start_call_main
*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.3-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: focal hirsute impish jammy kylin-21.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1964080 Title: /usr/lib/xorg/Xorg:6:OsAbort:AbortServer:FatalError:dix_main:__libc_start_call_main Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.3-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1964080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
Hi: Please see the attachment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Attachment added: "ldd -r" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5566868/+files/Screenshot%20from%202022-03-08%2011-02-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948612] Re: gnome-shell crashed with SIGSEGV in std::__uniq_ptr_impl::_M_ptr from std::unique_ptr::get from std::unique_ptr::operator bool from GjsMaybeOwned::get
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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948612 Title: gnome-shell crashed with SIGSEGV in std::__uniq_ptr_impl::_M_ptr from std::unique_ptr::get from std::unique_ptr::operator bool from GjsMaybeOwned::get Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8881ba9950cb2700ff108d1d2f7a557229355321 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963770] Re: gnome-shell crashed with SIGSEGV
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
your system at the time of the report. Please upgrade your system to the
latest package versions. If you still encounter the crash, please file a
new report.
Thank you for your understanding, and sorry for the inconvenience!
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1963770
Title:
gnome-shell crashed with SIGSEGV
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
Twice seen after starting the Firefox snap in a live session.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 5 22:30:08 2022
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220305)
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f1cb6d891b4:mov(%rsi),%rax
PC (0x7f1cb6d891b4) ok
source "(%rsi)" (0x1c402550) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
#0 0x7f1cb6d891b4 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffc18248c90
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963770/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933890] Re: No wacom tablet or stylus discovered, Fujitsu T935
** Package changed: gnome-control-center (Ubuntu) => libwacom (Ubuntu) ** Changed in: libwacom (Ubuntu) Assignee: (unassigned) => Rob Frohne (frohro) ** Changed in: libwacom (Ubuntu) Status: New => In Progress ** Changed in: libwacom (Ubuntu) Importance: Undecided => Medium ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 Status in libwacom package in Ubuntu: In Progress Bug description: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touch id: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylusid: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraserid: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1933890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766775] Re: "Automatic suspend" notifications do not disappear
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766775 Title: "Automatic suspend" notifications do not disappear Status in GNOME Settings Daemon: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963818] Re: Upgrading to 22.04 on wayland session closes session
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 us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: wayland (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1963818 Title: Upgrading to 22.04 on wayland session closes session Status in Ubuntu: Incomplete Bug description: Just tried to upgrade Kubuntu from 21.10 to 22.04 in a konsole on a Wayland session (using do-release-upgrade) and while setting up one of the packages I lost the Wayland session and was left with a tiny cursor in the upper left corner. No way to restart a new session or connect a tty to inspect the running upgrade process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1963818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
This affects me in the sense that Xpresent support in Marco was temporarily disabled in 22.04 until this is fixed, which ultimately results in screen tearing with Intel Iris Xe integrated graphics. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
The gnome-control-center 1:41.4-1ubuntu3.1 indeed fix the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962761] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962761/+attachment/5566717/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: Confirmed Bug description: It's part of a chain of bugs that come one after another as I try to report each one of them. Never saw this behavior before ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:32:37 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-01-03 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=ro_RO.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5f445b49a8 : cmp %rax,(%rbx) PC (0x7f5f445b49a8) ok source "%rax" ok destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962761] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1962761/+attachment/5566718/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: Confirmed Bug description: It's part of a chain of bugs that come one after another as I try to report each one of them. Never saw this behavior before ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:32:37 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-01-03 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=ro_RO.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5f445b49a8 : cmp %rax,(%rbx) PC (0x7f5f445b49a8) ok source "%rax" ok destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962761] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962761/+attachment/5566719/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962761/+attachment/5565047/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: Confirmed Bug description: It's part of a chain of bugs that come one after another as I try to report each one of them. Never saw this behavior before ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:32:37 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-01-03 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=ro_RO.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5f445b49a8 : cmp %rax,(%rbx) PC (0x7f5f445b49a8) ok source "%rax" ok destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962761] nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
StacktraceTop: gtk_widget_get_ancestor (widget=0x55d68dfbd340, widget_type=94379979195536) at ../../../../gtk/gtkwidget.c:11653 button_data_file_changed (file=0x55d68d4c4c20, button_data=0x55d68d7d05a0) at ../src/nautilus-pathbar.c:952 g_closure_invoke (closure=0x55d68d1dbc90, return_value=0x0, n_param_values=1, param_values=0x7ffc0e3c04c0, invocation_hint=0x7ffc0e3c0440) at ../../../gobject/gclosure.c:830 signal_emit_unlocked_R (node=node@entry=0x55d68d36b400, detail=detail@entry=0, instance=instance@entry=0x55d68d4c4c20, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc0e3c04c0) at ../../../gobject/gsignal.c:3744 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7ffc0e3c0670) at ../../../gobject/gsignal.c:3497 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: Confirmed Bug description: It's part of a chain of bugs that come one after another as I try to report each one of them. Never saw this behavior before ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:32:37 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-01-03 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=ro_RO.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5f445b49a8 : cmp %rax,(%rbx) PC (0x7f5f445b49a8) ok source "%rax" ok destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
The problem is that laptop go to suspend during boot because lid is closed. The behavior is actually highly depends on the hardware you use. It works for me with Lenovo Thinkpad P52 + Lenovo Thinkpad Thunderbolt 3 Gen2 dock station. Here is my full logind.conf: #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=lock HandleLidSwitchExternalPower=lock HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 Here is the ways i found to deal with that: 1) Play with logind.conf params (https://www.freedesktop.org/software/systemd/man/logind.conf.html - manual for configuration) 2) Use gnome-tweaks to disable suspend on lid closed (it actually creates ~/.config/autostart/ignore-lid-switch-tweak.desktop to achieve this) - does nothing for me 3) There is an option (which i use in combination with logind.conf) in Lenovo BIOS to use external docked monitor as main screen during boot - check if there is similar option in your BIOS. Please, let us know if you will find a solution for your hardware -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 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 laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962642] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1962642/+attachment/5566671/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: Incomplete Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962642] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962642/+attachment/5566670/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: Incomplete Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962642] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962642/+attachment/5566672/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962642/+attachment/5564752/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: Incomplete Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962642] geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected
StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: Incomplete Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
The new dependency on libopengl0 is expected. The new version of WebKitGTK fixed opengl detection and the new dependency is now required. I am going to re-assign this bug to unattended-upgrades. If it's not willing to install new dependencies, it definitely should get fixed as some security updates will always get held back. ** Package changed: webkit2gtk (Ubuntu) => unattended-upgrades (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1963751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Shadrin, I tried that... removed the # from the start of that line so it was set to ignore. It had no effect. I notice that there is another parameter LidSwitchIgnoreInhibited. That is set to yes. What is the function of that parameter, do you know? Thanks... AND I CONCUR: Please correct this bug... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 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 laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963861] Re: Can't tell what application will be launched with custom schemes
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1963861 Title: Can't tell what application will be launched with custom schemes Status in snapd: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: If a url is opened such as: mailto: feed: The firefox snap package no longer shows what application will be launched. This means that websites can potentially trick a user to start applications. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1963861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
OK, have manually rolled back the system to previous state (the old
versions of the packages were still available on my apt-cacher-ng
server), and run unattended-upgrades in debug mode - file attached. I
guess the key lines are:
sanity check failed for:
{'libjavascriptcoregtk-4.0-18=2.34.6-0ubuntu0.20.04.1',
'libopengl0=1.3.2-1~ubuntu0.20.04.1',
'libwebkit2gtk-4.0-37=2.34.6-0ubuntu0.20.04.1'} : pkg libopengl0 is not in an
allowed origin
falling back to adjusting libjavascriptcoregtk-4.0-18's dependencies
sanity check failed for: {'nautilus-share=0.7.3-2ubuntu3',
'libjavascriptcoregtk-4.0-18=2.34.6-0ubuntu0.20.04.1',
'gnome-session-flashback=1:3.36.5-0ubuntu1', 'atril=1.24.0-1',
'gnome-todo=3.28.1-5', 'gnucash=1:3.8b-1ubuntu1',
'gnome-calendar=3.36.2-0ubuntu1', 'xubuntu-desktop=2.233',
'ubuntu-unity-desktop=0.2', 'evolution-data-server=3.36.4-0ubuntu1',
'metacity=1:3.36.1-1', 'update-manager=1:20.04.10.7',
'indicator-bluetooth=0.0.6+17.10.20170605-0ubuntu3', 'libfolks-eds25=0.13.2-1',
'gdm3=3.36.3-0ubuntu0.20.04.3', 'update-notifier=3.192.30.7',
'mutter=3.36.9-0ubuntu0.20.04.1',
'gnome-user-docs=3.36.2+git20200704-0ubuntu0.1', 'yelp=3.36.0-1',
'rhythmbox-plugins=3.4.4-1ubuntu2', 'libedataserverui-1.2-2=3.36.4-0ubuntu1',
'libgoa-backend-1.0-1=3.36.0-1ubuntu1', 'ubuntu-session=3.36.0-2ubuntu1',
'ubuntu-docs=20.04.3', 'gir1.2-webkit2-4.0=2.34.6-0ubuntu0.20.04.1',
'libatrilview3=1.24.0-1',
'unity-control-center=15.04.0+19.10.20190921-0ubuntu3',
'gnome-control-center=1:3.36.5-0ubuntu1', 'zenity=3.32.0-5',
'gnome-online-accounts=3.36.0-1ubuntu1',
'ubuntu-release-upgrader-gtk=1:20.04.33',
'gnome-shell=3.36.7-0ubuntu0.20.04.1', 'apturl=0.5.2ubuntu19',
'shotwell=0.30.10-0ubuntu0.1', 'geary=3.36.1-1', 'libyelp0=3.36.0-1',
'libwebkit2gtk-4.0-37=2.34.6-0ubuntu0.20.04.1'} : pkg libgoa-backend-1.0-1 is
marked to be deleted
I'm unclear on exactly how u-a is supposed to work, it's possible this
is an algorithmic bug there I suppose?
** Attachment added: "ua.log"
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+attachment/559/+files/ua.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1963751
Title:
focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically
installed due to new dependency
Status in webkit2gtk package in Ubuntu:
Incomplete
Bug description:
Version: 2.34.6-0ubuntu0.20.04.1
This security update for focal does not seem to be automatically
upgradeable by unattended-upgrades:
2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but
fails to be marked for upgrade (E:Unable to correct problems, you have held
broken packages.)
2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but
fails to be marked for upgrade (E:Unable to correct problems, you have held
broken packages.)
2022-03-05 14:32:38,031 INFO No packages found that can be upgraded
unattended and no pending auto-removals
2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back
because a related package is kept back or due to local apt_preferences(5).
2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back
because a related package is kept back or due to local apt_preferences(5).
apt-mark showhold lists no held packages, and there are no
apt_preferences set. The actual cause seems to be an extra dependency
on libopengl0 which has been added with the upgrade. Is this
intentional?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
Uname: Linux 5.4.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Mar 5 14:39:24 2022
InstallationDate: Installed on 2018-06-15 (1358 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=screen.xterm-256color
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: webkit2gtk
UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
OK, here is dpkg.log section from one machine: 2022-03-05 14:45:14 startup archives unpack 2022-03-05 14:45:14 install libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:14 status triggers-pending libc-bin:amd64 2.31-0ubuntu9.2 2022-03-05 14:45:14 status half-installed libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:14 status unpacked libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:14 upgrade libwebkit2gtk-4.0-37:amd64 2.34.4-0ubuntu0.20.04.1 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:14 status half-configured libwebkit2gtk-4.0-37:amd64 2.34.4-0ubuntu0.20.04.1 2022-03-05 14:45:14 status unpacked libwebkit2gtk-4.0-37:amd64 2.34.4-0ubuntu0.20.04.1 2022-03-05 14:45:14 status half-installed libwebkit2gtk-4.0-37:amd64 2.34.4-0ubuntu0.20.04.1 2022-03-05 14:45:17 status unpacked libwebkit2gtk-4.0-37:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:18 upgrade libjavascriptcoregtk-4.0-18:amd64 2.34.4-0ubuntu0.20.04.1 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:18 status half-configured libjavascriptcoregtk-4.0-18:amd64 2.34.4-0ubuntu0.20.04.1 2022-03-05 14:45:18 status unpacked libjavascriptcoregtk-4.0-18:amd64 2.34.4-0ubuntu0.20.04.1 2022-03-05 14:45:18 status half-installed libjavascriptcoregtk-4.0-18:amd64 2.34.4-0ubuntu0.20.04.1 2022-03-05 14:45:19 status unpacked libjavascriptcoregtk-4.0-18:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 startup packages configure 2022-03-05 14:45:19 configure libjavascriptcoregtk-4.0-18:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 status unpacked libjavascriptcoregtk-4.0-18:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 status half-configured libjavascriptcoregtk-4.0-18:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 status installed libjavascriptcoregtk-4.0-18:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 configure libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:19 status unpacked libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:19 status half-configured libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:19 status installed libopengl0:amd64 1.3.2-1~ubuntu0.20.04.1 2022-03-05 14:45:19 configure libwebkit2gtk-4.0-37:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 status unpacked libwebkit2gtk-4.0-37:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 status half-configured libwebkit2gtk-4.0-37:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 status installed libwebkit2gtk-4.0-37:amd64 2.34.6-0ubuntu0.20.04.1 2022-03-05 14:45:19 trigproc libc-bin:amd64 2.31-0ubuntu9.2 2022-03-05 14:45:19 status half-configured libc-bin:amd64 2.31-0ubuntu9.2 2022-03-05 14:45:19 status installed libc-bin:amd64 2.31-0ubuntu9.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in webkit2gtk package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
Unfortunately I've already done that on the two affected machines and didn't make a note of the output. I will try to dig out the dpkg logs. As I said, the extra dependency on libopengl0 seemed to be the issue. It's also just possible I took a snapshot or backup so I can roll back and retry - I will have a look. I seem to recall one machine had had non-security updates disabled after they had previously been enabled, and I initially suspected that had caused the problem, but then it occurred on another machine where that wasn't true. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in webkit2gtk package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.5.1
---
ubuntu-drivers-common (1:0.9.5.1) jammy; urgency=medium
* Change maximum open file descriptors limit for the process in
the test suite. This should fix the FTBFS.
-- Alberto Milone Mon, 07 Mar 2022
17:16:26 +0100
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the
[Desktop-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
Hello Steve, thanks for the report; can you run a manual: sudo apt update && sudo apt upgrade and report back the apt output, which will give a better idea of what exactly is holding back the upgrade? Thanks ** Changed in: webkit2gtk (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in webkit2gtk package in Ubuntu: Incomplete Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963751] Re: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963751 Title: focal security update 2.34.6-0ubuntu0.20.04.1 cannot be automatically installed due to new dependency Status in webkit2gtk package in Ubuntu: New Bug description: Version: 2.34.6-0ubuntu0.20.04.1 This security update for focal does not seem to be automatically upgradeable by unattended-upgrades: 2022-03-05 14:32:35,653 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:36,685 WARNING package libwebkit2gtk-4.0-37 upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) 2022-03-05 14:32:38,031 INFO No packages found that can be upgraded unattended and no pending auto-removals 2022-03-05 14:32:38,232 INFO Package libjavascriptcoregtk-4.0-18 is kept back because a related package is kept back or due to local apt_preferences(5). 2022-03-05 14:32:38,382 INFO Package libwebkit2gtk-4.0-37 is kept back because a related package is kept back or due to local apt_preferences(5). apt-mark showhold lists no held packages, and there are no apt_preferences set. The actual cause seems to be an extra dependency on libopengl0 which has been added with the upgrade. Is this intentional? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwebkit2gtk-4.0-37 2.34.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Mar 5 14:39:24 2022 InstallationDate: Installed on 2018-06-15 (1358 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: webkit2gtk UpgradeStatus: Upgraded to focal on 2021-05-30 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1963751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964035] Re: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1964035 Title: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-signed-hwe-5.8 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics card (onboard intel+nvidia rtx3050) I didn't like how intel (i915) works (flickering problem has not yet been overcome) so I decided to try using nvidia only. I spent a long time dealing with the "xorg" settings in order to run "x" on nvidia only: * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 i915.modeset=0` * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier "Card0" ) after starting startx on the screen, the image freezes when switching to tty2 and back to tty1, the server does not render anything, and if you open `top` in tty2, you can see: ``` MiB Mem : 31808,1 total, 24998,2 free, 5471,6 used, 1338,3 buff/cache MiB Swap:954,0 total,954,0 free, 0,0 used. 25914,7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2547 root 20 0 2880328 156160 86076 R 100,3 0,5 6:19.96 kwin_x11 3033 hetman20 0 3052116 350728 186196 S 1,0 1,1 0:06.43 firefox 3314 hetman20 0 2477080 140688 93056 S 1,0 0,4 0:01.23 Isolated Web Co 306 root 20 0 0 0 0 I 0,3 0,0 0:00.36 kworker/6:2-events 776 message+ 20 09044 6032 3828 S 0,3 0,0 0:01.62 dbus-daemon 801 root 20 0 16852 7828 6892 S 0,3 0,0 0:00.17 systemd-logind 2967 hetman20 0 5771360 4,4g 124548 S 0,3 14,1 2:04.60 plasmashell 3000 hetman20 0 340504 63760 50732 S 0,3 0,2 0:00.37 kwalletd5 3207 hetman20 0 2427008 110324 89080 S 0,3 0,3 0:00.30 Privileged Cont 3607 root 20 0 0 0 0 I 0,3 0,0 0:00.03 kworker/u24:2-events_power_efficient ``` nvidia-smi ``` hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log Mon Mar 7 23:03:53 2022 +-+ | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 NVIDIA GeForce ... Off | :01:00.0 Off | N/A | | N/A 41CP8N/A / N/A |132MiB / 4096MiB | 0% Default | | | | N/A | +---+--+--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 2847 G /usr/lib/xorg/Xorg 12MiB | |0 N/A N/A 2967 G /usr/bin/plasmashell8MiB | |0 N/A N/A 3033 G /usr/lib/firefox/firefox 85MiB | |0 N/A N/A 4436 G ...bexec/kscreenlocker_greet 12MiB | +-+ ``` Thus, I stated that the X's started up and are working, but the image is not displayed. if return modprobe i915.modeset=1 /usr/share/X11/xorg.conf.d/20-intel.conf /usr/share/X11/xorg.conf.d/10-nvidia.conf - otherwise the output always goes through only intel (i915) nvidia not uses even if use `prime-select nvidia` - this option ignoring - Description:
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176)
** Changed in: df-libreoffice Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34-Clipboard- Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183]
@albertoma/Moshpirit: Please create a new bug as this one here is specifically about the Mutter situation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34-Clipboard- Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
Didier merged a better version of the fix I uploaded so presumably he'll upload that soon and we can see where things fall. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: New Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962566] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962566/+attachment/5566642/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962566] gnome-shell crash after resume from suspend in gdm/util.js:154
StacktraceTop: g_source_get_context (source=source@entry=0xa0c0) at ../../../glib/gmain.c:1481 g_task_return (type=, task=0x55ba93253a70) at ../../../gio/gtask.c:1278 g_task_return (task=0x55ba93253a70, type=) at ../../../gio/gtask.c:1249 g_task_return_error (task=, error=) at ../../../gio/gtask.c:1889 fp_device_task_return_in_idle_cb (user_data=0x55ba9326a220) at /usr/include/glib-2.0/glib/gmem.h:213 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962566] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1962566/+attachment/5566643/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962566] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962566/+attachment/5566644/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962566/+attachment/5564431/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
This bug was fixed in the package gnome-control-center - 1:41.4-1ubuntu3.1 --- gnome-control-center (1:41.4-1ubuntu3.1) jammy; urgency=medium * debian/patches/git_owe_settings.patch: Fix OWE settings (lp: #1963906) -- Sebastien Bacher Mon, 07 Mar 2022 17:05:27 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959508] Re: enable BMFF support in exiv2
I can confirm CR3 support is not enabled in exiv2 0.27.5-1. It very much appears the steps outlined by Robin Mills (aka clanmills) have not been undertaken by the Debian packager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Incomplete Status in exiv2 package in Debian: Fix Released Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906642] Re: Xorg crashes with abort in iris_dri.so
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 i have problem like this but Xorg didn't crash only on some Applications like: * Discover (plasma-discover), * Сістэмныя настаўленні (systemsettings5) some etc. Crash report has iris_dri.so [KCrash Handler] #6 0x7f44730525fe in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f44731fafba in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f4472fe9b08 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #9 0x7f4472feb186 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #10 0x7f447292d1b3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #11 0x7f447292d37a in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #12 0x7f44729319db in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #13 0x7f447293280b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #14 0x7f4472350422 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #15 0x7f44724fda1f in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #16 0x7f4472500959 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #17 0x7f4472506699 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #18 0x7f448af52bac in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f448af53068 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f448af5352a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 ... this problem on newest kernel 5.16.12-051612-generic #202203030915-Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1906642 Title: Xorg crashes with abort in iris_dri.so Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: System is crashing, logging out and i am constantly losing all my work if it's not saved Description: Ubuntu 20.04 LTS (fossa-beric-icl X31) Release: 20.04 N: Unable to locate package pkgname I expect not to happen (crash->log out) Instead, it happened ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 Uname: Linux 5.6.0-1033-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 12:33:11 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a2a] InstallationDate: Installed on 2020-09-19 (74 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 3501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=6b577a12-8585-4836-a5fc-abc3857f42ce ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 01D26F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd07/06/2020:svnDellInc.:pnVostro3501:pvr:rvnDellInc.:rn01D26F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3501 dmi.product.sku: 0A2A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1906642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964021] [NEW] pulseaudio crashes when using Spotify (from Snap)
Public bug reported: pulseaudio crashed twice while listening to Spotify (snap package). It was automatically respawn via systemd ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.15.21-051521-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 7 19:17:36 2022 InstallationDate: Installed on 2012-02-27 (3660 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-01-11 (55 days ago) dmi.bios.date: 01/15/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:br8.15:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-07-11T22:52:45.088258 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1964021 Title: pulseaudio crashes when using Spotify (from Snap) Status in pulseaudio package in Ubuntu: New Bug description: pulseaudio crashed twice while listening to Spotify (snap package). It was automatically respawn via systemd ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.15.21-051521-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 7 19:17:36 2022 InstallationDate: Installed on 2012-02-27 (3660 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-01-11 (55 days ago) dmi.bios.date: 01/15/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:br8.15:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-07-11T22:52:45.088258 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1964021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963723] Re: Crash: 'No module named "dbus"'
So: Mint tells me to consult Ubuntu; Ubuntu tells me to consult Mint. Nice. Luckily I solved the problem myself. See: https://github.com/linuxmint/cinnamon-control-center/issues/277 ** Bug watch added: github.com/linuxmint/cinnamon-control-center/issues #277 https://github.com/linuxmint/cinnamon-control-center/issues/277 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1963723 Title: Crash: 'No module named "dbus"' Status in system-config-printer package in Ubuntu: Invalid Bug description: $ system-config-printer Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus ModuleNotFoundError: No module named 'dbus' I have the problem on Linux Mint 20.3 Cinnamon, which is based upon Ubuntu 20.04; and/but a Mint developer advised me to report the problem here. $ apt list system-config-printer Listing... Done system-config-printer/focal-updates,focal-updates,now 1.5.12-0ubuntu1.1 all [installed] Cf. (among others?) ##1057256, 819053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1963723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Hi Łukasz, I have just attached the sbuild log. I can certainly upload to a PPA, so that, perhaps, testing the changes will be easier. As I wrote in the description, I saw the time for a simple "ubuntu- drivers list" go down from 13,751s to 2,673s, which is quite impressive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Attachment added: "Sbuild log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+attachment/5566587/+files/ubuntu-drivers-common_0.9.6_amd64-2022-03-07T16%3A44%3A03Z.build ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. - This significantly improves performance. + This significantly improves performance (2,673s vs 13,751s , on my dated + Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s - :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s - New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s - :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s - [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy amd64 xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy arm64 xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy armhf xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy ppc64el xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy riscv64 xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-input-mutouch (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-tdfx 1:1.5.0-4 in jammy xserver-xorg-video-tdfx 1:1.5.0-4 in jammy amd64 xserver-xorg-video-tdfx 1:1.5.0-4 in jammy arm64 xserver-xorg-video-tdfx 1:1.5.0-4 in jammy armhf xserver-xorg-video-tdfx 1:1.5.0-4 in jammy ppc64el xserver-xorg-video-tdfx 1:1.5.0-4 in jammy riscv64 xserver-xorg-video-tdfx 1:1.5.0-4 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-tdfx (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-trident 1:1.3.8-2build1 in jammy xserver-xorg-video-trident 1:1.3.8-2build1 in jammy amd64 xserver-xorg-video-trident 1:1.3.8-2build1 in jammy arm64 xserver-xorg-video-trident 1:1.3.8-2build1 in jammy armhf xserver-xorg-video-trident 1:1.3.8-2build1 in jammy ppc64el xserver-xorg-video-trident 1:1.3.8-2build1 in jammy riscv64 xserver-xorg-video-trident 1:1.3.8-2build1 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-trident (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy amd64 xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy arm64 xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy armhf xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy ppc64el xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy riscv64 xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-input-aiptek (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy amd64 xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy arm64 xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy armhf xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy riscv64 Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-siliconmotion (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-input-elographics 1:1.4.2-1 in jammy xserver-xorg-input-elographics 1:1.4.2-1 in jammy amd64 xserver-xorg-input-elographics 1:1.4.2-1 in jammy arm64 xserver-xorg-input-elographics 1:1.4.2-1 in jammy armhf xserver-xorg-input-elographics 1:1.4.2-1 in jammy ppc64el xserver-xorg-input-elographics 1:1.4.2-1 in jammy riscv64 xserver-xorg-input-elographics 1:1.4.2-1 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-input-elographics (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
geode doesn't seem to have been readded, but I've added it to the sync blacklist. ** Changed in: xserver-xorg-video-geode (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-mach64 6.9.6-3 in jammy xserver-xorg-video-mach64 6.9.6-3 in jammy amd64 xserver-xorg-video-mach64 6.9.6-3 in jammy arm64 xserver-xorg-video-mach64 6.9.6-3 in jammy armhf xserver-xorg-video-mach64 6.9.6-3 in jammy ppc64el xserver-xorg-video-mach64 6.9.6-3 in jammy riscv64 xserver-xorg-video-mach64 6.9.6-3 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-mach64 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy amd64 xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy arm64 xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy armhf xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy ppc64el xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy riscv64 xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-neomagic (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-savage 1:2.3.9-4 in jammy xserver-xorg-video-savage 1:2.3.9-4 in jammy amd64 xserver-xorg-video-savage 1:2.3.9-4 in jammy arm64 xserver-xorg-video-savage 1:2.3.9-4 in jammy armhf xserver-xorg-video-savage 1:2.3.9-4 in jammy ppc64el xserver-xorg-video-savage 1:2.3.9-4 in jammy riscv64 xserver-xorg-video-savage 1:2.3.9-4 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-savage (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from jammy: xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy amd64 xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy arm64 xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy armhf xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy ppc64el xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy riscv64 xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy s390x Comment: Reintroduced in Debian but not wanted for Ubuntu; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-sisusb (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: Fix Released Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Eduroam is a WPA2 Enterprise network. It supported different EAP methods (https://wiki.geant.org/pages/viewpage.action?pageId=121346284): - EAP TTLS-PAP - PEAP - EAP TLS - EAP-pwd I always use the default option selected in Ubuntu Wi-Fi Settings, which is labeled "Tunneled TLS". But I double-checked some guides and most recommend PEAP, which I've now also tried and had the same issue with. Guide from my institution: https://it.umn.edu/services-technologies/how-tos/wifi-connect-unix-or-linux-most-major Another guide: https://www.ucl.ac.uk/isd/how-to/connecting-to-eduroam-wi-fi-linux I usually use the "No CA certificate is required" option as shown in the second guide. The "Inner authentication" is the default option, MSCHAPv2. Log attached. Thanks! ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+attachment/5566574/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Incomplete Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Don't know if this is possible, but would there be a way to have gdb stop at the point where the segfault occurs in the updated library when using the previous release to see what differs? I want to help you track this down, but I am unsure what else I can do at this point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: Today I have been encountering segfaults in fcl and virtualbox: Mar 2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks suppressed Mar 2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27] Mar 2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0). Mar 2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 1000 dumped core.#012#012Stack trace of thread 933482:#012#0 0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded. and: Mar 2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27] Mar 2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 c0 74 12 Mar 2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0). Mar 2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0 0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 0x2b4218)#012#1 0x0002 n/a (n/a + 0x0) Mar 2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: Succeeded. As this library has not changed I am assuming the problem is with one of the libraries it depends upon. Several packages were updated in the past few days, I believe including some that may be the cause of the problem. I have attached a zip with my /var/log/apt/term.log and history.log for inspection. Version of library is 2.24.32-4ubuntu4 and library file is dated 2021-03-31 here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963934] [NEW] Audio device not detected after pipewire update
Public bug reported: Hi folks, I'm running Ubuntu 22.04 with latest mainline kernel 5.15.26 and the rest should be vanilla. After the updates on Sunday March 6th, which mostly look like pipewire-related from 0.3.47 to 0.3.48, my audio devices are no longer detected: settings only shows the dummy device, pressing the volume buttons on my keyboard do nothing, trying to connect my bluetooth headset outputs these lines in /var/log/syslog: Mar 7 10:41:47 jrrr bluetoothd[567]: message repeated 88 times: [ src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed] Mar 7 10:41:47 jrrr bluetoothd[567]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 0C:C4:13:08:0A:FB: Protocol not available Mar 7 10:41:47 jrrr bluetoothd[567]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed I hope that helps! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pipewire 0.3.48-1ubuntu1 Uname: Linux 5.15.26-051526-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 10:37:23 2022 InstallationDate: Installed on 2022-02-11 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1963934 Title: Audio device not detected after pipewire update Status in pipewire package in Ubuntu: New Bug description: Hi folks, I'm running Ubuntu 22.04 with latest mainline kernel 5.15.26 and the rest should be vanilla. After the updates on Sunday March 6th, which mostly look like pipewire-related from 0.3.47 to 0.3.48, my audio devices are no longer detected: settings only shows the dummy device, pressing the volume buttons on my keyboard do nothing, trying to connect my bluetooth headset outputs these lines in /var/log/syslog: Mar 7 10:41:47 jrrr bluetoothd[567]: message repeated 88 times: [ src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed] Mar 7 10:41:47 jrrr bluetoothd[567]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 0C:C4:13:08:0A:FB: Protocol not available Mar 7 10:41:47 jrrr bluetoothd[567]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed I hope that helps! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pipewire 0.3.48-1ubuntu1 Uname: Linux 5.15.26-051526-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 10:37:23 2022 InstallationDate: Installed on 2022-02-11 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963820] Re: Upgrade to 22.04 misses wireplumber
Could you try if creating an empty /usr/share/pipewire/media- session.d/with-pulseaudio makes it work without having wireplumber installed? ** Changed in: pipewire (Ubuntu) Status: Invalid => New ** Summary changed: - Upgrade to 22.04 misses wireplumber + Fails to act a sound service unless wireplumber is installed ** Summary changed: - Fails to act a sound service unless wireplumber is installed + Fails to act a sound server unless wireplumber is installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1963820 Title: Fails to act a sound server unless wireplumber is installed Status in pipewire package in Ubuntu: New Bug description: I understand this is quite an exotic upgrade scenario, nevertheless here goes: After upgrading from my pipwire enabled Kubuntu 21.10 to 22.04 I had no usable output devices. It turns out I needed to install wireplumber to get my output devices back in plasma pa widget (and actually use them). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok + Old detection code: + + :~$ time ubuntu-drivers list + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + + real 0m13,751s + user 0m13,480s + sys 0m0,258s + + + :~$ time ubuntu-drivers list + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + + real 0m13,785s + user 0m13,578s + sys 0m0,196s + + + New detection code: + + :~$ time ubuntu-drivers list + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + + real 0m2,673s + user 0m1,749s + sys 0m0,914s + + + :~$ time ubuntu-drivers list + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + + real 0m2,645s + user 0m1,702s + sys 0m0,935s + + [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
I gave a try and I can confirm that following the modemmanager docs to enable FCC unlock procedure at ModemManager level, the modem is properly unlocked and connects to the internet. However, this is another issue, but the firmware crashing persist when trying to make use of the LTE connection a bit more than just sending a ping. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Thank you for your bug report, do you have details on what sort of configuration and security options is eduroam using? Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart, try to connect and share the 'journalctl -b 0' log from the system? ** Changed in: wpa (Ubuntu) Importance: Undecided => High ** Changed in: wpa (Ubuntu) Status: Confirmed => Incomplete ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Incomplete Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
There are two bugs, which may be duplicates, or not: - this one, which apparently became an FTBFS on ppc64el due to a test failure (the same test? Unclear to me) - #1962510 which is an armhf failure, also due to tests failing during build Maybe a no-change rebuild should be uploaded, to confirm what's the current status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: New Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962170] Re: DEP8 failure with samba 4.15.5
Fixed in https://launchpad.net/ubuntu/+source/adsys/0.8ubuntu1 via the quick fix by Michael (thanks). AFAIU you wanted to keep the bug open for a better solution down the road? ** Tags removed: server-todo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1962170 Title: DEP8 failure with samba 4.15.5 Status in adsys package in Ubuntu: New Bug description: The DEP8 tests of adsys started to fail[1] with my samba 4.15.5 upload. Some hints: ahasenack: it seems we can’t start our smbd local daemon to simulate Active Directory smb server ahasenack: yeah, I’m puzzled because on smbd start failure, we do print stderr (not stdout though): https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L16 https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L43 in particular you can see here how we start it: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L21 and the config template is at https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/internal/testutils/samba.go#L55 2022/02/24 03:13:59 Setup: smbd hasn’t started successfully that's here: https://github.com/ubuntu/adsys/blob/main/internal/testutils/samba.go#L129 you wait for the port to be open? which port is that, 445/tcp? we wait on the port to be opened, and this one is passed as a parameter, see the template. For the argument we pass in ad tests, once sec, looking 1446 https://github.com/ubuntu/adsys/blob/20e6f962eb87f667f5e29800be0715ab2496a10d/cmd/integration_tests/adsys_test.go#L47 you just need to run go test . in internal/ad/ the failure is as the pre-test setup 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/adsys/20220224_031434_4d453@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1962170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962642] Re: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected
Thank you for your bug report, was that a one time error or do you get it at every start? ** Changed in: geoclue-2.0 (Ubuntu) Importance: Undecided => Low ** Changed in: geoclue-2.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962642 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in geoclue-2.0 package in Ubuntu: Incomplete Bug description: crash when booting ubuntu 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: geoclue-2.0 2.5.7-3ubuntu2 Uname: Linux 5.15.25-xanmod1-tt x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: pass Date: Sun Feb 27 02:18:52 2022 ExecutablePath: /usr/libexec/geoclue InstallationDate: Installed on 2022-02-23 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223) ProcCmdline: /usr/libexec/geoclue Signal: 6 SourcePackage: geoclue-2.0 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8920a69b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f8920a6c5d8 "malloc_consolidate(): unaligned fastbin chunk detected") at ./malloc/malloc.c:5664 malloc_consolidate (av=av@entry=0x7f8920aa2c80 ) at ./malloc/malloc.c:4750 _int_free (av=0x7f8920aa2c80 , p=0x563158ab8580, have_lock=) at ./malloc/malloc.c:4674 __GI___libc_free (mem=) at ./malloc/malloc.c:3391 Title: geoclue assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1962642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963756] Re: Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on
Hmm.. I installed gnome-shell and mutter and friends from jammy- proposed, and after that the desktop icons show up as expected both on Xorg and Wayland. So it looks like this is just a temporary state which will not be present when gnome-shell and mutter have been upgraded from 41 to 42. Closing this bug report. Please feel free to request it to be re-opened if you find that the issue is still present with version 42 of gnome- shell and mutter in place. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1963756 Title: Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Invalid Bug description: 1. Observe icons from Desktop Icons NG on desktop. 2. Log out. 3. Log back in. 4. Observe that desktop icons are gone. 5. Open Extensions app. 6. Observe that the Desktop Icons NG extension is enabled. 7. Turn it off and turn it back on. 8. Observe that the missing desktop icons now appear. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-desktop-icons-ng 39-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 5 13:06:10 2022 InstallationDate: Installed on 2019-01-02 (1158 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons-ng UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1963756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
Thanks, I just saw that Jammy has 1.26.2. I might try and give it a try to verify the behavior of the LTE modem there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Hello Alberto! Thank you for filling in the FFe! Did you do a test-build of the change on some PPA that we could take a look at? And did you do a test install of the test packages so that you could provide some logs? The changes seem on one side simple, but touch a lot of the code, so I'm obviously a bit worried about any bumps. How noticeable is the performance improvement? Has this been measured? Just trying to assess the risk-to-merit ratio here ;) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963241] Re: [FFe] evince 42
Hey Jeremy! Thanks for filling in this FFe. Did you do a test build of the new evince for non-amd64 architectures as well (like in some PPA, for instance)? Also, I assume that the two reverted commits for the new libarchive support have been rather non-invasive, right? If the answer is 'yes' for both, I think we can go ahead with this FFe. Seeing that the NEWS file advertises the libarchive >= 3.6.0 dependency, I was wondering: do you want/need to have this in jammy? Are we missing out (or risking regressing) some features by sticking with the old version? I don't think Foundations had plans on pulling in the new upstream version past FF, but we could discuss that if there is *actual* need for it (since it's out since last month). Though Debian's still on 3.5.2, and so far this was a merge/sync. ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963241 Title: [FFe] evince 42 Status in evince package in Ubuntu: Incomplete Bug description: Why Needed -- The Ubuntu Desktop had a goal of including as much of GNOME 42 as possible in Ubuntu 22.04 LTS. (One major exception was where apps had switched to GTK4). The evince document viewer (PDFs and more) did not have earlier releases in the 42 cycle and its Beta wasn't released until March 3, a week after Feature Freeze. The Ubuntu Desktop Team commits to packaging the final evince 42 stable release and working to fix any regressions introduced in the update. We do have the ability to use a "really" version number in case we decide we need to go back to the 41 version. What Changed https://gitlab.gnome.org/GNOME/evince/-/blob/42.beta/NEWS https://gitlab.gnome.org/GNOME/evince/-/compare/41.3...42.beta For this release I have reverted 2 commits that required a new version of libarchive since that wasn't included in 22.04 LTS yet. Build Test -- Builds successfully Install Test $ sudo apt install ./../build-area/*ev*.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'evince' instead of './../build-area/evince_42~beta-1_amd64.deb' Note, selecting 'evince-common' instead of './../build-area/evince-common_42~beta-1_all.deb' Note, selecting 'gir1.2-evince-3.0' instead of './../build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb' Note, selecting 'libevdocument3-4' instead of './../build-area/libevdocument3-4_42~beta-1_amd64.deb' Note, selecting 'libevview3-3' instead of './../build-area/libevview3-3_42~beta-1_amd64.deb' The following packages were automatically installed and are no longer required: libabsl20200923 libicu67 libpoppler115 Use 'sudo apt autoremove' to remove them. Suggested packages: unrar The following packages will be upgraded: evince evince-common gir1.2-evince-3.0 libevdocument3-4 libevview3-3 5 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B/821 kB of archives. After this operation, 803 kB disk space will be freed. Get:1 /home/jeremy/devel/pkg-gnome/build-area/evince-common_42~beta-1_all.deb evince-common all 42~beta-1 [132 kB] Get:2 /home/jeremy/devel/pkg-gnome/build-area/evince_42~beta-1_amd64.deb evince amd64 42~beta-1 [306 kB] Get:3 /home/jeremy/devel/pkg-gnome/build-area/libevdocument3-4_42~beta-1_amd64.deb libevdocument3-4 amd64 42~beta-1 [204 kB] Get:4 /home/jeremy/devel/pkg-gnome/build-area/libevview3-3_42~beta-1_amd64.deb libevview3-3 amd64 42~beta-1 [148 kB] Get:5 /home/jeremy/devel/pkg-gnome/build-area/gir1.2-evince-3.0_42~beta-1_amd64.deb gir1.2-evince-3.0 amd64 42~beta-1 [31.1 kB] (Reading database ... 207369 files and directories currently installed.) Preparing to unpack .../evince-common_42~beta-1_all.deb ... Unpacking evince-common (42~beta-1) over (41.3-3) ... Preparing to unpack .../evince_42~beta-1_amd64.deb ... Unpacking evince (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevdocument3-4_42~beta-1_amd64.deb ... Unpacking libevdocument3-4:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../libevview3-3_42~beta-1_amd64.deb ... Unpacking libevview3-3:amd64 (42~beta-1) over (41.3-3) ... Preparing to unpack .../gir1.2-evince-3.0_42~beta-1_amd64.deb ... Unpacking gir1.2-evince-3.0:amd64 (42~beta-1) over (41.3-3) ... Setting up evince-common (42~beta-1) ... Setting up libevdocument3-4:amd64 (42~beta-1) ... Setting up libevview3-3:amd64 (42~beta-1) ... Setting up evince (42~beta-1) ... Setting up gir1.2-evince-3.0:amd64 (42~beta-1) ... Processing triggers for desktop-file-utils (0.26-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu2) ... Processing triggers for libglib2.0-0:amd64
[Desktop-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
The new versions are in the current Ubuntu series, there is no plan to backport to impish though since that's a non LTS serie and there is limited demand for a such change ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: libmbim (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu) Importance: Undecided => Low ** Changed in: libmbim (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963911] [NEW] [snap] paste in composer does not work
Public bug reported: Hi, I switched (again!) from TB deb to TB snap (in Jammy), following the Firefox official way. Well, today I try to copy my calendar (Ctrl-Shift-PrintScreen) then paste in a new message as an image (Ctrl-V or Paste in menu). Nothing happens. The image is copied as I can paste it to LibreOffice. This bug is not present in TB deb. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1963911 Title: [snap] paste in composer does not work Status in thunderbird package in Ubuntu: New Bug description: Hi, I switched (again!) from TB deb to TB snap (in Jammy), following the Firefox official way. Well, today I try to copy my calendar (Ctrl-Shift-PrintScreen) then paste in a new message as an image (Ctrl-V or Paste in menu). Nothing happens. The image is copied as I can paste it to LibreOffice. This bug is not present in TB deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1963911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963902] Re: xdg-user-dirs-gtk-update not working properly
Thank you for your bug report. What xdg-user-dirs-gtk-update is doing is that if the session locale is changed to another language it will suggest renaming the directories to words that make sense in the new language ** Package changed: evince (Ubuntu) => xdg-user-dirs-gtk (Ubuntu) ** Changed in: xdg-user-dirs-gtk (Ubuntu) Importance: Undecided => Low ** Changed in: xdg-user-dirs-gtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963902 Title: xdg-user-dirs-gtk-update not working properly Status in xdg-user-dirs-gtk package in Ubuntu: Invalid Bug description: Hello. It seems to me that the xdg-user-dirs-gtk-update command does nothing at all. I want to change the location of the download directory. So I move the directory with this command: "mv -v /media/Common/a/Downloads /media/Common/a/BisDownloads" Then I update my reference file with this command: "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/DownloadsBis" Then I think to inform the software that the directory has changed by doing this command: "xdg-user-dirs-gtk-update" But when initiating a download, it cannot be done with the error message "...unable to save because an unknown error has occurred" Also, the "files" application continues to reference the old directory as if no update had been made. I have to log out and log back in to get everything working properly again. On the other hand, would it be possible to modify the contents of the file "user-dirs.dirs" to clearly say if the modification carried out by the command "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/TéléchargementsBis" is immediately carried out wherever necessary or if it is necessary to make another additional command or if it is necessary to wait for the next session launch because the message is not very understandable by saying only that the modifications are not lost. UBUNTU version 20.04 Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 13:09:20 2022 InstallationDate: Installed on 2022-02-16 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220216) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1963902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963758] Re: cups-browsed crashed with SIGSEGV in g_markup_parse_context_end_parse()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1963758 Title: cups-browsed crashed with SIGSEGV in g_markup_parse_context_end_parse() Status in cups-filters package in Ubuntu: New Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 cups-filters: Installed: 1.28.12-1 Candidate: 1.28.12-1 Version table: *** 1.28.12-1 500 500 http://it.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status I wasn't doing anything specific, just rebooted after installing all latest updates ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: cups-browsed 1.28.12-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Feb 23 21:24:00 2022 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2022-02-13 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220116) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Micro-Star International Co., Ltd. GS65 Stealth 8SE Papersize: a4 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=5053fbc2-94f5-4436-b882-67ae3ee204b6 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fe7dda6f73e:movl $0x1,0xa8(%rax) PC (0x7fe7dda6f73e) ok source "$0x1" ok destination "0xa8(%rax)" (0x556323bfc867) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 g_markup_parse_context_end_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: cups-browsed crashed with SIGSEGV in g_markup_parse_context_end_parse() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A dmi.bios.date: 05/18/2020 dmi.bios.release: 1.24 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q4IMS.118 dmi.board.asset.tag: Default string dmi.board.name: MS-16Q4 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q4IMS.118:bd05/18/2020:br1.24:svnMicro-StarInternationalCo.,Ltd.:pnGS65Stealth8SE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q4:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16Q4.1: dmi.product.family: GS dmi.product.name: GS65 Stealth 8SE dmi.product.sku: 16Q4.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1963758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
This issue affects me, too. Ubuntu mate 20.04 with Nvidia Quadro P2200 Graphics card. Please fix for the Mate desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
MP in upstream fixing the issue https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1232 https://gitlab.gnome.org/GNOME/network-manager-applet/-/merge_requests/108 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it Status in gnome-control-center package in Ubuntu: New Bug description: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963906] [NEW] Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
Public bug reported: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority third-party-packages ** Description changed: - Refer to gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1521 + Refer to https://gitlab.gnome.org/GNOME/gnome-control- + center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it Status in gnome-control-center package in Ubuntu: New Bug description: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963905] Re: /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 ** This bug has been marked a duplicate of bug 1962761 nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1963905 Title: /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:42~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/129adc3ee2e72c20335397eb652e701228616925 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962761] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
https://errors.ubuntu.com/problem/129adc3ee2e72c20335397eb652e701228616925 ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: Confirmed Bug description: It's part of a chain of bugs that come one after another as I try to report each one of them. Never saw this behavior before ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:32:37 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-01-03 (58 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=ro_RO.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5f445b49a8 : cmp %rax,(%rbx) PC (0x7f5f445b49a8) ok source "%rax" ok destination "(%rbx)" (0x71818181c7808080) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () at /lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963905] [NEW] /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:42~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/129adc3ee2e72c20335397eb652e701228616925 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: jammy vivid xenial yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1963905 Title: /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:42~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/129adc3ee2e72c20335397eb652e701228616925 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963902] [NEW] xdg-user-dirs-gtk-update not working properly
Public bug reported: Hello. It seems to me that the xdg-user-dirs-gtk-update command does nothing at all. I want to change the location of the download directory. So I move the directory with this command: "mv -v /media/Common/a/Downloads /media/Common/a/BisDownloads" Then I update my reference file with this command: "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/DownloadsBis" Then I think to inform the software that the directory has changed by doing this command: "xdg-user-dirs-gtk-update" But when initiating a download, it cannot be done with the error message "...unable to save because an unknown error has occurred" Also, the "files" application continues to reference the old directory as if no update had been made. I have to log out and log back in to get everything working properly again. On the other hand, would it be possible to modify the contents of the file "user-dirs.dirs" to clearly say if the modification carried out by the command "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/TéléchargementsBis" is immediately carried out wherever necessary or if it is necessary to make another additional command or if it is necessary to wait for the next session launch because the message is not very understandable by saying only that the modifications are not lost. UBUNTU version 20.04 Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 13:09:20 2022 InstallationDate: Installed on 2022-02-16 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220216) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1963902 Title: xdg-user-dirs-gtk-update not working properly Status in evince package in Ubuntu: New Bug description: Hello. It seems to me that the xdg-user-dirs-gtk-update command does nothing at all. I want to change the location of the download directory. So I move the directory with this command: "mv -v /media/Common/a/Downloads /media/Common/a/BisDownloads" Then I update my reference file with this command: "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/DownloadsBis" Then I think to inform the software that the directory has changed by doing this command: "xdg-user-dirs-gtk-update" But when initiating a download, it cannot be done with the error message "...unable to save because an unknown error has occurred" Also, the "files" application continues to reference the old directory as if no update had been made. I have to log out and log back in to get everything working properly again. On the other hand, would it be possible to modify the contents of the file "user-dirs.dirs" to clearly say if the modification carried out by the command "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/TéléchargementsBis" is immediately carried out wherever necessary or if it is necessary to make another additional command or if it is necessary to wait for the next session launch because the message is not very understandable by saying only that the modifications are not lost. UBUNTU version 20.04 Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 13:09:20 2022 InstallationDate: Installed on 2022-02-16 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220216) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
** Changed in: lightdm (Ubuntu) Status: Incomplete => Invalid ** Changed in: lightdm-gtk-greeter (Ubuntu) Status: Incomplete => Invalid ** Changed in: upstart (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed Status in Light Display Manager: New Status in lightdm package in Ubuntu: Invalid Status in lightdm-gtk-greeter package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: dm-tool lock starts a new lightdm greeter (for unlocking) and a new logind session. After unlocking the greeter disappears, but the logind session never closes. loginctl session status c24 reports something like: c24 - lightdm (103) Since: Thu 2014-05-22 18:38:27 CEST; 30min ago Leader: 7872 Seat: seat0; vc8 Display: :1 Service: lightdm-greeter; type x11; class greeter State: closing CGroup: systemd:/user/103.user/c24.session └─7907 init --user --startup-event indicator-services-start This results in an accumulation of stale lightdm sessions after using e.g. a session locker for a while. I get this issue on a freshly installed and fully updated Xubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963723] Re: Crash: 'No module named "dbus"'
sorry but no, we don't do Mint support, check with your distribution directly ** Changed in: system-config-printer (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1963723 Title: Crash: 'No module named "dbus"' Status in system-config-printer package in Ubuntu: Invalid Bug description: $ system-config-printer Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 29, in import dbus ModuleNotFoundError: No module named 'dbus' I have the problem on Linux Mint 20.3 Cinnamon, which is based upon Ubuntu 20.04; and/but a Mint developer advised me to report the problem here. $ apt list system-config-printer Listing... Done system-config-printer/focal-updates,focal-updates,now 1.5.12-0ubuntu1.1 all [installed] Cf. (among others?) ##1057256, 819053 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1963723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963820] Re: Upgrade to 22.04 misses wireplumber
Thanks but Ubuntu still default to pulseaudio so audio is disabled by default in pipewire, also see https://launchpad.net/ubuntu/+source/pipewire-media- session/0.4.1-2ubuntu1 in case you have pipewire-media-session installed ** Changed in: pipewire (Ubuntu) Importance: Undecided => Low ** Changed in: pipewire (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1963820 Title: Upgrade to 22.04 misses wireplumber Status in pipewire package in Ubuntu: Invalid Bug description: I understand this is quite an exotic upgrade scenario, nevertheless here goes: After upgrading from my pipwire enabled Kubuntu 21.10 to 22.04 I had no usable output devices. It turns out I needed to install wireplumber to get my output devices back in plasma pa widget (and actually use them). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963896] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 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 #1962761, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1963896/+attachment/5566468/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566470/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566474/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566475/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566476/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566477/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566478/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1962761 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1963896 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: New Bug description: nautilus crashed while running in background ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~beta-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 12:05:56 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-02-15 (19 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/bin/nautilus --gapplication-service RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7fb7ccd7c9a8 : cmp %rax,(%rbx) PC (0x7fb7ccd7c9a8) ok source "%rax" ok destination "(%rbx)" (0x7ff) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: Upgraded to jammy on 2022-02-15 (19 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince41.3-3 file-roller 3.41.90-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963863] Re: [snap] Firefox tries to open an application for localhost link
Launchpad has imported 10 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1740963. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-11-12T21:19:45+00:00 Wlach wrote: Created attachment 9250543 about:support On the latest version of Firefox beta (Ubuntu snap, 95.0b6), I get a prompt to use the "system handler" when opening a localhost link (e.g. http://localhost:3000) Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/0 On 2021-11-12T21:20:08+00:00 Wlach wrote: Created attachment 9250544 screenshot Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/1 On 2021-11-12T21:26:01+00:00 Wlach wrote: I tried a couple of nightlies (2021-11-01, 2021-11-10) via mozregression and neither of them exhibited this problem, which makes me wonder if this problem is snap specific. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/2 On 2021-12-01T14:07:16+00:00 Wlach wrote: Still happening in 95.0b12 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/3 On 2021-12-01T14:09:57+00:00 Wlach wrote: Oh wait, I see what's going on. If I type `http://localhost:3000` into the URL bar everything works as expected. Somehow it's interpreting `localhost` as a protocol handler. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/4 On 2021-12-02T13:03:51+00:00 Evilpies wrote: This is probably similar to bug 1618094, but I am not sure if the flatpak issue applies to snap as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/5 On 2021-12-06T00:16:32+00:00 Release-mgmt-account-bot wrote: The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/6 On 2022-02-08T10:36:37+00:00 Olivier Tilloy wrote: I can see the prompt when I type e.g. `localhost:3000` in the address bar and press enter. However clicking on the hyperlink in the description of this bug does the right thing, probably because the target of the link is `http://localhost:3000` (scheme included). This is with the snap version 97.0 (currently in the candidate channel, expected to be promoted to stable later today). I can confirm the deb package for the same version isn't affected. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/7 On 2022-02-08T10:41:33+00:00 Olivier Tilloy wrote: Related: bug 1744243. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/8 On 2022-02-18T02:43:06+00:00 Wlach wrote: This appears to be working now, though I'm now seeing bug 1756083 which might be related. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1963863/comments/9 ** Changed in: firefox Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1963863 Title: [snap] Firefox tries to open an application for localhost link Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When I'm opening an address like localhost:8080 (without the http), snap firefox will assume that 'localhost' is the scheme and start an application that registered localhost: To test, open Firefox and type 'localhost:8080' in the address bar and hit enter. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1963863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963754] Re: No brightness slider in settings
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1963754 Title: No brightness slider in settings Status in gnome-shell package in Ubuntu: New Bug description: This page mentions a brightness slider : https://help.ubuntu.com/22.04/ubuntu-help/display-brightness.html.en When I click on the system settings I see a (sound) volume slider but no brightness slider. screenshot : https://i.imgur.com/N6EWUra.png lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 apt update/upgrade done today 2022-03-05 Gnome version 42.beta Windowing system X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963754] [NEW] No brightness slider in settings
You have been subscribed to a public bug: This page mentions a brightness slider : https://help.ubuntu.com/22.04/ubuntu-help/display-brightness.html.en When I click on the system settings I see a (sound) volume slider but no brightness slider. screenshot : https://i.imgur.com/N6EWUra.png lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 apt update/upgrade done today 2022-03-05 Gnome version 42.beta Windowing system X11 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- No brightness slider in settings https://bugs.launchpad.net/bugs/1963754 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963863] Re: Typing localhost:8080 no longer works since the snap
** Bug watch added: Mozilla Bugzilla #1740963 https://bugzilla.mozilla.org/show_bug.cgi?id=1740963 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1740963 Importance: Unknown Status: Unknown ** Changed in: firefox (Ubuntu) Status: New => Confirmed ** Changed in: firefox (Ubuntu) Importance: Undecided => Medium ** Tags added: snap ** Summary changed: - Typing localhost:8080 no longer works since the snap + [snap] Firefox tries to open an application for localhost link -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1963863 Title: [snap] Firefox tries to open an application for localhost link Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: When I'm opening an address like localhost:8080 (without the http), snap firefox will assume that 'localhost' is the scheme and start an application that registered localhost: To test, open Firefox and type 'localhost:8080' in the address bar and hit enter. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1963863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Tags removed: gdm3
** Tags added: nvidia
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
To manage
[Desktop-packages] [Bug 1956143] Re: gnome-control-center requires libcheese8 and libcheese-gtk25
the -faces package contains only icons, libcheese is used by the user panel to allow taking a picture for the profile, it's a shared library and isn't optional, without it the users panel wouldn't start -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956143 Title: gnome-control-center requires libcheese8 and libcheese-gtk25 Status in gnome-control-center package in Ubuntu: Expired Bug description: gnome-control-center requires libcheese8 and libcheese-gtk25 even though gnome-control-center-faces is a recommended package. The functionality isn't there on a minimal installation but all three of these packages are. The library packages cannot be removed because they are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Summary changed:
- [nvidia][xorg] display hangs on boot LOGO
+ [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia
driver probe
** Tags added: gdm3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
[1]
