[Touch-packages] [Bug 2052492] Re: Pairing: passcode dialogue disappears in <1 second
FIX (Maybe?) I put the keyboard aside for (about) a week. During this time the laptop when through a usual 'apt update/apt upgrade' process and reboot. When I tried to subsequently re-pair the keyboard, the 'passcode dialog' stayed visible, and the keyboard paired. Considerations: - This laptop is not the fastest (i5-3210M CPU @ 2.50GHz), and this time I waited after entering the passcode (and pressinbg enter) for the pairing to be successful. This took maybe 5-10 sec. I may not have been as patient in the first case and quit the pairing dialog to try again. - Deleting the detected entry for the keyboard in the Bluetooth list and getting it to be detected again, did not help. ** Description changed: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop- up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- + Bluetooth Device + + Logitech - Logi POP Keys (see link below) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- Bluetooth Device Logitech - Logi POP Keys (see link below) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2052492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052494] [NEW] There is an error in the recording of timezones for some cities
Public bug reported: There is an error in the recording of timezones for some cities. Cities such as Zhanjiang are located in Guangdong Province, which is in the East 8 time zone, which is in the Asia/Shanghai time zone.but in the file timezonemap/src/data/cities15000.txt the city is recorded as being in East 6, the Asia/Urumqi time zone. Here is the modifications： == timezonemap/src/data/cities15000.txt 3054c3054 < 1784990 Zhanjiang Zhanjiang Chan-chiang,Chan-chiang-shih,Chankiang,Chzhan'czjan,Fort Bayard,Hsi-ying,Kwangchow,Kwangchowan,Kwangchowwan,Tram Giang,Trạm Giang,Tsamkong,ZHA,Zhanjiang,Zhanjiang Shi,zhan jiang,zhan jiang shi,Чжаньцзян,جاڭجياڭ شەھىرى,湛江,湛江市21.28145110.34271 P PPLA2 CN 30 637790 29 Asia/Shanghai 2012-01-18 --- > 1784990 Zhanjiang Zhanjiang > Chan-chiang,Chan-chiang-shih,Chankiang,Chzhan'czjan,Fort > Bayard,Hsi-ying,Kwangchow,Kwangchowan,Kwangchowwan,Tram Giang,Trạm > Giang,Tsamkong,ZHA,Zhanjiang,Zhanjiang Shi,zhan jiang,zhan jiang > shi,Чжаньцзян,جاڭجياڭ شەھىرى,湛江,湛江市21.28145110.34271 P > PPLA2 CN 30 637790 > 29 Asia/Urumqi 2012-01-18 3108c3108 < 1787837 Xucheng Xucheng Hsu-wen,Hsu-wen-hsien,Hsü-wen,Hsü-wen-hsien,Suwen,Suwenyun,Tsuimen,Xucheng,Xucheng Jiedao,Xucheng Zhen,Xuwen,xu cheng,xu cheng jie dao,xu cheng zhen,徐城,徐城街道,徐城镇 20.32917110.16712 P PPLA3 CN 30 83267 75 Asia/Shanghai 2013-10-05 --- > 1787837 Xucheng Xucheng > Hsu-wen,Hsu-wen-hsien,Hsü-wen,Hsü-wen-hsien,Suwen,Suwenyun,Tsuimen,Xucheng,Xucheng > Jiedao,Xucheng Zhen,Xuwen,xu cheng,xu cheng jie dao,xu cheng > zhen,徐城,徐城街道,徐城镇20.32917110.16712 P PPLA3 CN > 30 83267 75 Asia/Urumqi > 2013-10-05 3318c3318 < 1800829 Wuchuan Wuchuan Hai-lu,Mei-lu-shih,Mei-mao,Meilu,Muiluk,Wuchuan,wu chuan,吴川 21.45713 110.76591 P PPL CN 30 104168 7 Asia/Shanghai 2012-01-18 --- > 1800829 Wuchuan Wuchuan > Hai-lu,Mei-lu-shih,Mei-mao,Meilu,Muiluk,Wuchuan,wu chuan,吴川 21.45713 > 110.76591 P PPL CN 30 > 104168 7 Asia/Urumqi 2012-01-18 3364c3364 < 1804120 Lianjiang Lianjiang Lei-pei,Liancheng,Lianjiang,Lien-chiang,Lien-chiang-hsien,Limkong,Limkong-hsien,Lunkong,Shih-ch'eng,Shih-ch’eng,lian jiang,廉江 21.64673110.28172 P PPL CN 30 100341 46 Asia/Shanghai 2012-01-18 --- > 1804120 Lianjiang Lianjiang > Lei-pei,Liancheng,Lianjiang,Lien-chiang,Lien-chiang-hsien,Limkong,Limkong-hsien,Lunkong,Shih-ch'eng,Shih-ch’eng,lian > jiang,廉江 21.64673110.28172 P PPL CN > 30 100341 46 Asia/Urumqi > 2012-01-18 3432c3432 < 1806960 Huazhou Huazhou Fachow,Fahsien,Fu-ch'eng-chen,Fu-ch’eng-chen,Hau-hsien,Hua,Hua-chou,Hua-hsien,Huazhou 21.6110.58333 P PPL CN 30 91701 35 Asia/Shanghai 2012-01-18 --- > 1806960 Huazhou Huazhou > Fachow,Fahsien,Fu-ch'eng-chen,Fu-ch’eng-chen,Hau-hsien,Hua,Hua-chou,Hua-hsien,Huazhou >21.6110.58333 P PPL CN 30 > 91701 35 Asia/Urumqi 2012-01-18 3484c3484 < 1810295 Gaozhou Gaozhou Gaozhou,Kao-chou,Kaochow,Kochow,Kochowfu,Mao-ming,Mao-ming-hsien,Mowming,gao zhou,高州21.93924110.84607 P PPL CN 30 166069 57 Asia/Shanghai 2012-01-18 --- > 1810295 Gaozhou Gaozhou > Gaozhou,Kao-chou,Kaochow,Kochow,Kochowfu,Mao-ming,Mao-ming-hsien,Mowming,gao > zhou,高州21.93924110.84607 P PPL CN 30 > 166069 57 Asia/Urumqi > 2012-01-18 3507c3507 < 1812057 Xinyi Xinyi Dongzhen,Hsin-i,Tung-chen,Tung-chen-chen,Tung-chen-hsu,Tung-chen-hsü,Xinyi,xin yi,信宜22.37303110.94746 P PPL CN 30 98259 89 Asia/Shanghai 2012-01-18 --- > 1812057 Xinyi Xinyi > Dongzhen,Hsin-i,Tung-chen,Tung-chen-chen,Tung-chen-hsu,Tung-chen-hsü,Xinyi,xin > yi,信宜22.37303110.94746 P PPL CN 30 > 98259 89 Asia/Urumqi 2012-01-18 3598c3598 < 1915223 Zhongshan
[Touch-packages] [Bug 2052492] Re: Pairing: passcode dialogue disappears in <1 second
I am seeing this bug in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop- up disappears very quickly (as described, <1sec). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2052492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052492] Re: Pairing: passcode dialogue disappears in <1 second
- This occurs on my daily use laptop which has been upgraded from 23.04 -> 23.10 - I have just tried to pair on another laptop with freshly installed 23.10 - The dialog displaying the pairing code persists and I can pair correctly with same keyboard (it can pair with 3 separate devices) - bluez 5.68-0ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2052492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052492] Re: Pairing: passcode dialogue disappears in <1 second
Related to https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/241000 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2052492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052492] [NEW] Pairing: passcode dialogue disappears in <1 second
Public bug reported: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop- up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Description changed: - UPDATE: I am creating this bug in case i comes back again. My Fix was to put the bluetooth keyboard + UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: - 1) There is something I messed that someone else can suggest; and - 2) it occurs for someone else. + 1) There is something I messed that someone else can suggest; and + 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop- up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2052492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052492] Re: Pairing: passcode dialogue disappears in <1 second
Some things that I have tried which didn't immediately fix the problem. Resetting the bluez package did NOT fix the problem. Removing the bluez package(s), removing /var/lib/bluetooth and re-installing. sudo apt remove --purge bluez rm -rf /var/lib/bluetooth sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto The bluetooth system needs to be started, and this empties the list of discovered bluetoothe devices, but the popup for the keyboard auth number still disappears quickly again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2052492 Title: Pairing: passcode dialogue disappears in <1 second Status in bluez package in Ubuntu: New Bug description: UPDATE: I am creating this bug in case it comes back again. My Fix was to put the bluetooth keyboard aside for a week (not use it), then reconnect after the laptop had been rebooted after an update and daily use. I will post the things that I tried, just in case: 1) There is something I messed that someone else can suggest; and 2) it occurs for someone else. I suspect that it will happen again at some stage. -- I am seeing this issue in Ubuntu 23.10. bluez 5.68-0ubuntu1.1 Hardware: Logi POP Keys https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec). System details - $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 - ii bluez 5.68-0ubuntu1.1amd64Bluetooth tools and daemons -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2052492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Note: snap now vendors apparmor so reinstalling/removing the system apparmor package with not affect snapd's use of apparmor. You can temporarily (for the boot) disable apparmor in the grub command line by adding apparmor=0 to the kernel parameters. >From the logs the following adjustments need to be done to snap policy, after fixing these new denials may be encountered. The firefox denial is weird, and I have to ask why is root trying to run firefox. The likely culprits are /snap/snapd/20671/usr/lib/snapd/snap-confine and snap.snapd-desktop-integration.snapd-desktop-integration. Can you try copying these profiles out of /var/lib/snapd/apparmor/profiles/ modifying them by putting flags=(complain) in the profile header, and then reloading them with sudo apparmor_parser -r profile.file. This will temporarily place these profiles in dev mode and if they are the source of the problem allow the graphics layer to come up. profile snap-update-ns.firefox /usr/local/share/ r, # owner root, fsuid root profile /snap/snapd/20671/usr/lib/snapd/snap-confine capability net_admin, capability perfmon, profile snap.snapd-desktop-integration.snapd-desktop-integration /etc/gnutls/config r, # owner root, fsuid 1000 /etc/gnutls/config r, # owner root, fsuid 1000 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Permissions problem wit LightDM? >>> mafoelffen@noble-mate-01:~$ sudo systemctl status lightdm --no-pager -l ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; preset: enabled) Active: active (running) since Mon 2024-02-05 21:24:19 PST; 3min 39s ago Docs: man:lightdm(1) Process: 6243 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 6246 (lightdm) Tasks: 6 (limit: 4559) Memory: 14.2M CPU: 99ms CGroup: /system.slice/lightdm.service ├─6246 /usr/sbin/lightdm └─6253 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Feb 05 21:24:19 noble-mate-01 systemd[1]: Starting lightdm.service - Light Display Manager... Feb 05 21:24:19 noble-mate-01 lightdm[6246]: Seat type 'xlocal' is deprecated, use 'type=local' instead Feb 05 21:24:19 noble-mate-01 systemd[1]: Started lightdm.service - Light Display Manager. Feb 05 21:24:19 noble-mate-01 lightdm[6262]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=112) by (uid=0) Feb 05 21:24:19 noble-mate-01 lightdm[6262]: gkr-pam: couldn't unlock the login keyring. Feb 05 21:24:19 noble-mate-01 lightdm[6262]: pam_env(lightdm-greeter:session): deprecated reading of user environment enabled >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Reinstalling lightdm and trying to start it manually, brings it right to the same failure point, where it hangs on a black screen. I think there is a problem with LightDM not displaying on this install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
** Attachment added: "_usr_lib_xorg_Xorg.0.crash" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+attachment/5744811/+files/_usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
If I reinstalled apparmor thorugh apt, then reinstalled snapd-desktop integration... Then gave it >>> startx >>> Then the desktop come up. But it will not boot to the Mate Desktop. Wait one. Reinstalled lightdm. Still boots to black screen. If you give it a nomodeset boot parameter, it boots to an init 3 console prompt(?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
That was the first boot. Machine was KVM VM: i9-138900K, 4GB RAM 25 GB vDisk, UEFI, SecureBoot off. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Had to collect report remotely to my workstation: ** Attachment added: "apport.apparmor.2jwsui89.apport" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+attachment/5744810/+files/apport.apparmor.2jwsui89.apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052489] [NEW] Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Public bug reported: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048092] Re: [low-priority SRU] Fix CVE-2022-0563 in source
The remaining autopkgtest failures are due to the following unrelated bugs: cmake-extras/armhf: bug 2052360 livecd-rootfs/amd64: bug 2045586 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2048092 Title: [low-priority SRU] Fix CVE-2022-0563 in source Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Jammy: Fix Committed Status in util-linux source package in Lunar: Fix Released Status in util-linux source package in Mantic: Fix Released Status in util-linux source package in Noble: Fix Released Bug description: [Impact] We did not fix this CVE in Ubuntu because we do not build the impacted binaries (we use --disable-chfn-chsh). However, some users are known to build their own binaries from this Ubuntu source and therefore could be impacted. [Test Plan] Since there is no impact to Ubuntu binaries, there is no functional change to verify. Regression testing using the existing build-time tests and autopkgtests should suffice. We should also verify that util-linux source builds fine w/ chfn and chsh enabled after applying this patch - otherwise it is really helping no one. [Where problems could occur] The upstream patch is clearly restricted to the chfn chsh binaries, which are not compiled by Ubuntu, so I don't see a risk there. I do see a risk that this is used as a precedent to fix other no-impact-to-Ubuntu security issues in other source - say, just to silence 3rd party security scanners. I do not intend to set such a precedent here, and suggest we consider them only on a case-by-case basis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2048092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052470] Re: Alt-backtick does not switch between the same application
Please check that this isn't being caused by local extensions. You can remove them by running: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the problem persists after that then please run: gnome-extensions list --enabled > extensions.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2052470 Title: Alt-backtick does not switch between the same application Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I use Alt+` it will switch to the first application in the list, rather than between different windows of the same application I am running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-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..65.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 525.147.05 Wed Oct 25 20:27:35 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 5 14:43:05 2024 DistUpgraded: 2022-08-26 00:48:24,846 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.147.05, 5.15.0-92-generic, x86_64: installed nvidia/525.147.05, 6.2.0-37-generic, x86_64: installed nvidia/525.147.05, 6.5.0-14-generic, x86_64: installed nvidia/525.147.05, 6.5.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [TITAN X] [10de:1b00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP102 [TITAN X] [10de:119a] InstallationDate: Installed on 2021-11-08 (819 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=bb6c7a01-5fb3-46e1-b488-ce8f4dbfa062 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-26 (528 days ago) dmi.bios.date: 03/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-A II 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.:bvr1004:bd03/19/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-AII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_KBLX: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 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.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/gnome-shell/+bug/2052470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052482] [NEW] Bad packet length 2424479189 Connection corrupted
Public bug reported: ssh-clent: uname -a :5.15.0-48-generic #54-Ubuntu ``` Ubuntu 22.04.3 LTS OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022 ``` ssh-server: ``` OracleLinux 8.9 OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021 ``` ``` userxxx@userxxx-H3C-X7-030s-0274:~$ ssh 192.168.xxx.xxx -vvv OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug2: resolve_canonicalize: hostname 192.168.xxx.xxx is address debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/userxxx/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/userxxx/.ssh/known_hosts2' debug3: ssh_connect_direct: entering debug1: Connecting to 192.168.xxx.xxx [192.168.xxx.xxx] port 22. debug3: set_sock_tos: set socket 3 IP_TOS 0x10 debug1: Connection established. debug1: identity file /home/userxxx/.ssh/id_rsa type 0 debug1: identity file /home/userxxx/.ssh/id_rsa-cert type -1 debug1: identity file /home/userxxx/.ssh/id_ecdsa type 2 debug1: identity file /home/userxxx/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/userxxx/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/userxxx/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/userxxx/.ssh/id_ed25519 type -1 debug1: identity file /home/userxxx/.ssh/id_ed25519-cert type -1 debug1: identity file /home/userxxx/.ssh/id_ed25519_sk type -1 debug1: identity file /home/userxxx/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/userxxx/.ssh/id_xmss type -1 debug1: identity file /home/userxxx/.ssh/id_xmss-cert type -1 debug1: identity file /home/userxxx/.ssh/id_dsa type -1 debug1: identity file /home/userxxx/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0 debug1: compat_banner: match: OpenSSH_8.0 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 192.168.xxx.xxx:22 as 'userxxx' debug3: record_hostkey: found key type ED25519 in file /home/userxxx/.ssh/known_hosts:20 debug3: load_hostkeys_file: loaded 1 keys from 192.168.xxx.xxx debug1: load_hostkeys: fopen /home/userxxx/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-...@openssh.com, using HostkeyAlgorithms verbatim debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,sntrup761x25519-sha...@openssh.com,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-...@openssh.com debug2: host key algorithms: ssh-ed25519-cert-...@openssh.com,ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,sk-ssh-ed25519-cert-...@openssh.com,sk-ecdsa-sha2-nistp256-cert-...@openssh.com,rsa-sha2-512-cert-...@openssh.com,rsa-sha2-256-cert-...@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25...@openssh.com,sk-ecdsa-sha2-nistp...@openssh.com,rsa-sha2-512,rsa-sha2-256 debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,z...@openssh.com,zlib debug2: compression stoc: none,z...@openssh.com,zlib debug2: languages ctos: debug2: languages stoc: debug2: first_kex_follows 0 debug2: reserved 0 debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1 debug2:
[Touch-packages] [Bug 2025169] Re: pasdsp LIB dir incorrect
** Changed in: pulseaudio (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2025169 Title: pasdsp LIB dir incorrect Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Debian: Fix Released Bug description: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052470] [NEW] Alt-backtick does not switch between the same application
Public bug reported: When I use Alt+` it will switch to the first application in the list, rather than between different windows of the same application I am running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-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..65.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 525.147.05 Wed Oct 25 20:27:35 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 5 14:43:05 2024 DistUpgraded: 2022-08-26 00:48:24,846 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.147.05, 5.15.0-92-generic, x86_64: installed nvidia/525.147.05, 6.2.0-37-generic, x86_64: installed nvidia/525.147.05, 6.5.0-14-generic, x86_64: installed nvidia/525.147.05, 6.5.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [TITAN X] [10de:1b00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP102 [TITAN X] [10de:119a] InstallationDate: Installed on 2021-11-08 (819 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=bb6c7a01-5fb3-46e1-b488-ce8f4dbfa062 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-08-26 (528 days ago) dmi.bios.date: 03/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-A II 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.:bvr1004:bd03/19/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-AII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_KBLX: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 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.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2052470 Title: Alt-backtick does not switch between the same application Status in xorg package in Ubuntu: New Bug description: When I use Alt+` it will switch to the first application in the list, rather than between different windows of the same application I am running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-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..65.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
[Touch-packages] [Bug 2004003] Re: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2004003 Title: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script Status in ifupdown package in Ubuntu: Confirmed Bug description: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2004003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004003] Re: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script
I've also encountered this bug in Ubuntu 22.04 LTS. I'd get an error in /etc/network/if-up.d/resolved unless I change 'return' to 'exit' in the affected line. After the change I'd no longer encounter an error. I have /bin/sh symlinked to bash as requirement to build some software. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2004003 Title: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script Status in ifupdown package in Ubuntu: Confirmed Bug description: Just found the following errors in "systemctl status networking" × networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2023-01-27 12:26:29 MSK; 3min 10s ago Docs: man:interfaces(5) Process: 3963 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Main PID: 3963 (code=exited, status=1/FAILURE) CPU: 147ms янв 27 12:26:29 gerbera systemd[1]: Starting Raise network interfaces... янв 27 12:26:29 gerbera ifup[3976]: /etc/network/if-up.d/resolved: line 12: mystatedir: command not found янв 27 12:26:29 gerbera ifup[3973]: /etc/network/if-up.d/resolved: line 20: return: can only `return' from a function or sourced script янв 27 12:26:29 gerbera ifup[3969]: run-parts: /etc/network/if-up.d/resolved exited with return code 2 янв 27 12:26:29 gerbera ifup[3963]: ifup: failed to bring up lo янв 27 12:26:29 gerbera systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE янв 27 12:26:29 gerbera systemd[1]: networking.service: Failed with result 'exit-code'. янв 27 12:26:29 gerbera systemd[1]: Failed to start Raise network interfaces. The error with mystatedir has been already reported as bug#1907878. However, patches there do not fix unexpected return statement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2004003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052297] Re: Please add opt.keybase.keybase profile
** Changed in: apparmor (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2052297
Title:
Please add opt.keybase.keybase profile
Status in apparmor package in Ubuntu:
Fix Committed
Bug description:
Like the other Chrome binaries, Keybase also needs a profile:
abi ,
/opt/keybase/Keybase flags=(unconfined) {
allow userns create,
}
Keybase is heavily used for security and boot engineering for cross-vendor
communication and broken without it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052297/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033892] Re: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled
$ git tag --contains 85c975df2c2 v9.1 v9.2 v9.3 v9.4 $ git tag --contains 92cb8427c53 v9.1 v9.2 v9.3 v9.4 $ Ubuntu 23.10 includes coreutils 9.1, 24.04 LTS will include coreutils 9.4. So this bug is fixed in the latest release of Ubuntu. ** Changed in: coreutils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2033892 Title: ls -l triggers mount of autofs shares when --ghost option is present or browse_mode is enabled Status in coreutils package in Ubuntu: Fix Released Status in coreutils package in Fedora: Fix Released Bug description: Release: 22.04.3 LTS coreutils 8.32-4.1ubuntu1 ls triggers unwanted mounts of autofs filesystems cause: coreutils 8.32.4.1ubuntu1 uses statx which not pass the AT_NO_AUTOMOUNT flag This bug is also known (and fixed) at Redhat https://bugzilla.redhat.com/show_bug.cgi?id=2044981 upstream commits: https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-177-g85c975df2c2 https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v9.0-178-g92cb8427c53 fedora commit https://src.fedoraproject.org/rpms/coreutils/c/d736cafa20f13eeb037a3950bdbb4b63dc39b7e3?branch=f35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052405] Re: Translation error in policykit-1 package
** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2052405 Title: Translation error in policykit-1 package Status in Ubuntu Translations: New Status in policykit-1 package in Ubuntu: New Bug description: policykit-1 package have translation error. https://translations.launchpad.net/ubuntu/jammy/+source/policykit-1/+pots/polkit-1/ko/+translate `$(program)'을(를) 관리자 권한으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) 관리자 권한으로 실행하려면 인증이 필요합니다. `$(program)'을(를) $(user) 계정으로 실행려면 인증이 필요합니다. -> `$(program)'을(를) $(user) 계정으로 실행하려면 인증이 필요합니다. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/2052405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052328] Re: openssh-client encounters MAC algo issue with EL8
I am closing this bug since the issue appears to be in Oracle Linux and is being tracked here: https://github.com/oracle/oracle-linux/issues/125 Thanks! ** Bug watch added: github.com/oracle/oracle-linux/issues #125 https://github.com/oracle/oracle-linux/issues/125 ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: Invalid Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
While the above MP is now merged, I still see additional potential races in the code. For example, anything calling mount_partition() for the first partition, and also maybe bug 2030771. I don't see a good way to solve that w/o `udevadm lock` because these functions don't currently know what the full block device - and I don't think we want to implement that logic ourselves. I suggest we move from flock to `udevadm lock` once it is available in noble. If that proves to be stable, then perhaps we consider backporting that to jammy's systemd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052328] Re: openssh-client encounters MAC algo issue with EL8
Thank you Marc and ibauto. I'll try to investigate/report on the Oracle Linux 8 side. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: New Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052328] Re: openssh-client encounters MAC algo issue with EL8
I believe this issue is caused by a bad backport in Oracle's 8.0p1-19.el8_9.2 package. I think their fix for CVE-2023-48795 isn't properly adding kex-strict-s-...@openssh.com to their KEX. Downgrading the Ubuntu package works around the problem as that prevents the client from offering kex-strict-c-...@openssh.com. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-48795 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: New Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052328] Re: openssh-client encounters MAC algo issue with EL8
OK, I have managed to locate the Oracle binary packages for 8.0p1-19.el8_9.2 and can confirm the issue. This is curious as the same packages from RockyLinux appear to work. I will attempt to investigate the differences. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: New Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950828] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear().
This is not fixed. See bug #2052422. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1950828 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear(). Status in ibus package in Ubuntu: Fix Released Bug description: Bug report generated after logging in. Nothing other then the log in was done. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-2build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 15:58:02 2021 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2021-10-27 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211025) ProcCmdline: ibus-daemon --panel disable ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1950828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1950828] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear().
** Changed in: ibus (Ubuntu) Assignee: Marcos Casquero (mcasquero) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1950828 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear(). Status in ibus package in Ubuntu: Fix Released Bug description: Bug report generated after logging in. Nothing other then the log in was done. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-2build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 15:58:02 2021 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2021-10-27 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211025) ProcCmdline: ibus-daemon --panel disable ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1950828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052328] Re: openssh-client encounters MAC algo issue with EL8
The Oracle Linux I'm running is the v8 developer preview, as that is the only freely downloadable version. I couldn't reproduce the issue with openssh-server-8.0p1-17.el8.x86_64. Since I can't get newer packages from Oracle with this version, I installed openssh, openssh-askpass, openssh-client and openssh-server 8.0p1-19.el8_9.2 from RockyLinux into the Oracle install, and I still can't reproduce the issue. Could someone perhaps email me the 4 Oracle binary rpms for the packages listed above so I can try them? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: New Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052328] Re: openssh-client encounters MAC algo issue with EL8
We are having the same with OL8 8.9 Openssh used om OL8 = 8.0p1-19.el8_9.2 Ubuntu 18.04, 20.04 and 22.04 who update to are having a problem We downgraded our versions temporary to 18.04: openssh-server=1:7.6p1-4ubuntu0.7 20.04: openssh-server=1:8.2p1-4 22.04: openssh-server=1:8.9p1-3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2052328 Title: openssh-client encounters MAC algo issue with EL8 Status in openssh package in Ubuntu: New Bug description: Ubuntu 22.04 system connecting to an Oracle Linux v8 host. The following error occurs regardless of the the MACs specified (or not) in sshd_config: Corrupted MAC on input. ssh_dispatch_run_fatal: Connection to XX.XX.XX.XX port 22: message authentication code incorrect Presumably, this may happen on any RHEL v8 variant. Note that connecting to Enterprise Linux v7 work as well as other Ubuntu hosts. Downgrading to previous version of openssh-client fixes issue. apt install openssh-client=1:8.9p1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2052328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Legion Slim 7 16IRH8 quirk added with this commit: https://github.com/torvalds/linux/commit/99af5b11c57d33c32d761797f6308b40936c22ed This is in 6.7.1+. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to Jacob Garby from comment #816) > (In reply to Lukas from comment #814) > > (In reply to Jacob Garby from comment #813) > > > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of > nowhere, > > > the speaker started working. I have no idea how -- I did not change > > anything > > > manually. I suspect it's a new kernel version that did it. > > > > > > I'm on Arch Linux, and I can't remember which kernel version I have > > > installed (but I can update when I get home later today). > > > > > > Anyway, good news! > > > > Amazing > > > > I would like to reproduce this. You can find out your current kernel > version > > with the command "uname -r". The installed sound packages/libs would also > be > > interesting. What I know of would be to look at the alsa version. > > Someone else surely has more information on what to specificly look for and > > how. > > Okay, so my kernel version is 6.7.2-arch1-1 > > These are some (maybe all) of the audio related packages I have installed: > kpipewire 5.27.10-1 > libpipewire 1:1.0.1-2 > pipewire 1:1.0.1-2 > pipewire-alsa 1:1.0.1-2 > pipewire-audio 1:1.0.1-2 > pipewire-jack 1:1.0.1-2 > pipewire-pulse 1:1.0.1-2 > libpulse 17.0-3 > pipewire-pulse 1:1.0.1-2 > projectm-pulseaudio 3.1.12-4 > > But I can verify that my speaker did also work _before_ I switched from > Pulseaudio to Pipewire, seems both should work. > > The result of running alsa-info is here: > http://alsa-project.org/db/?f=07a1fdaf34a424adc27dbb6be3f417995df6994f > > Good luck! atm i did not get it to work. i habe all the same packages or newer installed. hoping newer verions did not brick it again this means it would have to be the kernel. fedora 39 stabe only gets access to 6.6.13. tests for 6.7 are beeing done. i even tired to switch to pulse and back. no changes. will provide mor info when new kernel is here. maybe someone can provide info on weather fedora and arch kernel are vastly different as yours specificly says arch in the version. mine does not -- You received this bug notification because you are a member of Ubuntu Touch seeded 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:
[Touch-packages] [Bug 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
That sounds even more like a RAM issue (that it stopped occurring with the same kernel and software version). Perhaps when you switched away from Wayland, your graphics card is now used less heavily, and when the GPU was used more, the RAM got hotter or got minimally less power and therefore had issues, or something. (This is something people have indeed seen, so…) If you can trigger it reliably again, the changes would indeed be interesting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052422] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear()
*** This bug is a duplicate of bug 1950828 *** https://bugs.launchpad.net/bugs/1950828 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1950828, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2052422/+attachment/5744648/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2052422/+attachment/5744650/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2052422/+attachment/5744653/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2052422/+attachment/5744654/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2052422/+attachment/5744655/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2052422/+attachment/5744656/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2052422/+attachment/5744657/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1950828 ibus-daemon crashed with SIGABRT in g_mutex_clear(). ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2052422 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() Status in ibus package in Ubuntu: New Bug description: This happened about 15 seconds after logging in, and after launching 5 applications (Firefox, Files, Rhythmbox, Terminal and Thunderbird) in quick succession. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.26-4 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 4 21:31:30 2024 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2023-09-23 (134 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230923) ProcCmdline: ibus-daemon --panel disable --xim ProcEnviron: LANG=en_US.UTF-8 Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2023-12-25T21:34:30.416006 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2052422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: plymouth (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
