[Desktop-packages] [Bug 2059149] Re: Xorg crash
It appears the recurring problem here is: simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem) WARNING: CPU: 19 PID: 4751 at drivers/gpu/drm/drm_gem_shmem_helper.c:319 drm_gem_shmem_vmap+0x1a5/0x1e0 ** Summary changed: - Xorg crash + Crash ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/2059149 Title: Crash Status in linux package in Ubuntu: Incomplete Bug description: X display crashes when disconnecting and reconnecting my monitors. This appears to be different than my KVM issue. I am not seeing drm gpu error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 11:36:54 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102GL [RTX A5000] [10de:2231] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102GL [RTX A5000] [10de:147e] InstallationDate: Installed on 2022-04-07 (719 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash nvidia-drm.modeset=1 initcall_blacklist=acpi_cpufreq_init amd_pstate=active amd_pstate.shared_mem=1 acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd09/26/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059149/+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 2055479] Re: I2S DAC not loading
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2055479 Title: I2S DAC not loading Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am attempting to add an I2S DAC for line level output on a Raspberry Pi 5. The hardware is a Pimoroni Audio DAC Shim which uses the dtoverlay=hifiberry-dac The hardware, when used with Raspberry Pi OS (Bookworm) configured per instructions works fine, this I2S output DAC appears in the sound output selector pull-down, line-out works, so hardware and connections are good. When installed and configured on Ubuntu 23.10 Desktop, fully updated to current, the I2S DAC output does appear in the sound pull-down selector window, so the I2S DAC output can not be selected, and is not functional. Configuration consists of adding the following to the /boot/firmware/config.txt file: dtparam=i2s=on dtoverlay=hifiberry-dac When a user signs into Ubuntu, a pair of error messages appears 25 times in the CLI ttyAMA10 output: [ 23.126215] designware-i2s 1f000a.i2s: ASoC: error at snd_soc_dai_set_bclk_ratio on 1f000a.i2s: -22 [ 23.136303] HifiBerry DAC: ASoC: error at snd_soc_link_hw_params on HifiBerry DAC: -22 This seems to reference some kind of failure to initialize an I2S bit clock ratio parameter on the part of designware-i2s, which causes HiFiBerry DAC to error out. ~$ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 All updates are current as of 2024 FEB 29 the dtoverlay=hifiberry-dac is the one distributed with the Ubuntu 23.10 Desktop release. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-1011.14-raspi 6.5.8 Uname: Linux 6.5.0-1011-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: graham 1907 F wireplumber /dev/snd/seq:graham 1894 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Feb 29 16:08:26 2024 PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2055479/+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 2059187] [NEW] fails in autopkgtest on gnome-desktop-testing
Public bug reported: flatpak fails autopkgtest like so: 1125s Updating appstream branch 1125s Updating summary 1125s ok app with mismatched metadata (in summary) can't be installed 1125s test-metadata-validation.sh:158 - app with mismatched metadata (in summary) can't be installed 1125s OK closing connection 1125s fusermount: entry for /tmp/test-flatpak-MPRPRX/runtime/doc not found in /etc/mtab 1125s PASS: Flatpak/test-metadata-validation.sh.test 1125s SUMMARY: total=45; passed=38; skipped=0; failed=7; user=205.6s; system=150.8s; maxrss=423860 1125s FAIL: Flatpak/test-bun...@system.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/testlibrary.test (Child process killed by signal 6) 1125s FAIL: Flatpak/test-bun...@system-norevokefs.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,nodeltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,nodeltas.wrap.test (Child process exited with code 1) 1125s /tmp/autopkgtest.Kstx4F/wrapper.sh: Killing leaked background processes: 9343 1125s PID TTY STAT TIME COMMAND 1125s9343 ?S 0:00 /usr/bin/python3 /usr/libexec/installed-tests/Flatpak/web-server.py repos 1125s autopkgtest [07:37:45]: test gnome-desktop-testing: ---] 1126s autopkgtest [07:37:46]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - 1126s gnome-desktop-testing FAIL non-zero exit status 2 https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/f/flatpak/20240324_073939_33ef3@/log.gz ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2059187 Title: fails in autopkgtest on gnome-desktop-testing Status in flatpak package in Ubuntu: New Bug description: flatpak fails autopkgtest like so: 1125s Updating appstream branch 1125s Updating summary 1125s ok app with mismatched metadata (in summary) can't be installed 1125s test-metadata-validation.sh:158 - app with mismatched metadata (in summary) can't be installed 1125s OK closing connection 1125s fusermount: entry for /tmp/test-flatpak-MPRPRX/runtime/doc not found in /etc/mtab 1125s PASS: Flatpak/test-metadata-validation.sh.test 1125s SUMMARY: total=45; passed=38; skipped=0; failed=7; user=205.6s; system=150.8s; maxrss=423860 1125s FAIL: Flatpak/test-bun...@system.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/testlibrary.test (Child process killed by signal 6) 1125s FAIL: Flatpak/test-bun...@system-norevokefs.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,nodeltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,nodeltas.wrap.test (Child process exited with code 1) 1125s /tmp/autopkgtest.Kstx4F/wrapper.sh: Killing leaked background processes: 9343 1125s PID TTY STAT TIME COMMAND 1125s9343 ?S 0:00 /usr/bin/python3 /usr/libexec/installed-tests/Flatpak/web-server.py repos 1125s autopkgtest [07:37:45]: test gnome-desktop-testing: ---] 1126s autopkgtest [07:37:46]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - 1126s gnome-desktop-testing FAIL non-zero exit status 2 https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/f/flatpak/20240324_073939_33ef3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2059187/+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 2059177] [NEW] dev package doesn't include *Config.cmake files
Public bug reported: For several years now, Ogg has supported auto-generated and exported CMake configuration, especially when building Ogg with CMake. Properly installed, this allows someone to merely use `find_package(Ogg)` in their CMake project without having to jump through hoops. An example where this is done well in Ubuntu is qtbase5-dev. $ dpkg -L qtbase5-dev |grep Config.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Concurrent/Qt5ConcurrentConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5DBus/Qt5DBusConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5EglFsKmsSupport/Qt5EglFsKmsSupportConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Network/Qt5NetworkConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5OpenGLExtensions/Qt5OpenGLExtensionsConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport/Qt5PrintSupportConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5SqlConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Test/Qt5TestConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml/Qt5XmlConfig.cmake An example where this is done well for Ogg is Homebrew @ https://github.com/Homebrew/homebrew- core/blob/175a655dbe76d08350ff941f9c9d7fd9ef2933d0/Formula/lib/libogg.rb Please include the `*Config.cmake` files (and friends) in the Ogg family of packages. ** Affects: libogg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libogg in Ubuntu. https://bugs.launchpad.net/bugs/2059177 Title: dev package doesn't include *Config.cmake files Status in libogg package in Ubuntu: New Bug description: For several years now, Ogg has supported auto-generated and exported CMake configuration, especially when building Ogg with CMake. Properly installed, this allows someone to merely use `find_package(Ogg)` in their CMake project without having to jump through hoops. An example where this is done well in Ubuntu is qtbase5-dev. $ dpkg -L qtbase5-dev |grep Config.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Concurrent/Qt5ConcurrentConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5DBus/Qt5DBusConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5EglFsKmsSupport/Qt5EglFsKmsSupportConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Network/Qt5NetworkConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5OpenGLExtensions/Qt5OpenGLExtensionsConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5PrintSupport/Qt5PrintSupportConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Sql/Qt5SqlConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Test/Qt5TestConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake /usr/lib/x86_64-linux-gnu/cmake/Qt5Xml/Qt5XmlConfig.cmake An example where this is done well for Ogg is Homebrew @ https://github.com/Homebrew/homebrew- core/blob/175a655dbe76d08350ff941f9c9d7fd9ef2933d0/Formula/lib/libogg.rb Please include the `*Config.cmake` files (and friends) in the Ogg family of packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libogg/+bug/2059177/+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 2056595] Re: Lot of SyntaxWarning messages for rhythmbox
Same here:
Setting up rhythmbox-plugins (3.4.7-2ubuntu2) ...
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66:
SyntaxWarning: invalid escape sequence '\/'
title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
[...]
** Tags added: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/2056595
Title:
Lot of SyntaxWarning messages for rhythmbox
Status in rhythmbox package in Ubuntu:
Confirmed
Bug description:
During recent updates on Ubuntu 24.04 I see Lot of SyntaxWarning
messages for rhythmbox
/usr/lib/rhythmbox/plugins/alternative-toolbar/alttoolbar_plugins.py:171:
SyntaxWarning: invalid escape sequence '\('
translation = re.sub('\(..\)', '', translation, flags=re.DOTALL)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66:
SyntaxWarning: invalid escape sequence '\/'
title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:97:
SyntaxWarning: invalid escape sequence '\/'
lyrics = re.split('()(.*)(<\/font>http://jetlyrics\.com/viewlyrics\.php\?id=[0-9]*)\'>', result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/JlyricParser.py:49:
SyntaxWarning: invalid escape sequence '\.'
m = re.search('',
result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/TerraParser.py:39:
SyntaxWarning: invalid escape sequence '\w'
pattern = re.compile("&(#?\w+?);")
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/WinampcnParser.py:87:
SyntaxWarning: invalid escape sequence '\['
lrcplaintext = re.sub('\[.*?\]', '', lrcplaintext)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2056595/+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 2056595] Re: Lot of SyntaxWarning messages for rhythmbox
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rhythmbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/2056595
Title:
Lot of SyntaxWarning messages for rhythmbox
Status in rhythmbox package in Ubuntu:
Confirmed
Bug description:
During recent updates on Ubuntu 24.04 I see Lot of SyntaxWarning
messages for rhythmbox
/usr/lib/rhythmbox/plugins/alternative-toolbar/alttoolbar_plugins.py:171:
SyntaxWarning: invalid escape sequence '\('
translation = re.sub('\(..\)', '', translation, flags=re.DOTALL)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66:
SyntaxWarning: invalid escape sequence '\/'
title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:97:
SyntaxWarning: invalid escape sequence '\/'
lyrics = re.split('()(.*)(<\/font>http://jetlyrics\.com/viewlyrics\.php\?id=[0-9]*)\'>', result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/JlyricParser.py:49:
SyntaxWarning: invalid escape sequence '\.'
m = re.search('',
result)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/TerraParser.py:39:
SyntaxWarning: invalid escape sequence '\w'
pattern = re.compile("&(#?\w+?);")
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/WinampcnParser.py:87:
SyntaxWarning: invalid escape sequence '\['
lrcplaintext = re.sub('\[.*?\]', '', lrcplaintext)
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/lyrics.py:44:
SyntaxWarning: invalid escape sequence '\('
LYRIC_TITLE_STRIP=["\(live[^\)]*\)", "\(acoustic[^\)]*\)", "\([^\)]*mix\)",
"\([^\)]*version\)", "\([^\)]*edit\)", "\(feat[^\)]*\)"]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2056595/+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 2059166] Re: Nautilus doesn't show hidden files under computer/>>>
** Package changed: ubiquity (Ubuntu) => nautilus (Ubuntu) -- 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/2059166 Title: Nautilus doesn't show hidden files under computer/>>> Status in nautilus package in Ubuntu: New Bug description: In Nautilus, when I go to the file list under "otherlocations/computer", the hidden files will not display. I have tried checking the "show hidden files", and the keyboard shortcut cntl+H , but they don't uncover the hidden file. In the terminal if I go to say '/etc' and do "ls -a", all the hidden and not hidden files will show, but the hidden files do not have a period in front of them. I did submit ubuntu-bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: User Name 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 18:07:37 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2023-09-14 (194 days ago) InstallationMedia: Ubuntu 20.04.4 gb3b LTS amd64 "Ip3 Focal Fossa" (20220425) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to jammy on 2024-03-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2059166/+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 2059166] [NEW] Nautilus doesn't show hidden files under computer/>>>
You have been subscribed to a public bug: In Nautilus, when I go to the file list under "otherlocations/computer", the hidden files will not display. I have tried checking the "show hidden files", and the keyboard shortcut cntl+H , but they don't uncover the hidden file. In the terminal if I go to say '/etc' and do "ls -a", all the hidden and not hidden files will show, but the hidden files do not have a period in front of them. I did submit ubuntu-bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: User Name 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 18:07:37 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2023-09-14 (194 days ago) InstallationMedia: Ubuntu 20.04.4 gb3b LTS amd64 "Ip3 Focal Fossa" (20220425) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to jammy on 2024-03-25 (1 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-20.04.15.19 wayland-session -- Nautilus doesn't show hidden files under computer/>>> https://bugs.launchpad.net/bugs/2059166 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus 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 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
Debian had added their own cups.pc file to CUPS 2.4.7, overlooking that already in 2.4.6 upstream has introduced a cups.pc file which is much more comprehensive. This broke the autopkgtest of cups-browsed in noble. Fixed in cups 2.4.7-1.2ubuntu2. ** Changed in: cups (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to c2esp in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: Fix Committed Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2058881] Re: [snap] Allow chromium snap to access Pressure Stall Information (PSI)
I've not observed any problems or hindrance as a result of these denials, no. Just more noise and thought maybe Chromium was going to use the pressure stall information for something useful like for the selection of which tabs/process to kill off when the system is experiencing pressure in either CPU, I/O, and/or memory. But all good if it does not and it does not plan to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2058881 Title: [snap] Allow chromium snap to access Pressure Stall Information (PSI) Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Currently seeing this: | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:657): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/cpu" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:658): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/io" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid=0 | Mar 25 16:12:23 dharkan.local kernel: audit: type=1400 audit(1711343543.539:659): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/proc/pressure/memory" pid=63335 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=3134 ouid> It seems the AppAmor profile should be updated to allow Chromium access to the pressure stall information for it to monitor and manage it's processes? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058881/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems
So what does that mean for ubuntu? Will it be included or will we have to include this on our own? -- 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/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in SDDM: New Status in linux-raspi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/sddm/+bug/2044718/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems
So does this mean that ubuntu will include this or will we have to do it on our own? -- 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/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in SDDM: New Status in linux-raspi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/sddm/+bug/2044718/+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 2059158] [NEW] proposed-migration for gtk4 4.14.1+ds-0ubuntu1
Public bug reported: gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on armhf. 1706s # Running test: gtk-4.0/tools/settings.test 1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126) 1706s not ok - gtk-4.0/tools/settings.test 2100s # Running test: gtk-4.0/tools/simplify.test 2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126) 2100s not ok - gtk-4.0/tools/simplify.test almost certainly time-t related. ** Affects: gtk4 (Ubuntu) Importance: Critical Status: New ** Tags: time-t update-excuse ** Description changed: - gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed. + gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on + armhf. + + 1706s # Running test: gtk-4.0/tools/settings.test + 1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126) + 1706s not ok - gtk-4.0/tools/settings.test + + 2100s # Running test: gtk-4.0/tools/simplify.test + 2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126) + 2100s not ok - gtk-4.0/tools/simplify.test + + almost certainly time-t related. ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Critical ** Tags added: time-t -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2059158 Title: proposed-migration for gtk4 4.14.1+ds-0ubuntu1 Status in gtk4 package in Ubuntu: New Bug description: gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on armhf. 1706s # Running test: gtk-4.0/tools/settings.test 1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126) 1706s not ok - gtk-4.0/tools/settings.test 2100s # Running test: gtk-4.0/tools/simplify.test 2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126) 2100s not ok - gtk-4.0/tools/simplify.test almost certainly time-t related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2059158/+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 2059157] [NEW] proposed-migration for cups 2.4.7-1.2ubuntu1
Public bug reported: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. ** Affects: c2esp (Ubuntu) Importance: Critical Status: New ** Affects: cups (Ubuntu) Importance: Critical Status: New ** Tags: time-t update-excuse ** Description changed: - cups 2.4.7-1.2ubuntu1 is stuck in -proposed. + multiple cups-related packages are having test failures on armhf after time_t transition. + https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf + https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 + + I am suspecting a common cups-based issue. + + cups-browsed already has a separate bug open at + https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. ** Tags added: time-t ** Changed in: cups (Ubuntu) Importance: Undecided => Critical ** Also affects: c2esp (Ubuntu) Importance: Undecided Status: New ** Changed in: c2esp (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2059157] Re: proposed-migration for cups 2.4.7-1.2ubuntu1
marking critical because these packages are being allowed into the release pocket as-is but the printing stack may be broken, which is of high importance in a server/embedded context. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2059157 Title: proposed-migration for cups 2.4.7-1.2ubuntu1 Status in c2esp package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: multiple cups-related packages are having test failures on armhf after time_t transition. https://autopkgtest.ubuntu.com/packages/c/c2esp/noble/armhf https://launchpad.net/ubuntu/+source/cups-browsed/2.0.0-0ubuntu9 I am suspecting a common cups-based issue. cups-browsed already has a separate bug open at https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/c2esp/+bug/2059157/+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 2059033] Re: Xorg crashes with SIGABRT
Tried kernel parameter i915.enable_dc=0 as suggested by https://wiki.archlinux.org/title/intel_graphics#Crash.2Ffreeze_on_low_power_Intel_CPUs; still crashes -- 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/2059033 Title: Xorg crashes with SIGABRT Status in Mesa: New Status in mesa package in Ubuntu: New Bug description: I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915 graphics driver. I am seeing random Xorg crashes due to SIGABRT, which kicks me back to the login screen. Ubuntu version: 22.04 Kernel version: 5.19.0-50-generic libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 I am seeing this message in kern.log: i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617] I have also gotten a core dump; here is the track trace: #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352 #6 0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879 #7 0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #8 0x560c5cc72abd in OsSigHandler (unused=, sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156 #9 OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at ../../../../os/osinit.c:110 #10 #11 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:44 #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at ./nptl/pthread_kill.c:78 #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79 #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, file=, line=) at ../src/gallium/drivers/iris/iris_batch.c:1116 #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, out_fence=0x0, flags=) at ../src/gallium/drivers/iris/iris_fence.c:267 #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at ../src/mesa/state_tracker/st_cb_flush.c:60 #19 st_glFlush (ctx=, gallium_flush_flags=0) at ../src/mesa/state_tracker/st_cb_flush.c:94 #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, timeout=0x713af054) at ../../../../glamor/glamor.c:285 #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, timeout=0x713af054) at ../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701 #22 0x560c5cb01095 in BlockHandler (pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394 #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:201 #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492 #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, envp=) at ../../../../dix/main.c:272 #26 0x7f72fec29d90 in __libc_start_call_main (main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , argc=11, argv=0x713af268, init=, fini=, rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392 #28 0x560c5cae9605 in _start () This post describes a similar issue: https://gitlab.freedesktop.org/drm/intel/-/issues/4858 I tried using a workaround from the above link, to set GPU to max frequency using command "intel_gpu_frequency -m", this seemed to reduce the rate of occurrence from once per day to once every 3 days, but this is not a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2059033/+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 2059149] [NEW] Xorg crash
Public bug reported: X display crashes when disconnecting and reconnecting my monitors. This appears to be different than my KVM issue. I am not seeing drm gpu error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 11:36:54 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102GL [RTX A5000] [10de:2231] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102GL [RTX A5000] [10de:147e] InstallationDate: Installed on 2022-04-07 (719 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=c56061b9-1478-4914-a919-96eb077fff48 ro quiet splash nvidia-drm.modeset=1 initcall_blacklist=acpi_cpufreq_init amd_pstate=active amd_pstate.shared_mem=1 acpi_enforce_resources=lax vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd09/26/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash noble ubuntu -- 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/2059149 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: X display crashes when disconnecting and reconnecting my monitors. This appears to be different than my KVM issue. I am not seeing drm gpu error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 11:36:54 2024 DistUpgraded: Fresh install
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
We should solve this issue before Earth Day. It has caused a lot of wastage of electricity. -- 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/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 2058409] Re: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found
The postinstall runs fails because luatex now has the 'socket' functionality disabled by default. [CVE-2023-32668] The upstream source for mtxrun has --socket added to the luatex command line to reenable the functionality while running 'mtxrun --make'. See lines having '--socket' in https://source.contextgarden.net/mtxrun.lua I think that there are two bugs here: 1) The mismatch between luatex and context regarding --socket, and 2) The post-install hangs indefinitely rather than returning an error. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32668 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2058409 Title: Install of tevlive-full hangs: tex/context/base/mkiv/l-sandbox.lua:180: module 'socket.core' not found Status in texlive-base package in Ubuntu: Confirmed Bug description: Before 3 weeks at least it was possible to install texlive-full without any issues. Now this is not possible anymore. So the bug was probably introduced with one of the latest updates. How to reproduce: Install package texlive-full $ apt install texlive-full Install hangs: texlive-lang-japanese (2021.20220204-1) wird eingerichtet ... context (2021.03.05.20220211-1) wird eingerichtet ... Running mtxrun --generate. This may take some time... done. Pregenerating ConTeXt MarkIV format. This may take some time... Related running processes: root 18747 0.4 0.0 13936 7456 pts/2Ss+ 17:47 0:01 /usr/bin/dpkg --status-fd 43 --configure --pending root 20584 0.0 0.0 2892 960 pts/2S+ 17:48 0:00 /bin/sh /var/lib/dpkg/info/context.postinst configure root 20592 0.0 0.0 2892 1064 pts/2S+ 17:48 0:00 /bin/sh /usr/bin/luatools --make cont-en root 20593 0.1 0.9 92868 79952 pts/2S+ 17:48 0:00 texlua /usr/bin/mtxrun --script base --make cont-en root 20596 0.0 0.0 2892 1004 pts/2S+ 17:48 0:00 sh -c /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv root 20597 0.0 0.3 40816 28684 pts/2S+ 17:48 0:00 /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv Run luatex manually: # /usr/bin/luatex --ini --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv This is LuaTeX, Version 1.14.0 (TeX Live 2022/dev/Debian) (INITEX) system commands enabled. (/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv (/usr/share/texmf/tex/context/base/mkiv/context.mkiv (/usr/share/texmf/tex/context/base/mkiv/syst-ini.mkiv) (/usr/share/texmf/tex/context/base/mkiv/norm-ctx.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-pln.mkiv) (/usr/share/texmf/tex/context/base/mkiv/syst-mes.mkiv) (/usr/share/texmf/tex/context/base/mkiv/luat-cod.mkiv<+ /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-bas.mkiv loading: ConTeXt Lua Macros / Basic Lua Libraries<+ /usr/share/texmf/tex/context/base/mkiv/l-bit32.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lua.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sandbox.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-package.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-lpeg.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-function.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-string.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-table.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-boolean.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-number.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-math.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-io.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-os.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-file.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-gzip.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-md5.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-sha.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-dir.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-unicode.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-url.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-set.lua><+ /usr/share/texmf/tex/context/base/mkiv/l-macro-imp-optimize.lua>) (/usr/share/texmf/tex/context/base/mkiv/luat-lib.mkiv loading: ConTeXt Lua Macros / Libraries<+ /usr/share/texmf/tex/context/base/mkiv/util-str.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-tab.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-fil.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sac.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-sto.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-pck.lua><+ /usr/share/texmf/tex/context/base/mkiv/util-prs.lua><+
[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
Please see bug 2056160 for the time being. -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2051894] Re: Cannot activate WWAN connection, repeatedly connects and disconnects very quickly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- 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/2051894 Title: Cannot activate WWAN connection, repeatedly connects and disconnects very quickly Status in modemmanager package in Ubuntu: Confirmed Bug description: I have a SIM installed and activated. If I boot into Windows I can verify connectivity works there. In Ubuntu I can see the connection. When I try to activate it, graphically it toggles on and off very quickly. mccli output is pasted below. I believe all the hardware is fully supported. This laptop can be ordered with Linux (Ubuntu 22.04 LTS) or Windows 10/11. It is a Lenovo ThinkPad z16 gen1 Additionally here's a screen cap of what I'm seeing in the UI https://photos.app.goo.gl/bsoQbF7KPC9zLufr6 # mmcli -m 0 -- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: 06d0e7ce8f0a51e2ae17d0340ef10fe5c0e7794e -- Hardware | manufacturer: Intel | model: MBIM [8086:7560] | firmware revision: 18601.5001.00.01.16.35_TM | h/w revision: V1.3 | supported: gsm-umts, lte |current: gsm-umts, lte | equipment id: 016175005936119 -- System | device: /sys/devices/pci:00/:00:01.3/:05:00.0 |drivers: iosm | plugin: Intel | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0at1 (at), wwan0mbim0 (mbim) -- Numbers |own: 16318330089ËFsÿ -- Status | unlock retries: sim-pin (3) | state: disabled |power state: low -- Modes| supported: allowed: 3g, 4g; preferred: none |current: allowed: 3g, 4g; preferred: none -- IP | supported: ipv4, ipv6, ipv4v6 -- 3GPP | imei: 016175005936119 | enabled locks: fixed-dialing | packet service state: detached -- 3GPP EPS | ue mode of operation: csps-2 | initial bearer ip type: ipv4v6 -- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 -- # journalctl -f -u NetworkManager.service Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2611] policy: auto-activating connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2614] device (wwan0mbim0): Activation: starting connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2614] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2781] device (wwan0mbim0): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2787] policy: auto-activating connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2791] device (wwan0mbim0): Activation: starting connection 'Google-Fi' (05250c1d-91b1-420c-99ec-f922b318a83d) Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2791] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2795] device (wwan0mbim0): state change: prepare -> deactivating (reason 'user-requested', sys-iface-state: 'managed') Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.2797] audit: op="device-disconnect" interface="wwan0mbim0" pid=3422 uid=1000 result="success" Jan 31 20:32:10 nickh-ThinkPad-Z16 NetworkManager[1115]: [1706754730.3267] device (wwan0mbim0): state change: deactivating ->
[Desktop-packages] [Bug 2051894] Re: Cannot activate WWAN connection, repeatedly connects and disconnects very quickly
Can reproduce on Noble (24.04), with a slightly different log but the same symptoms: Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.0747] device (wwan0mbim0): Activation: starting connection 'Mobile Internet' (43d34e84-2773-416a-9535-73ae2fc773ab) Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.0748] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.0750] manager: NetworkManager state is now CONNECTING Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1011] device (wwan0mbim0): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1015] manager: NetworkManager state is now CONNECTED_LOCAL Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1021] policy: auto-activating connection 'Mobile Internet' (43d34e84-2773-416a-9535-73ae2fc773ab) Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1025] device (wwan0mbim0): Activation: starting connection 'Mobile Internet' (43d34e84-2773-416a-9535-73ae2fc773ab) Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1026] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1027] manager: NetworkManager state is now CONNECTING Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1285] device (wwan0mbim0): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1289] manager: NetworkManager state is now CONNECTED_LOCAL Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1295] policy: auto-activating connection 'Mobile Internet' (43d34e84-2773-416a-9535-73ae2fc773ab) Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1300] device (wwan0mbim0): Activation: starting connection 'Mobile Internet' (43d34e84-2773-416a-9535-73ae2fc773ab) Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1301] device (wwan0mbim0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1303] manager: NetworkManager state is now CONNECTING Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1572] device (wwan0mbim0): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') Mar 26 14:59:13 ubuntu NetworkManager[2022]: [1711461553.1579] manager: NetworkManager state is now CONNECTED_LOCAL Maybe related to LP: #1592514 The SIM card works just fine on a spare smartphone and the data link can be established. No user is needed in the smartphone connection, so I do not understand the state changes. -- 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/2051894 Title: Cannot activate WWAN connection, repeatedly connects and disconnects very quickly Status in modemmanager package in Ubuntu: Confirmed Bug description: I have a SIM installed and activated. If I boot into Windows I can verify connectivity works there. In Ubuntu I can see the connection. When I try to activate it, graphically it toggles on and off very quickly. mccli output is pasted below. I believe all the hardware is fully supported. This laptop can be ordered with Linux (Ubuntu 22.04 LTS) or Windows 10/11. It is a Lenovo ThinkPad z16 gen1 Additionally here's a screen cap of what I'm seeing in the UI https://photos.app.goo.gl/bsoQbF7KPC9zLufr6 # mmcli -m 0 -- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: 06d0e7ce8f0a51e2ae17d0340ef10fe5c0e7794e -- Hardware | manufacturer: Intel | model: MBIM [8086:7560] | firmware revision: 18601.5001.00.01.16.35_TM | h/w revision: V1.3 | supported: gsm-umts, lte |current: gsm-umts, lte | equipment id: 016175005936119 -- System | device: /sys/devices/pci:00/:00:01.3/:05:00.0 |drivers: iosm | plugin: Intel | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0at1 (at), wwan0mbim0 (mbim) -- Numbers |own: 16318330089ËFsÿ -- Status | unlock retries: sim-pin (3) | state: disabled
[Desktop-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
I will share my experience maybe it can help. I am running this configuration CPU: 8-core AMD Ryzen 7 5800H with Radeon Graphics (-MT MCP-) speed/min/max: 400/400/4463 MHz Kernel: 6.5.0-26-generic x86_64 Up: 10m Mem: 3724.7/64145.7 MiB (5.8%) Storage: 2.75 TiB (59.2% used) Procs: 378 Shell: Bash inxi: 3.3.13 a Lenovo 82N6 Legion 7 16ACHg6. Now in kernel 5.15 the sound was back but external displays could not be detected. Can we use the sound ports of kernel 5.15 in kernel 6.5+? It would be awesome to finally see audio and video working at the same time on my machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2058930] Re: Missing in i386 Packages index
A fix was deployed (cowboyed) to the autopkgtest-cloud today. ** Changed in: libvpx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/2058930 Title: Missing in i386 Packages index Status in libvpx package in Ubuntu: Fix Committed Bug description: The new version of libvpx 1.14 seems not to be published to http://ftpmaster.internal on i386 only. This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any effect on i386: https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+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 2059121] [NEW] The gnome-initial-setup-copy-worker never seems to have the correct permissions to copy from /run/gnome-initial-setup go a users ~/.config
Public bug reported: There is a check in the copy worker that looks to see if the user running the copy worker owns the files it is trying to copy ``` if (!g_file_query_exists (src, NULL) || !file_is_ours (src)) exit (EXIT_SUCCESS); ``` From all my testing, the copy worker will always run as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here. My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass. Without this workaround, several settings applied in the gnome-initial- setup new user flow (mainly a11y) are not persisted to the new user after the gis process concludes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop] ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 14:31:52 2024 InstallationDate: Installed on 2024-03-02 (24 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Description changed: - These is a check in the copy worker that looks to see if the user + There is a check in the copy worker that looks to see if the user running the copy worker owns the files it is trying to copy ``` if (!g_file_query_exists (src, NULL) || - !file_is_ours (src)) - exit (EXIT_SUCCESS); + !file_is_ours (src)) + exit (EXIT_SUCCESS); ``` From all my testing, the copy worker will always run as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here. My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop] ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 14:31:52 2024 InstallationDate: Installed on 2024-03-02 (24 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/usr/bin/zsh - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/usr/bin/zsh + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: There is a check in the copy worker that looks to see if the user running the copy worker owns the files it is trying to copy ``` if (!g_file_query_exists (src, NULL) || !file_is_ours (src)) exit (EXIT_SUCCESS); ``` From all my testing, the copy worker will always run as a newly created user, and thus not own the file in /run/gnome-initial-setup and always exit here. My workaround in provd is to update the ownership of the file in /run/gnome-initial-setup to the newly created user before booting into their session, allowing this check to pass. + + Without this workaround, several settings applied in the gnome-initial- + setup new user flow (mainly a11y) are not persisted to the new user + after the gis process concludes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-initial-setup 45.0-1ubuntu3 [modified: usr/share/applications/gnome-initial-setup.desktop] ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 14:31:52 2024 InstallationDate: Installed on 2024-03-02 (24 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu.
[Desktop-packages] [Bug 2059100] [NEW] Voice is lost after sleep
Public bug reported: This problem is when I use kernel 6.5 and I do not have this problem with kernel 6.2 When the laptop wakes up from sleep, it has no voice. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 13:28:37 2024 InstallationDate: Installed on 2023-07-23 (246 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 2.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0CW9KM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/18/2023:br2.9:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0CW9KM:rvrA00:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2059100 Title: Voice is lost after sleep Status in pulseaudio package in Ubuntu: New Bug description: This problem is when I use kernel 6.5 and I do not have this problem with kernel 6.2 When the laptop wakes up from sleep, it has no voice. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4c', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 13:28:37 2024 InstallationDate: Installed on 2023-07-23 (246 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 2.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0CW9KM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd12/18/2023:br2.9:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0CW9KM:rvrA00:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2059100/+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 2058866] Re: proposed-migration for cups-browsed 2.0.0-0ubuntu8
Thanks! Since this issue was seen only with the package in -proposed, I'm closing this bug. There are other unrelated test failures now blocking the build on armhf. I will open a separate bug for these. ** Changed in: cups-browsed (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: apparmor (Ubuntu) Status: New => Invalid ** Also affects: privoxy (Ubuntu) Importance: Undecided Status: New ** Changed in: privoxy (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: Invalid Status in cups-browsed package in Ubuntu: Fix Released Status in privoxy package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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 2059089] [NEW] proposed-migration for cups-browsed 2.0.0-0ubuntu9
Public bug reported: cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed with test failures on armhf. ** Affects: cups-browsed (Ubuntu) Importance: Undecided Status: New ** Tags: time-t update-excuse ** Tags added: time-t ** Description changed: - cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed. + cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed with test failures on + armhf. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2059089 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu9 Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu9 is stuck in -proposed with test failures on armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2059089/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
into the same trouble I just did...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
> Many thanks for raising this way before Plasma 6 is released to
Ubuntu, this way we can assure this bug is gone by the time Plasma 6
becomes officially supported in Ubuntu.
This was my intend. :)
I'm using KDE neon, which is an extension of Ubuntu 22.04 providing the
most recent KDE applications.
* https://neon.kde.org/
Obviously, this comes with some breakage from time to time which I
normally report against neon itself, but this time it looked more
sensible to report it here against the Chromium snap.
A fix will already help all KDE neon users which use Chromium and use
KDE wallet to store Chromium Password wallet's master password.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2058840
Title:
Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed
Status in chromium-browser package in Ubuntu:
New
Bug description:
Ubuntu 22.04 LTS Jammy x64
I hope this is the correct package to assign this request to:
In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
decrypt its password store.
This makes all stored passwords unavailable as soon as the system is
upgraded from Plasma 5 to Plasma 6.
Chromium writes the following error messages to the console:
-
[5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="isEnabled" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting
kwalletd6 (isEnabled)
[5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KLauncher.start_service_by_desktop_name: object_path=
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.kde.klauncher was not provided by any .service files
[5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting
klauncher to start kwalletd6
[5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call
method: org.kde.KWallet.close: object_path= /modules/kwalletd6:
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this
sender from sending this message to this recipient; type="method_call",
sender=":1.113" (uid=1000 pid=5362
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom"
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet"
member="close" error name="(unset)" requested_reply="0"
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6
--pam-login 13 14 " label="unconfined")
[5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting
kwalletd6 (close)
-
Followed by hundreds of messages as the following:
-
ERROR:login_database.cc(1046) Password decryption failed, encryption_result
is 2
-
It appears to work to "just" whitelist the new kwalletd module name in
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
/var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)
followed by
$ systemctl restart apparmor
$ systemctl restart snapd.apparmor
$ systemctl restart apparmor
(Not sure if both of these are necessary, and if so, in what order.)
and completely restart Chromium.
The new KWallet section looks as follows - I only added the ",6" to
the patterns:
-
# KWallet's client API is still in use in KDE/Plasma. It's DBus API relies
upon
# member data for access to its 'folders' and 'entries' and it therefore does
# not allow for application isolation via AppArmor. For details, see:
# - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
#
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.freedesktop.DBus.*
peer=(label=unconfined),
dbus (receive, send)
bus=session
path=/modules/kwalletd{,5,6}
interface=org.kde.KWallet
peer=(label=unconfined),
-
I hope that at least this report may be found by other people running
[Desktop-packages] [Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Sorry I only just figured out that comment #17 is about mantic, not jammy. https://ubuntu-archive-team.ubuntu.com/proposed- migration/mantic/update_excuses.html#mutter And the Debian fix I mentioned in comment #18 is actually in 44.8-1 onward *and* 45.2-2 onward. So mantic would get the fix for fullscreen- maximize.test automatically if it was to receive an update to 45.3 or even if it was rebased on 45.2-2. -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 1905186] Re: dock and top bar flashing non-stop at fullscreen in Xorg sessions
In progress upstream: https://github.com/micheleg/dash-to-dock/pull/2149 Also I have deleted tasks for the now unsupported deb versions of some extensions. ** No longer affects: gnome-shell-extension-dashtodock (Ubuntu) ** No longer affects: gnome-shell-extension-autohidetopbar (Ubuntu) ** No longer affects: gnome-shell-extension-dash-to-panel (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905186 Title: dock and top bar flashing non-stop at fullscreen in Xorg sessions Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.1 LTS This problem affects all extensions that alter the dock and top bar. Including the standard extension "Ubuntu dock". All extensions are duly updated to the present date. I hoped that when entering full screen it would be possible to bring the dock and the top bar when placing the mouse over the respective corners. And in fact it is partially possible. However, both are flashing, making it impossible to use them in full screen. They blink very fast and you need to click on the correct timing to open the programs on the dock, for example. It is possible to click, but it is as if they were triggered several times, as if I were placing and removing the mouse from the corner very quickly. I enter the program. Everything is OK. The problem arises when I use the fullscreen. Sometimes the docks and the top bar work perfectly for a while, and then they start flashing. - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 14:07:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-24 (121 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-07-25T15:59:00.336431 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1905186/+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 2057842] Re: FFe: [MIR] freedp2 -> freerdp3 in main
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2057842
Title:
FFe: [MIR] freedp2 -> freerdp3 in main
Status in freerdp3 package in Ubuntu:
Fix Released
Status in gnome-remote-desktop package in Ubuntu:
Fix Committed
Status in remmina package in Ubuntu:
Fix Committed
Bug description:
Feature Freeze Exception Request
--
There are only 2 packages in Ubuntu main that use freerdp2: remmina and
gnome-remote-desktop. It is requested to switch both to freerdp3. Therefore
only one version of freerdp will be in main. freerdp2 will be demoted to
universe since many universe packages use it and are not prepared to switch to
freerdp3.
This also requests updating gnome-control-center to fully enable the
features of gnome-remote-desktop 46.
Impact
--
A headline feature of GNOME 46 is support as a Remote Desktop server without
requiring someone to already be logged in locally ("headless" mode). This
feature requires gnome-remote-desktop 46. gnome-remote-desktop 46 requires
freerdp3.
Impact if this does not happen
--
- We would need to patch gnome-control-center to use the older Remote Desktop
panel (or at least hide the new tab for Remote Login)
- We would need to keep using gnome-remote-desktop 45 instead of 46. The
gnome-remote-desktop upstream maintainers would be unhappy with this decision.
gnome-remote-desktop 45 was tested against Mutter 45. Changes in Mutter 46 may
require changes in gnome-remote-desktop for things to work well although a
simple test showed that basic remote desktop seems to work ok with the
mismatch. (See comment #1 from upstream developer.)
Why this did not land sooner
---
It required the packaging of a new source package freerdp3. And we had to do
this sooner than Debian. Sorry too many things to do before Feature Freeze and
this did not make it.
Affected Packages
-
- gnome-remote-desktop 45 -> 46
- gnome-control-center (to update the Remote Desktop settings page)
- remmina 1.4.34 -> 1.4.35 and swap build-depends. Remmina 1.4.34 did not
work with freerdp 3.3 in my testing
- gnome-connections (build-dependency swap): Not required by other changes
and not in Main but makes sense to switch it also
Affected Flavors
Only Ubuntu Desktop and Edubuntu ships gdm3, gnome-control-center,
gnome-remote-desktop. (Cinnamon 23.04 and daily 23.10 also ships
gnome-control-center but this appears to be a bug since they ship
cinnamon-control-center and is likely already fixed in noble-proposed)
Remmina is included in Ubuntu Desktop, Cinnamon, Kylin, and Unity.
gnome-connections has no reverse dependencies or recommends.
Upstream Changes
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/blob/46.rc/NEWS
https://gitlab.com/Remmina/Remmina/-/blob/rel/v1.4.35/CHANGELOG.md
gnome-control-center 46~beta was already in Ubuntu 24.04 LTS before Feature
Freeze. It will be updated to 46.0. The relevant part here is whether we use
the 46~beta version of the Remote Desktop page or the 46.0 version.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/46.rc/NEWS
Build Logs
--
I have backported GNOME Shell 46 RC and GTK4 4.13 to the Ubuntu Desktop PPA.
The PPA currently has noble-proposed disabled so that it is easily possible to
try this set of packages without dealing with the incomplete 32-bit time
transition in noble-proposed. In addition, the PPA has the affected packages
from this FFe.
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages
Testing Done
---
1. From Ubuntu 23.10 client using Remmina, I was successfully able to connect
to Ubuntu 24.04 LTS host using GNOME Shell 46 RC and GNOME Remote Desktop 46
RC. Remote control worked.
2. From Ubuntu 24.04 LTS client with Remmina 1.4.35 built with
freerdp3, I was able to connect to Ubuntu 23.10 host. Remote control
worked.
3. From Ubuntu 24.04 LTS client with GNOME Connections 46 RC built
with freerdp3, I was able to connect to Ubuntu 23.10 host. Remote
control worked.
4. I added a new Remote Login test case to
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop and
verified that remote login worked. Notably, enabling this changes the
port for the older service, now called "Desktop Sharing" to 3390.
Since 3389 is the default port, users would then need to manually
specific port 3390 for Desktop Sharing in their remote connection app
(Remmina, GNOME Connections, etc.).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp3/+bug/2057842/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 2059076] [NEW] proposed-migration for gnome-remote-desktop 46~rc-0ubuntu2
Public bug reported: gnome-remote-desktop 46~rc-0ubuntu2 is built in -proposed but not on armhf. This will not block migration because armhf binaries are being removed from the release pocket, but unless addressed will regress armhf availability of this package in 24.04 LTS. ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: time-t update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2059076 Title: proposed-migration for gnome-remote-desktop 46~rc-0ubuntu2 Status in gnome-remote-desktop package in Ubuntu: New Bug description: gnome-remote-desktop 46~rc-0ubuntu2 is built in -proposed but not on armhf. This will not block migration because armhf binaries are being removed from the release pocket, but unless addressed will regress armhf availability of this package in 24.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2059076/+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 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed
** Changed in: network-manager Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1997553 Title: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Triaged Bug description: We rely on network-manager dispatcher scripts on our desktop and laptop computers. The dispatcher scripts are used to update DNS records with nsupdate when the dhcp lease is renewed. With jammy this is not working anymore. It seems that dispatcher scripts are run only when the interface comes up (with action 'up') and with the initial dhcp lease (with action 'dhcp4-change'), but when the lease is renewed, the dispatcher scripts are not run with any action. The only action the dispatcher scripts are run regularly with is 'connectivity-change', which seems to occur twice in a row every few hours. I have made a simple script to log how the dispatcher scripts are run: /etc/NetworkManager/dispatcher.d/99-test: #!/bin/bash PATH='/bin:/sbin:/usr/bin:/usr/sbin' echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log This script proves that action 'dhcp4-change' only occurs when I manually restart NetworkManager.service or unplug and replug the ethernet cable. network-manager version: 1.36.6-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1997553/+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 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C
Seems like the bug is back. It pops up occasionally (one error line every ~2 hours) on Linux 6.5.0-14, 6.6.0-14 and 6.8.0-20. Appears on both Jammy: Xorg (Mate) and Mantic: Xorg/Wayland (Mate/KDE). Default kernel cmdline. On Xorg the graphics is fine, but on Wayland it can a bit "flickery" at times but it's barely noticeable. Machine is XPS13 9350. ``` kernel: i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=582395 end=582396) time 9696 us, min 1073, max 1079, scanline start 733, end 268 ``` Please let me know if there is any additional information you need. P.S. Not necessarily related, but I also see: ``` kernel: workqueue: engine_retire [i915] hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND among others like: kernel: [130525.417342] workqueue: set_brightness_delayed hogged CPU for >1us 32 times, consider switching to WQ_UNBOUND kernel: [153420.843667] workqueue: smp_call_on_cpu_callback hogged CPU for >1us 2048 times, consider switching to WQ_UNBOUND kernel: [168386.280902] workqueue: delayed_fput hogged CPU for >1us 512 times, consider switching to WQ_UNBOUND kernel: [192582.937788] workqueue: intel_atomic_cleanup_work [i915] hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND ``` But that might be the scheduler getting confused on this aging and overloaded machine... -- 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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb
