[Touch-packages] [Bug 2047802] [NEW] [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Headphone not used when connected during boot
Public bug reported: When the headphone is connected before the computer is booted the sound is played on the speakers and not on the headphone. When I remove the headphone and insert it back, the sound then switches correctly to the headphone. => This seems to be an boot / initialization issue, because generally the hardware does work $ lsb_release -rd Description:Ubuntu 22.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cm 2246 F pulseaudio /dev/snd/controlC1: cm 2246 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jan 2 08:04:24 2024 InstallationDate: Installed on 2023-08-26 (128 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0342YC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd11/13/2023:br1.8:efr1.6:svnDellInc.:pnPrecision7780:pvr:rvnDellInc.:rn0342YC:rvrA00:cvnDellInc.:ct10:cvr:sku0C42: dmi.product.family: Precision dmi.product.name: Precision 7780 dmi.product.sku: 0C42 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kernel-sound ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2047802 Title: [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Headphone not used when connected during boot Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When the headphone is connected before the computer is booted the sound is played on the speakers and not on the headphone. When I remove the headphone and insert it back, the sound then switches correctly to the headphone. => This seems to be an boot / initialization issue, because generally the hardware does work $ lsb_release -rd Description:Ubuntu 22.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cm 2246 F pulseaudio /dev/snd/controlC1: cm 2246 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jan 2 08:04:24 2024 InstallationDate: Installed on 2023-08-26 (128 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Precision 7780, Realtek ALC289, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2023 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0342YC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd11/13/2023:br1.8:efr1.6:svnDellInc.:pnPrecision7780:pvr:rvnDellInc.:rn0342YC:rvrA00:cvnDellInc.:ct10:cvr:sku0C42: dmi.product.family: Precision dmi.product.name: Precision 7780 dmi.product.sku: 0C42 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Hi everyone, I've marked the bug "affects me" as I have three users with non- functioning email. Would be great to get it working again for them, is there anyone this bug can be assigned to? many thanks Chris -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Can confirm that 3.40-1 version on flathub successfully fixes the problem. Many thanks https://flathub.org/apps/details/org.gnome.Evolution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1990689] Re: Cannot connect to Google account after upgrading to 22.04 LTS
Problem identified today : the folder ~/.local/share/webkitgtk is owned by root, with no permissions granted to other users. I changed the permissions to RW for other users, and I am now able to log in my google accounts ! Chris -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990689 Title: Cannot connect to Google account after upgrading to 22.04 LTS Status in gnome-online-accounts package in Ubuntu: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS, my Google accounts were disconnected. In the "Parameters/Online accounts" window, a double-click on each Google account opens a window indicating "authentication data expired. Please login to use this account". A click on the "Login" button opens a blank window, the only thing I can do is closing the window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 23 21:00:36 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2021-12-29 (268 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to jammy on 2022-09-11 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990689/+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 1654448] Re: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss
Hi Kai-Heng Feng, I experience a hissing noise on Ubuntu Ubuntu 18.04.2 LTS with Dell XPS 9370. Is there some patch I can apply to prevent this from happening? The hissing begins as soon as I plug headphones or speakers in and it goes away when I mute the system. -- 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/1654448 Title: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
Sure, Daniel, Kai-Heng. Please let me know what information you would like added to bug 1809856 for the 9370. FYI, the fix amixer -c 0 set 'Headphone Mic Boost',0 1 does not work on my laptop. -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
Sorry for the slow reply! See attached. ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+attachment/5244176/+files/allpackages.txt -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: Incomplete Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
Thanks Daniel for the suggestion, I'll try it. The audio issue doesnt always happen and I can't spot exactly what the triggers are, this morning 3 sessions are all working fine. any suggestion for what to do if it occurs again? 'kill all pulseaudio' doesnt help, neither does asking it to restart. I wonder if the bug is actually elsewhere, as the other issue i see is when plugging in a usb drive - another session will try to mount it, but fail to get access permission and a window pops up asking for admin login/pwd. that happens in the background session, the front session just shows a window saying failed to mount. Coincidence? Ive seen that bug before with ubuntu and mint going back to distros built on 16.04LTS, but still see it on occasion today. -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: New Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
Understood. I wont have daemonize=yes set, I will wait until the bug next occurs. Is there anything i can do run to troubleshoot further? -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: New Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
thats actually really useful information. the Arch link in particular. think i am happy to have my family members able to change volume etc, but not sure how to set up a systemd service. think i will just log everyone out when the bug happens, at least starting a new session gets the sound working again. -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: Triaged Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
I was reading more about pulseaudio and saw this on one of the Arch pages: https://wiki.archlinux.org/index.php/PulseAudio#Configuration_files "PulseAudio uses udev and logind to give access dynamically to the currently "active" user" could it be this which is not happening correctly? I started looking at udev and logind documentation and dont know where to start. The previous line quoted above, was about not needing to have a user being member of the "audio" group. Thought I would check, and strange! my account is the only one NOT in the audio group. Ive added my user in and will report back if that fixes it. (my user was the default admin one created on ubuntu install). -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: Triaged Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1814964] Re: No audio when logging in as second user. Only dummy audio device seen
ah, sadly not. added my user to audio group, logged in/out and still dont get sound (my wife's session is running in the background) I'll try a reboot and see if that works. -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: Triaged Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814964/+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 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
as per request this is my output for $dpkg -l hplip-data Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii hplip-data 3.17.10+repa all HP Linux Printing and Imaging - d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
I have the same issue. Running Linux Mint with latest kernel. Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It takes me disabling bluetooth, deleting the profile, re-enabling bluetooth, and putting the mouse back in pairing mode to fix. Only began happening after updating from Linux Mint 19 from Linux Mint 18.3 (I assume due to the Bluez version) dmesg: [ 9094.174854] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9113.487898] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9129.243872] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9145.487806] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9155.351840] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9171.601996] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9187.474873] Bluetooth: hci0: last event is not cmd complete (0x0f) [ 9193.843245] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 9193.843255] Bluetooth: HIDP socket layer initialized [ 9194.686585] hid-generic 0005:046D:B016.0002: unknown main item tag 0x0 [ 9194.686700] input: Bluetooth Mouse M336/M337/M535 Mouse as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input27 [ 9194.687692] input: Bluetooth Mouse M336/M337/M535 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input28 [ 9194.687919] input: Bluetooth Mouse M336/M337/M535 Keyboard as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input31 [ 9194.688328] hid-generic 0005:046D:B016.0002: input,hidraw1: BLUETOOTH HID v12.03 Mouse [Bluetooth Mouse M336/M337/M535] on a4:34:d9:e0:9c:d1 -- 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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
[Touch-packages] [Bug 1845998] [NEW] No audio from Dell Lattitude E5530 - looks like everything should be working fine, but no sound.
Public bug reported: Release: Ubunto 18.04.3 LTS Expected Behaviour: Sound to come out of the speakers Actual Behaviour: No sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Sep 30 17:18:10 2019 InstallationDate: Installed on 2019-09-11 (18 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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/1845998 Title: No audio from Dell Lattitude E5530 - looks like everything should be working fine, but no sound. Status in alsa-driver package in Ubuntu: New Bug description: Release: Ubunto 18.04.3 LTS Expected Behaviour: Sound to come out of the speakers Actual Behaviour: No sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Sep 30 17:18:10 2019 InstallationDate: Installed on 2019-09-11 (18 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1845998/+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 1845998] Re: No audio from Dell Lattitude E5530 - looks like everything should be working fine, but no sound.
Don't know how to remove the bug - but it fixed itself after a reboot :shrug: ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1845998 Title: No audio from Dell Lattitude E5530 - looks like everything should be working fine, but no sound. Status in alsa-driver package in Ubuntu: Invalid Bug description: Release: Ubunto 18.04.3 LTS Expected Behaviour: Sound to come out of the speakers Actual Behaviour: No sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Sep 30 17:18:10 2019 InstallationDate: Installed on 2019-09-11 (18 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1845998/+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 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop
*** This bug is a duplicate of bug 1778946 *** https://bugs.launchpad.net/bugs/1778946 This is happening for me as well. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic -- 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/1797415 Title: DNS stops working when disconnecting PPTP VPN on desktop Status in systemd package in Ubuntu: Confirmed Bug description: On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to my server. Everything connected and worked as it should. When I disconnect the VPN, DNS resolution stops working. Looking at "systemd-resolve --status" shows that the correct DNS server is listed for the interface when the connection is torn down, and I can ping it. Doing a nslookup setting the server to the IP address shown in --status shows that DNS resolution is working correctly. resolv.conf says nameserver 127.0.0.53 Restart resolved makes things work again. (Also, restarting Network Manager makes it work again.) Trying to ping a hostname from the cli when in the broken state yields zero output from resolved logs when in debug mode. Almost like it's not even hitting resolved, so this bug could very well be somewhere else. I've checked, and I can ping 127.0.0.1 and the default routes look OK, although there is a route to the VPN server left over. I'm all out of ideas. Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Hi Hui Wang, sorry it has taken me so long to test this. I installed your patch and noticed the following things: 1. I **think** the noise is less than before although still present. 2. The commands in your test instructions now make no difference (https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/comments/12) Please let me know if you need any further detail. -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1838682] [NEW] fftwq-wisdom does not load system quad-precision wisdom file
Public bug reported: $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 $ dpkg -l | grep fftw3 ii libfftw3-3:amd643.3.8-2 amd64Library for computing Fast Fourier Transforms ii libfftw3-bin3.3.8-2 amd64Library for computing Fast Fourier Transforms - Tools ii libfftw3-double3:amd64 3.3.8-2 amd64Library for computing Fast Fourier Transforms - Double precision ii libfftw3-long3:amd643.3.8-2 amd64Library for computing Fast Fourier Transforms - Long precision ii libfftw3-quad3:amd643.3.8-2 amd64Library for computing Fast Fourier Transforms - Quad precision ii libfftw3-single3:amd64 3.3.8-2 amd64Library for computing Fast Fourier Transforms - Single precision Let's see which wisdom file gets loaded: $ strace fftw-wisdom 2>&1 |grep open openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3_threads.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libm.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/etc/fftw/wisdom", O_RDONLY) = 3 Seems legit. What about the other wisdom binaries? $ strace fftwf-wisdom 2>&1 |grep open openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3f_threads.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3f.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libm.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/etc/fftw/wisdomf", O_RDONLY) = 3 Looks good. $ strace fftwl-wisdom 2>&1 |grep open openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3l_threads.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3l.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libm.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/etc/fftw/wisdoml", O_RDONLY) = 3 This is ok too. $ strace fftwq-wisdom 2>&1 |grep open openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3q_threads.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libfftw3q.so.3", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libquadmath.so.0", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libm.so.6", O_RDONLY|O_CLOEXEC) = 3 openat(AT_FDCWD, "/etc/fftw/wisdom", O_RDONLY) = 3 LOLWUT? When I explicitly read the wisdom file with `fftwq-wisdom -w /etc/fftw/wisdomq` it works Alas, concatenating all of the wisdom files together doesn't work. ** Affects: fftw3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fftw3 in Ubuntu. https://bugs.launchpad.net/bugs/1838682 Title: fftwq-wisdom does not load system quad-precision wisdom file Status in fftw3 package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 $ dpkg -l | grep fftw3 ii libfftw3-3:amd643.3.8-2 amd64Library for computing Fast Fourier Transforms ii libfftw3-bin3.3.8-2 amd64Library for computing Fast Fourier Transforms - Tools ii libfftw3-double3:amd64 3.3.8-2 amd64Library for computing Fast Fourier Transforms - Double precision ii libfftw3-long
[Touch-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
Hey Charles and Vincent, sorry to see this bug is STILL not fixed. Goodness me. The workaround I used is reported in this other bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1695775 I saw it in 17.04 and 17.10. Since then I gave up and moved to Ubuntu MATE, not just because of this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1814964] [NEW] No audio when logging in as second user. Only dummy audio device seen
Public bug reported: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1814964 Title: No audio when logging in as second user. Only dummy audio device seen Status in pulseaudio package in Ubuntu: New Bug description: Laptop with multiple user accounts. Logging in as any user has working audio, but if that session is locked and a second user logs in, the second user gets no sound. Workaround is for both users to log out and 2nd user to log in a fresh session. Obviously a problem if you cant log in as the first user. No sound hardware is shown in the MATE sound preferences, output pane only shows "dummy output". Looking at 'top' or system monitor shows that 1st user pulseaudio is running, but 2nd user pulseaudio is sleeping. $ lspci -nnk | grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b57] (rev 05) Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio [1028:0410] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 6 21:19:25 2019 InstallationDate: Installed on 2018-11-12 (86 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0T6M8G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor:
[Touch-packages] [Bug 1758087] [NEW] pgrep -f fails for long command lines
Public bug reported: If a command line is really long and the search term is toward the end of it, pgrep -f fails to find the process. Experimentally, it appears that the magic number is about 4084. The script below reproduces the problem. If the command line is short, pgrep -f reports both a sleep and a bash process. If the line is too long, pgrep -f only reports the sleep process. # pgrep -f fails if >= 4063, succeeds if < 4063 stringLength=4063 reallyLongString=$(cat /dev/urandom | tr -cd '[:alnum:]' | head -c $stringLength) bash -c "echo $reallyLongString > /dev/null ; sleep 999" 2> /dev/null& pid=$! sleep 1 echo no -f: pgrep -l sleep echo with -f: pgrep -fl sleep pkill sleep ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1758087 Title: pgrep -f fails for long command lines Status in procps package in Ubuntu: New Bug description: If a command line is really long and the search term is toward the end of it, pgrep -f fails to find the process. Experimentally, it appears that the magic number is about 4084. The script below reproduces the problem. If the command line is short, pgrep -f reports both a sleep and a bash process. If the line is too long, pgrep -f only reports the sleep process. # pgrep -f fails if >= 4063, succeeds if < 4063 stringLength=4063 reallyLongString=$(cat /dev/urandom | tr -cd '[:alnum:]' | head -c $stringLength) bash -c "echo $reallyLongString > /dev/null ; sleep 999" 2> /dev/null& pid=$! sleep 1 echo no -f: pgrep -l sleep echo with -f: pgrep -fl sleep pkill sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1758087/+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 1752053] Re: nvidia-390 fails to boot graphical display
I started to experience this problem for the first time on July 2nd, 2018 after upgrading to kernel 4.15.0-24-generic. It only happens on machines with a Nvidia card. It does not matter if ANY Nvidia drivers are installed or not. I downgraded to kernel 4.15.0-20, 0-22 and 0-23 but it didn't fix the issue. I confirmed this on 2 machines with Nvidia cards. adding deb http://de.archive.ubuntu.com/ubuntu/ bionic-proposed multiverse main universe restricted to /etc/apt/sources.list and running apt install libglvnd0 xserver-xorg-core libgl1-mesa-glx did not help. At least not on Linux Lite v4.0. It's takes about 3mins and 6 seconds to get to the desktop. Everything works as normal after that. So i ran some tests Lenovo ThinkPad W530 Model Type: 2436CTO GB 16GB RAM Intel i7-3920XM @ 2.90Ghz 4 Core 256 SSD lspci -vnn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Xubuntu 18.04 LTS (This is my main OS) - Broken Kernel v4.15.0-24 after updates. Updates downloaded during fresh install. Works after fresh install but not after updates applied through Software Update. Also tried kernel v4.17.0 and v4.17.3 login with ctrl+alt+f1 and after a few seconds i see: nouveau :01:00.0: msvld: unable to find firmware data dmesg | grep nouveau [ 34.304193] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 34.304206] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 34.304210] nouveau :01:00.0: msvld: unable to load firmware data [ 34.304277] nouveau :01:00.0: msvld: init failed, -19 Kubuntu 18.04 LTS - Works Kernel v4.15.0-20 after fresh install - Kernel v4.15.0-24 after updates. Updates downloaded during fresh install. Full install selected. Works after fresh install and after updates applied through Discover application. KDE neon User Edition 5.13 - Works 16.04 Kernel v4.13.0-45 after fresh install - Kernel v4.15.0-24 after updates. Updates downloaded during fresh install. Works after fresh install and after updates applied through Discover application. Installed nVidia driver v384.130 (nvidia-384) and still working. Lubuntu - 18.04 LTS – Works Kernel v4.15.0-20 after fresh install - Kernel v4.15.0-24 after updates. Updates downloaded during fresh install. Full install selected. Works after fresh install and after updates applied through Software Updater application. Installed nVidia driver v390 (nvidia-driver-390) and still working. Mate 18.04 LTS - Broken Kernel v4.15.0-24 after updates. Updates downloaded during fresh install. Full install selected. Works after fresh install but not after updates applied through Software Update. "Could not update ICEauthority file /home/user/.ICEauthority" appears during auto login. Desktop does not finishing loading but keyboard shortcuts work. Elementary OS 0.4.1 Loki – Works Kernel v4.15.0-24 after updates. Updates downloaded during fresh install. Works after fresh install and after updates applied through AppCenter. Installed kernel v4.17.0 and v4.17.3 and still works. But did receive this warning when upgrading the kernel. W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_27.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_04.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cnl_dmc_ver1_07.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_39.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver9_29.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_ver9_33.bin for module i915 W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia
[Touch-packages] [Bug 1736112] [NEW] Display error when using top with the memory bar or block graph
Public bug reported: Most of the time when using top in the display mode with a memory bar or block graph (by pressing "m" in top), the graph exceeds the scale by far and also the displayed number for memory usage is not correct. In the usual "numbers only" view the numbers are correct. I was not able to figure out when this problem appears or not, but it appears most of the times for me. I attached a screenshot to illustrate the problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: procps 2:3.3.12-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 11:30:36 2017 InstallationDate: Installed on 2016-07-29 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: procps UpgradeStatus: Upgraded to artful on 2017-11-11 (23 days ago) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "2017-12-04 11-21-11.png" https://bugs.launchpad.net/bugs/1736112/+attachment/5018094/+files/2017-12-04%2011-21-11.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1736112 Title: Display error when using top with the memory bar or block graph Status in procps package in Ubuntu: New Bug description: Most of the time when using top in the display mode with a memory bar or block graph (by pressing "m" in top), the graph exceeds the scale by far and also the displayed number for memory usage is not correct. In the usual "numbers only" view the numbers are correct. I was not able to figure out when this problem appears or not, but it appears most of the times for me. I attached a screenshot to illustrate the problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: procps 2:3.3.12-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 11:30:36 2017 InstallationDate: Installed on 2016-07-29 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: procps UpgradeStatus: Upgraded to artful on 2017-11-11 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1736112/+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 1736112] Re: Display error when using top with the memory bar or block graph
For some reason the problem seems to be solved in Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1736112 Title: Display error when using top with the memory bar or block graph Status in procps package in Ubuntu: New Bug description: Most of the time when using top in the display mode with a memory bar or block graph (by pressing "m" in top), the graph exceeds the scale by far and also the displayed number for memory usage is not correct. In the usual "numbers only" view the numbers are correct. I was not able to figure out when this problem appears or not, but it appears most of the times for me. I attached a screenshot to illustrate the problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: procps 2:3.3.12-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 11:30:36 2017 InstallationDate: Installed on 2016-07-29 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: procps UpgradeStatus: Upgraded to artful on 2017-11-11 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1736112/+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 1758087] Re: pgrep -f fails for long command lines
I am running 16.04.5 LTS (Xenial Xerus). pgrep version 3.3.10 (from procps-ng). I just confirmed that the problem still exists. When stringLength is >= 4063, pgrep does not find the bash process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1758087 Title: pgrep -f fails for long command lines Status in procps package in Ubuntu: Expired Bug description: If a command line is really long and the search term is toward the end of it, pgrep -f fails to find the process. Experimentally, it appears that the magic number is about 4084. The script below reproduces the problem. If the command line is short, pgrep -f reports both a sleep and a bash process. If the line is too long, pgrep -f only reports the sleep process. # pgrep -f fails if >= 4063, succeeds if < 4063 stringLength=4063 reallyLongString=$(cat /dev/urandom | tr -cd '[:alnum:]' | head -c $stringLength) bash -c "echo $reallyLongString > /dev/null ; sleep 999" 2> /dev/null& pid=$! sleep 1 echo no -f: pgrep -l sleep echo with -f: pgrep -fl sleep pkill sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1758087/+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 1453517] [NEW] Plasma 5.2 System Preference Crash -> destroyed QQuickItems can be left in the dirty list
Public bug reported: In latest Kubuntu (15.04, vivid) the system preference application is repeatingly crashing. Steps to reproduce: just open it, change a few settings switch to a new pane. Do that as long as required till the crash is happening (takes only very few attempts) The relevant bug on kde.org is https://bugs.kde.org/show_bug.cgi?id=344651- which says that this is a bug in Qt and it is resolved there in 5.4.2 (see https://bugreports.qt.io/browse/QTBUG-43376 ). => Please backport the fix or upgrade Qt to 5.4.2 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1453517 Title: Plasma 5.2 System Preference Crash -> destroyed QQuickItems can be left in the dirty list Status in qtbase-opensource-src package in Ubuntu: New Bug description: In latest Kubuntu (15.04, vivid) the system preference application is repeatingly crashing. Steps to reproduce: just open it, change a few settings switch to a new pane. Do that as long as required till the crash is happening (takes only very few attempts) The relevant bug on kde.org is https://bugs.kde.org/show_bug.cgi?id=344651- which says that this is a bug in Qt and it is resolved there in 5.4.2 (see https://bugreports.qt.io/browse/QTBUG-43376 ). => Please backport the fix or upgrade Qt to 5.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1453517/+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 1453517] Re: Plasma 5.2 System Preference Crash -> destroyed QQuickItems can be left in the dirty list
** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1453517 Title: Plasma 5.2 System Preference Crash -> destroyed QQuickItems can be left in the dirty list Status in qtbase-opensource-src package in Ubuntu: New Bug description: In latest Kubuntu (15.04, vivid) the system preference application is repeatingly crashing. Steps to reproduce: just open it, change a few settings switch to a new pane. Do that as long as required till the crash is happening (takes only very few attempts) The relevant bug on kde.org is https://bugs.kde.org/show_bug.cgi?id=344651- which says that this is a bug in Qt and it is resolved there in 5.4.2 (see https://bugreports.qt.io/browse/QTBUG-43376 ). => Please backport the fix or upgrade Qt to 5.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1453517/+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 1440889] Re: Dialer app launches to slow
Can I suggest "preloading" dialler when contacts are opened? In most cases I open contacts I select contact and go straight to dialling trather than anything else. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1440889 Title: Dialer app launches to slow Status in dialer-app package in Ubuntu: Confirmed Bug description: The dialer app on the BQ Aquarius 4.5 takes too long to launch. It takes 2-5 seconds to open the dialer. After that more time is required for dialing. I thing for a device that should at first still be a phone, this is much too long. Here a solution is absolutly neccessary. Could keeping the dialer app in the RAM be an option? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1440889/+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 1460301] [NEW] Incomming call - no info which SIM card was called (dual SIM)
Public bug reported: Ubuntu 14.10 (r22) (Don't know how to find a package version :/, but I checked for updates on 29-05-2015 and all apps are up to date) I have two SIM cards inserted into BQ Aquaris 4.5 On incoming call I expect to see information if SIM1 or SIM2 was dialled by caller alongside caller ID. I see only caller ID. It may be useful if one of the SIM cards is in roaming, or when one of the SIMs is a company number while other is a private number. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1460301 Title: Incomming call - no info which SIM card was called (dual SIM) Status in dialer-app package in Ubuntu: New Bug description: Ubuntu 14.10 (r22) (Don't know how to find a package version :/, but I checked for updates on 29-05-2015 and all apps are up to date) I have two SIM cards inserted into BQ Aquaris 4.5 On incoming call I expect to see information if SIM1 or SIM2 was dialled by caller alongside caller ID. I see only caller ID. It may be useful if one of the SIM cards is in roaming, or when one of the SIMs is a company number while other is a private number. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1460301/+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 1695775] [NEW] goa-daemon not stopped on logout, and gnome-keyring unusable on next log in
Public bug reported: Bug seen in Evolution - fails to connect to my google accounts on second log-in. Accounts are set up fine, but after a log out then log back in, they fail. Error reported in Evolution is: "Failed to authenticate: Failed to obtain an access token for '--@gmail.com':Failed to retrieve credentials from the keyring" It is fixed by running "/usr/lib/gnome-online-accounts/goa-daemon --replace" in the terminal. I found the bug described and confirmed on redhat, where I also found the solution. (although they have the goa-demon in the /usr/libexec/ folder) https://bugzilla.redhat.com/show_bug.cgi?id=1340203 As a work-around, for each user account I created a new file in ~/.config/autostart/ called goa-replace.desktop, and in a text-editor entered the following: [Desktop Entry] Name=GOA Replace Exec=/usr/lib/gnome-online-accounts/goa-daemon --replace NoDisplay=true Terminal=false Type=Application The problem seems to be that dbus is spawning goa-daemon, but then not killing the process when the user logs out. gnome-keyring IS killed, and this breaks the link between the two. Not sure what the *real* solution is, seems to be a big debate about how systemd leaves 'lingering' processes from users after log out. I see 28 processes left running after a user logs out. Surely this needs to be cleaned up??? Is there a better way to force systemd to properly close a users session? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-online-accounts 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jun 4 21:48:59 2017 InstallationDate: Installed on 2017-05-03 (32 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1695775 Title: goa-daemon not stopped on logout, and gnome-keyring unusable on next log in Status in gnome-online-accounts package in Ubuntu: New Bug description: Bug seen in Evolution - fails to connect to my google accounts on second log-in. Accounts are set up fine, but after a log out then log back in, they fail. Error reported in Evolution is: "Failed to authenticate: Failed to obtain an access token for '--@gmail.com':Failed to retrieve credentials from the keyring" It is fixed by running "/usr/lib/gnome-online-accounts/goa-daemon --replace" in the terminal. I found the bug described and confirmed on redhat, where I also found the solution. (although they have the goa-demon in the /usr/libexec/ folder) https://bugzilla.redhat.com/show_bug.cgi?id=1340203 As a work-around, for each user account I created a new file in ~/.config/autostart/ called goa-replace.desktop, and in a text-editor entered the following: [Desktop Entry] Name=GOA Replace Exec=/usr/lib/gnome-online-accounts/goa-daemon --replace NoDisplay=true Terminal=false Type=Application The problem seems to be that dbus is spawning goa-daemon, but then not killing the process when the user logs out. gnome-keyring IS killed, and this breaks the link between the two. Not sure what the *real* solution is, seems to be a big debate about how systemd leaves 'lingering' processes from users after log out. I see 28 processes left running after a user logs out. Surely this needs to be cleaned up??? Is there a better way to force systemd to properly close a users session? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-online-accounts 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jun 4 21:48:59 2017 InstallationDate: Installed on 2017-05-03 (32 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1695775/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I found the bug described and confirmed on redhat, where I also found the solution. (although they have the goa-demon in the /usr/libexec/ folder) https://bugzilla.redhat.com/show_bug.cgi?id=1340203 As a work-around, for each user account I created a new file in ~/.config/autostart/ called goa-replace.desktop, and in a text-editor entered the following: [Desktop Entry] Name=GOA Replace Exec=/usr/lib/gnome-online-accounts/goa-daemon --replace NoDisplay=true Terminal=false Type=Application The problem seems to be that dbus is spawning goa-daemon, but then not killing the process when the user logs out. gnome-keyring IS killed, and this breaks the link between the two. Not sure what the *real* solution is, seems to be a big debate about how systemd leaves 'lingering' processes from users after log out. I see 28 processes left running after a user logs out. Surely this needs to be cleaned up??? Is there a better way to force systemd to properly close a users session? ** Bug watch added: Red Hat Bugzilla #1340203 https://bugzilla.redhat.com/show_bug.cgi?id=1340203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1696799] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: share/bleachbit/bleachbit/Command.py", line 131, in execute func_ret = self.func() File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove raise RuntimeError(line) RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1) Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", line 131, in execute func_ret = self.func() File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove raise RuntimeError(line) RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1) Delete 1.1MB /var/cache/apt/archives ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libssl1.0.0: Install libssl1.0.0: Configure libssl1.0.0: Configure libssl-dev: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 8 12:29:11 2017 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ... dpkg: error processing package libssl1.0.0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-11-30 (190 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1696799 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssl package in Ubuntu: New Bug description: share/bleachbit/bleachbit/Command.py", line 131, in execute func_ret = self.func() File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove raise RuntimeError(line) RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1) Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", line 131, in execute func_ret = self.func() File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove raise RuntimeError(line) RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1) Delete 1.1MB /var/cache/apt/archives ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libssl1.0.0: Install libssl1.0.0: Configure libssl1.0.0: Configure libssl-dev: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 8 12:29:11 2017 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ... dpkg: error processing package libssl1.0.0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-11-30 (190 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696799/+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 1697306] [NEW] error
Public bug reported: does not update Shows Error: BrokenCount >0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 11 12:44:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:2102] InstallationDate: Installed on 2016-04-28 (408 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=80d375c8-4b70-466f-b69f-cc96476c9f3e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.404 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55A.404:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages ubuntu xenial -- 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/1697306 Title: error Status in xorg package in Ubuntu: New Bug description: does not update Shows Error: BrokenCount >0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jun 11 12:44:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:2102] InstallationDate: Installed on 2016-04-28 (408 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) MachineType: ASUSTeK COMPUTER INC. K55A ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=80d375c8-4b70-466f-b69f-cc96476c9f3e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55A.404 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55A.404:bd08/20/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K55A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2
[Touch-packages] [Bug 1679607] [NEW] Hashing known_hosts renders fingerprints unusable
Public bug reported: Running ssh-keygen -H against known_hosts renders the fingerprints so that a match is no longer found. The man page states this is 'safe to use on files that mix hashed and non-hashed names'. To reproduce on Ubuntu 16.10, with openssh-client 1:7.3p1-1: -- 1. Try to connect first time, prompted for fingerprint so add it user@myserver:~$ ssh example.com The authenticity of host 'example.com (192.0.2.1)' can't be established. ECDSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'example.com,192.0.2.1' (ECDSA) to the list of known hosts. u...@example.com's password: -- 2. Try to connect again, no prompt for fingerprint (as expected) user@myserver:~$ ssh example.com u...@example.com's password: -- 4. Hash the known hosts file user@myserver:~$ ssh-keygen -H /home/user/.ssh/known_hosts updated. Original contents retained as /home/user/.ssh/known_hosts.old WARNING: /home/user/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames -- 5. Try to connect again, prompted for fingerprint user@myserver:~$ ssh example.com The authenticity of host 'example.com (192.0.2.1)' can't be established. ECDSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.. Are you sure you want to continue connecting (yes/no)? ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1679607 Title: Hashing known_hosts renders fingerprints unusable Status in openssh package in Ubuntu: New Bug description: Running ssh-keygen -H against known_hosts renders the fingerprints so that a match is no longer found. The man page states this is 'safe to use on files that mix hashed and non-hashed names'. To reproduce on Ubuntu 16.10, with openssh-client 1:7.3p1-1: -- 1. Try to connect first time, prompted for fingerprint so add it user@myserver:~$ ssh example.com The authenticity of host 'example.com (192.0.2.1)' can't be established. ECDSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'example.com,192.0.2.1' (ECDSA) to the list of known hosts. u...@example.com's password: -- 2. Try to connect again, no prompt for fingerprint (as expected) user@myserver:~$ ssh example.com u...@example.com's password: -- 4. Hash the known hosts file user@myserver:~$ ssh-keygen -H /home/user/.ssh/known_hosts updated. Original contents retained as /home/user/.ssh/known_hosts.old WARNING: /home/user/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames -- 5. Try to connect again, prompted for fingerprint user@myserver:~$ ssh example.com The authenticity of host 'example.com (192.0.2.1)' can't be established. ECDSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.. Are you sure you want to continue connecting (yes/no)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1679607/+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 1679607] Re: Hashing known_hosts renders fingerprints unusable
*** This bug is a duplicate of bug 1668093 *** https://bugs.launchpad.net/bugs/1668093 Ah yes, same thing, sorry about that - default (simple) search doesn't show bugs with Fix Released so I didn't spot it. Will mark as duplicate. ** This bug has been marked a duplicate of bug 1668093 ssh-keygen -H corrupts already hashed entries -- 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/1679607 Title: Hashing known_hosts renders fingerprints unusable Status in openssh package in Ubuntu: New Bug description: Running ssh-keygen -H against known_hosts renders the fingerprints so that a match is no longer found. The man page states this is 'safe to use on files that mix hashed and non-hashed names'. To reproduce on Ubuntu 16.10, with openssh-client 1:7.3p1-1: -- 1. Try to connect first time, prompted for fingerprint so add it user@myserver:~$ ssh example.com The authenticity of host 'example.com (192.0.2.1)' can't be established. ECDSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'example.com,192.0.2.1' (ECDSA) to the list of known hosts. u...@example.com's password: -- 2. Try to connect again, no prompt for fingerprint (as expected) user@myserver:~$ ssh example.com u...@example.com's password: -- 4. Hash the known hosts file user@myserver:~$ ssh-keygen -H /home/user/.ssh/known_hosts updated. Original contents retained as /home/user/.ssh/known_hosts.old WARNING: /home/user/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames -- 5. Try to connect again, prompted for fingerprint user@myserver:~$ ssh example.com The authenticity of host 'example.com (192.0.2.1)' can't be established. ECDSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.. Are you sure you want to continue connecting (yes/no)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1679607/+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 1670031] [NEW] Wireless driver (QCA-9377) not working properly
Public bug reported: Hello guys, I have Lenovo Ideapad 500S-13ISK. It is bundled with Qualcomm Atheros QCA-9377 (rev 30) 802.11ac wireless card. Currently I have running Ubuntu 16.10 with all security updates. Wireless is dropping constantly. I tried different GNU/Linux distributions but the result is either same or worse. I assume is something related to NetworkManager and eventually Systemd. The thing is that I loose signal at some point but the network manager indicates that I have connection. After toggling Airplane mode it manages to continue to work properly but I am loosing the list with wireless connections which are available to be. For some reason it starts to show that I am connected through cable, instead of wireless. The only two ways to resolve constant drops in the signal I found is to toggle Airplane mode or restart NetworkManager. Both results to wrong indication and disables me from choosing another network. ➜ ~ lsb_release -rd Description:Ubuntu 16.10 Release:16.10 ➜ ~ apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://bg.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager qca9377 ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1670031/+attachment/4831428/+files/lspci-vnvn.log ** Package changed: linux (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1670031 Title: Wireless driver (QCA-9377) not working properly Status in network-manager package in Ubuntu: New Bug description: Hello guys, I have Lenovo Ideapad 500S-13ISK. It is bundled with Qualcomm Atheros QCA-9377 (rev 30) 802.11ac wireless card. Currently I have running Ubuntu 16.10 with all security updates. Wireless is dropping constantly. I tried different GNU/Linux distributions but the result is either same or worse. I assume is something related to NetworkManager and eventually Systemd. The thing is that I loose signal at some point but the network manager indicates that I have connection. After toggling Airplane mode it manages to continue to work properly but I am loosing the list with wireless connections which are available to be. For some reason it starts to show that I am connected through cable, instead of wireless. The only two ways to resolve constant drops in the signal I found is to toggle Airplane mode or restart NetworkManager. Both results to wrong indication and disables me from choosing another network. ➜ ~ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 ➜ ~ apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://bg.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1670031/+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 1689825] Re: gnome-keyring not unlocked on boot
It may not be flatpak on its own, but the machine I installed (and later removed and purged) flatkpak on this problem exists. (So a correlation does seem to exist) It might have something to do with other PPAs or how packages you install from external PPAs affect the system. The only major changes I made with the system around the time this happened was installing flatpak (and monodevelop through it), wine updating to 2.11 staging, and some retroarch cores updating. Also it might be worth looking into how exactly the gnome-keyring-daemon is started on login to see if there is a manual edit to some file that could resolve this issue. Sadly I don't have much else to offer other than that I am using Xubuntu 16.04.2 and have decided that the best temporary fix is to just enter my password in a second time by automatically starting the keyring daemon on startup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
My workaround above (calling "goa-daemon --replace" on login) isnt working all the time, sadly. On occasion, I am ending up with 3 or 4 instances of goa-daemon per user (I guess --replace isnt able to kill the previous instance?). Multiple instances results in high CPU usage. I have also seen goa-daemon report that it cannot connect to the keychain: "/usr/lib/gnome-online-accounts/goa-daemon --replace goa-daemon-Message: goa-daemon version 3.24.0 starting (goa-daemon:18954): GoaBackend-WARNING **: secret_password_lookup_sync() returned NULL goa-daemon-Message: /org/gnome/OnlineAccounts/Accounts/account_1496262706_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: No credentials found in the keyring (goa-error-quark, 4)" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Hi Kai-Heng Feng, Do you have a link to a process that I can use to test your patch? Many thanks. -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Hi Kai-Heng Feng, I successfully applied the patch, thanks. Now when the headphones are plugged in there are a few seconds of hissing before it goes quiet. If I change the volume, the hissing returns and stops after around 3-5s. If I play some music and then stop the music, the hissing returns and eventually stops after around 10s. Is this the expected behaviour? -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
It seems this was a red herring. I was testing on battery power which is why the audio was being runtime suspended. The hissing remains constant when the laptop is plugged in. -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
No. The issue remains. -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
This noise disappears when running this command. sudo ./hda-verb /dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x0 The noise returns when running this command. sudo hda-verb /dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x20 Thanks! -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1773859] Re: upgrades to 18.04 fail
I got nipped by this bug today moving from 16.04LTS to 18.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 495981] Re: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k
I'm going to bump this, as the last report was years ago. I'm now experiencing this issue on a Qualcomm Atheros AR938x device I've had for years now. Same issue with constant disconnects as well as a new issue that might involve iommu? [ 680.361521] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfdee1544 flags=0x] [ 680.425700] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe720fc4 flags=0x] [ 680.425707] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xfe721000 flags=0x] [ 680.489520] ath9k :21:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xff0d5a44 flags=0x] [ 680.650051] wlo1: authenticate with 10:c3:7b:ce:7e:ac [ 680.665173] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3) [ 680.666229] wlo1: authenticated [ 680.669072] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3) [ 680.670356] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 aid=4) [ 680.670494] wlo1: associated [ 1014.692234] wlo1: authenticate with 10:c3:7b:ce:7e:ac [ 1014.707630] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3) [ 1014.708714] wlo1: authenticated [ 1014.711340] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3) [ 1014.712644] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 aid=4) [ 1014.712784] wlo1: associated [ 1295.496298] wlo1: authenticate with 10:c3:7b:ce:7e:ac [ 1295.511421] wlo1: send auth to 10:c3:7b:ce:7e:ac (try 1/3) [ 1295.512484] wlo1: authenticated [ 1295.514554] wlo1: associate with 10:c3:7b:ce:7e:ac (try 1/3) [ 1295.515851] wlo1: RX AssocResp from 10:c3:7b:ce:7e:ac (capab=0x11 status=0 aid=4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/495981 Title: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k Status in network-manager package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I have Dell studio XPS 13 running: Description: Ubuntu 9.10 Release: 9.10 with wifi card (lspci): 06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) that works (tries to) with ath9k module. It connects to my access point and works ok however, It disconnects every 2-3 min saying (in dmesg): [ 311.600306] wlan0: RX AssocResp from 00:1d:68:0c:97:63 (capab=0x411 status=0 aid=2) and then automatically reconnects... I have tried different drivers and other things Interestingly when I right-clicked on network manger applet, select ¨disable networking¨ and then set up everything myself on console using iwconfig and dhclient. IT WORKS!!! no disconnections wpa_supplicant is still running in a background but not doing anything (my wifi has WEP encryption). I´ve seen some similar reports in Internet but they seem to think that it is a driver problem when to me it looks like a NetworkManager issue... Hope it helps drphd ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sat Dec 12 19:42:18 2009 DistroRelease: Ubuntu 9.10 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) IpRoute: 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.65 172.16.77.0/24 dev vmnet1 proto kernel scope link src 172.16.77.1 172.16.158.0/24 dev vmnet8 proto kernel scope link src 172.16.158.1 default via 192.168.1.254 dev wlan0 NonfreeKernelModules: nvidia Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: network-manager Uname: Linux 2.6.31-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/495981/+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 1882453] [NEW] GUI blanks after long period of use
Public bug reported: GUI screen goes blank with a right click on the desktop or a click on the power button. The entire systems seems to slow too, with CPU utilization reaching 100% at a consistent interval. This has happened twice already after a long period of idle or when conducting many actions with several applications. Not sure if any of it is causation given its only happened twice and I can't replicate the problem consistently. If you need further information reach me at clmora...@pm.me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 15:00:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974] InstallationDate: Installed on 2020-05-20 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7885 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=40367ef8-089b-4ef9-9b43-d538f9b52b3d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7885 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1882453 Title: GUI blanks after long period of use Status in xorg package in Ubuntu: New Bug description: GUI screen goes blank with a right click on the desktop or a click on the power button. The entire systems seems to slow too, with CPU utilization reaching 100% at a consistent interval. This has happened twice already after a long period of idle or when conducting many actions with several applications. Not sure if any of it is causation given its only happened twice and I can't replicate the problem consistently. If you need further information reach me at clmora...@pm.me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: sk
[Touch-packages] [Bug 914033]
*** Bug 67011 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/914033 Title: [Upstream] threading crashes in qt with kde theme Status in Qt: Fix Released Status in “libreoffice” package in Ubuntu: Fix Released Status in “qt4-x11” package in Ubuntu: Fix Released Status in “qt4-x11” source package in Oneiric: Fix Released Status in “libreoffice” package in Mandriva: Fix Released Bug description: let Qt call XInitThreads(), so that it knows it's been called Otherwise QPixmap complains when used outside of the main Qt thread and resets itself to null pixmap, eventually leading to crashes. Upstream reports that Libreoffice and Qt need a patch each to work together with Libreoffice 3.4 and Qt 4.7, this is because of assumptions about threading. To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/914033/+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 1418029] [NEW] what f r u talking about
Public bug reported: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 4 04:48:54 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-35-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-41-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-44-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-45-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:308f] Subsystem: Hewlett-Packard Company Device [103c:308f] InstallationDate: Installed on 2014-09-17 (140 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Hewlett-Packard HP Mini 110-1000 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=ae1cb9b1-6f1c-4c27-8b1f-c720151837f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.05 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.09 dmi.chassis.asset.tag: CNU9241TZH dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.05:bd05/11/2009:svnHewlett-Packard:pnHPMini110-1000:pvr03A8100010030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.09:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Mini 110-1000 dmi.product.version: 03A8100010030 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 2 13:52:20 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4097 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 package-from-proposed trusty 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/1418029 Title: what f r u talking about Status in xorg package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 4 04:48:54 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-35-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-41-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-44-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-45-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:308f] Subsystem: Hewlett-Packard Company Device [103c:308f] InstallationDate: Installed on 2014-09-17 (140 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release
[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
I've been watching this one and the related bugs for a while. Using an Nvidia (580) with an Intel (HD3000) on a desktop PC this issue is substantially improved in the latest xorg-edgers releases; it's now very close to working perfectly. There are still some small niggles - using Unity in 16.x the cursor will flicker when changing between icons on the Launcher and when moving between the Launcher and the rest of the desktop. In Cinnamon it's almost entirely gone - it's only especially prominent when moving between menu directories. There are a couple of other flashes here and there, but it's otherwise working exactly as you'd want it to. I'll happily submit a bug report if it'll help, but it's looking like the developers have narrowed the cause down - hopefully it's not just a fortunate accident. -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1548571] [NEW] start up
Public bug reported: had 2 reboot @ start up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.1B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.0E:bd09/14/2009:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.0E:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.1B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2530p dmi.product.version: F.0E dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 17 09:10:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4663 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1548571 Title: start up Status in xorg package in Ubuntu: New Bug description: had 2 reboot @ start up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.1B dmi.chassis.type: 10 dmi.cha
[Touch-packages] [Bug 1548574] [NEW] all files read ony including trash
Public bug reported: b 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec[4405]: ralf: Executing command [USER=root] [TTY=unknown] [CWD=/home/ralf] [COMMAND=/usr/lib/update-notifier/package-system-locked] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.1B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.0E:bd09/14/2009:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.0E:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.1B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2530p dmi.product.version: F.0E dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 17 09:10:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4663 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1548574 Title: all files read ony including trash Status in xorg package in Ubuntu: New Bug description: b 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec[4405]: ralf: Executing command [USER=root] [TTY=unknown] [CWD=/home/ralf] [COMMAND=/usr/lib/update-notifier/package-system-locked] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device
[Touch-packages] [Bug 1548574] Re: all files read ony including trash
b 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec[4405]: ralf: Executing command [USER=root] [TTY=unknown] [CWD=/home/ralf] [COMMAND=/usr/lib/update-notifier/package-system-locked] -- 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/1548574 Title: all files read ony including trash Status in xorg package in Ubuntu: New Bug description: b 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec[4405]: ralf: Executing command [USER=root] [TTY=unknown] [CWD=/home/ralf] [COMMAND=/usr/lib/update-notifier/package-system-locked] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.1B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.0E:bd09/14/2009:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.0E:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.1B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2530p dmi.product.version: F.0E dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 17 09:10:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4663 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548574/+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 1548574] Re: all files read ony including trash
b 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec[4405]: ralf: Executing command [USER=root] [TTY=unknown] [CWD=/home/ralf] [COMMAND=/usr/lib/update-notifier/package-system-locked] -- 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/1548574 Title: all files read ony including trash Status in xorg package in Ubuntu: New Bug description: b 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 22 17:37:45 ralf-HP-EliteBook-2530p pkexec[4405]: ralf: Executing command [USER=root] [TTY=unknown] [CWD=/home/ralf] [COMMAND=/usr/lib/update-notifier/package-system-locked] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.1B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.0E:bd09/14/2009:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.0E:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.1B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2530p dmi.product.version: F.0E dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 17 09:10:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4663 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548574/+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 1638345] Re: avahi-daemon crashes multiple times an hour
Hi! I have the same problem, but only when I am in a specific WiFi which uses MSCHPv2. In this case also my network manager crashes sometimes when resuming from sleep mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+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 1615423] [NEW] it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone
Public bug reported: from install it was fine, but all of a sudden it lost all printers and will not add any 16.04.1 chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 21 19:16:31 2016 InstallationDate: Installed on 2016-05-08 (105 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire ES1-531 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire ES1-531 dmi.board.vendor: Acer dmi.board.version: V1.11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.name: Aspire ES1-531 dmi.product.version: V1.11 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1615423 Title: it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone Status in cups package in Ubuntu: New Bug description: from install it was fine, but all of a sudden it lost all printers and will not add any 16.04.1 chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 21 19:16:31 2016 InstallationDate: Installed on 2016-05-08 (105 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire ES1-531 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire ES1-531 dmi.board.vendor: Acer dmi.board.version: V1.11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.name: Aspire ES1-531 dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1615423/+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
Re: [Touch-packages] [Bug 1615423] Re: it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone
its in the description part of the bug report laptop from install it was fine, but all of a sudden it has lost all printers and will not add any On 21/08/16 23:15, Till Kamppeter wrote: > What does not work? > > Please follow the instructions on > > https://wiki.ubuntu.com/DebuggingPrintingProblems > > when you report printing-related bugs. > > ** Changed in: cups (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1615423 Title: it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone Status in cups package in Ubuntu: Incomplete Bug description: from install it was fine, but all of a sudden it lost all printers and will not add any 16.04.1 chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 21 19:16:31 2016 InstallationDate: Installed on 2016-05-08 (105 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire ES1-531 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire ES1-531 dmi.board.vendor: Acer dmi.board.version: V1.11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.name: Aspire ES1-531 dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1615423/+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 1606929] [NEW] ssh-agent PKCS#11: agent refused operation
Public bug reported: I'm using simple-tpm-pk11 (from Ubuntu repo) and can successfully connect to SSH using a TPM key. When trying to add the key to my ssh-agent, the action is refused: $ ssh-add -s /usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so Enter passphrase for PKCS#11: Could not add card "/usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so": agent refused operation Thomas Habets, author of simple-tpm-pk11 suggested to compile ssh-agent from source [1]. This fixed the issue. Recompile steps: $ apt-get source openssh-client […] $ cd openssh-7.2p2 $ ./configure --prefix=$HOME/opt/openssh […] $ grep -q '^#define ENABLE_PKCS11' config.h && echo success || echo fail success $ sudo mkdir -p /var/empty $ make install […] $ ~/opt/openssh/bin/ssh-agent [… env stuff for ssh-agent. copy-paste run this …] $ ssh-add -s /usr/local/lib/libsimple-tpm-pk11.so Enter passphrase for PKCS#11: Card added: /usr/local/lib/libsimple-tpm-pk11.so $ ssh-add -l 2048 SHA256:x[…]xx /usr/local/lib/libsimple-tpm-pk11.so (RSA) 1) Ubuntu 16.04.1 LTS 2) openssh-client 1:7.2p2-4ubuntu1 simple-tpm-pk11 0.04-1 3) I would expect the Ubuntu binary release of ssh-agent to allow adding the TPM key just like the locally compiled test. 4) An error is returned by ssh-add: Could not add card "/usr/lib/x86_64 -linux-gnu/libsimple-tpm-pk11.so": agent refused operation ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-client 1:7.2p2-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 27 06:24:19 2016 InstallationDate: Installed on 2016-07-26 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) upstart.ssh-agent.log: ssh-agent stop/pre-start, process 4012 ssh-agent stop/pre-start, process 3782 ssh-agent stop/pre-start, process 3440 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1606929 Title: ssh-agent PKCS#11: agent refused operation Status in openssh package in Ubuntu: New Bug description: I'm using simple-tpm-pk11 (from Ubuntu repo) and can successfully connect to SSH using a TPM key. When trying to add the key to my ssh-agent, the action is refused: $ ssh-add -s /usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so Enter passphrase for PKCS#11: Could not add card "/usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so": agent refused operation Thomas Habets, author of simple-tpm-pk11 suggested to compile ssh- agent from source [1]. This fixed the issue. Recompile steps: $ apt-get source openssh-client […] $ cd openssh-7.2p2 $ ./configure --prefix=$HOME/opt/openssh […] $ grep -q '^#define ENABLE_PKCS11' config.h && echo success || echo fail success $ sudo mkdir -p /var/empty $ make install […] $ ~/opt/openssh/bin/ssh-agent [… env stuff for ssh-agent. copy-paste run this …] $ ssh-add -s /usr/local/lib/libsimple-tpm-pk11.so Enter passphrase for PKCS#11: Card added: /usr/local/lib/libsimple-tpm-pk11.so $ ssh-add -l 2048 SHA256:x[…]xx /usr/local/lib/libsimple-tpm-pk11.so (RSA) 1) Ubuntu 16.04.1 LTS 2) openssh-client 1:7.2p2-4ubuntu1 simple-tpm-pk11 0.04-1 3) I would expect the Ubuntu binary release of ssh-agent to allow adding the TPM key just like the locally compiled test. 4) An error is returned by ssh-add: Could not add card "/usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so": agent refused operation ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-client 1:7.2p2-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 27 06:24:19 2016 InstallationDate: Installed on 2016-07-26 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) upstart.ssh-agent.log: ssh-agent stop/pre-start, process 4012 ssh-agent stop/pre-start, process 3782 ssh-agent stop/pre-start, process 3440 To manage notifications about this bug go to: https://bugs.launchpad.net/u
[Touch-packages] [Bug 1606929] Re: ssh-agent PKCS#11: agent refused operation
Sorry. Actually I just discovered that ssh-agent wasn't used by default, but gnome-keyring-daemon is. Probably gnome-keyring-daemon just does not support PKCS#11 yet... -- 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/1606929 Title: ssh-agent PKCS#11: agent refused operation Status in openssh package in Ubuntu: New Bug description: I'm using simple-tpm-pk11 (from Ubuntu repo) and can successfully connect to SSH using a TPM key. When trying to add the key to my ssh-agent, the action is refused: $ ssh-add -s /usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so Enter passphrase for PKCS#11: Could not add card "/usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so": agent refused operation Thomas Habets, author of simple-tpm-pk11 suggested to compile ssh- agent from source [1]. This fixed the issue. Recompile steps: $ apt-get source openssh-client […] $ cd openssh-7.2p2 $ ./configure --prefix=$HOME/opt/openssh […] $ grep -q '^#define ENABLE_PKCS11' config.h && echo success || echo fail success $ sudo mkdir -p /var/empty $ make install […] $ ~/opt/openssh/bin/ssh-agent [… env stuff for ssh-agent. copy-paste run this …] $ ssh-add -s /usr/local/lib/libsimple-tpm-pk11.so Enter passphrase for PKCS#11: Card added: /usr/local/lib/libsimple-tpm-pk11.so $ ssh-add -l 2048 SHA256:x[…]xx /usr/local/lib/libsimple-tpm-pk11.so (RSA) 1) Ubuntu 16.04.1 LTS 2) openssh-client 1:7.2p2-4ubuntu1 simple-tpm-pk11 0.04-1 3) I would expect the Ubuntu binary release of ssh-agent to allow adding the TPM key just like the locally compiled test. 4) An error is returned by ssh-add: Could not add card "/usr/lib/x86_64-linux-gnu/libsimple-tpm-pk11.so": agent refused operation ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-client 1:7.2p2-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 27 06:24:19 2016 InstallationDate: Installed on 2016-07-26 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) upstart.ssh-agent.log: ssh-agent stop/pre-start, process 4012 ssh-agent stop/pre-start, process 3782 ssh-agent stop/pre-start, process 3440 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1606929/+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 1546645] [NEW] de ve de
Public bug reported: stopped working have 2 manually restart comp ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.1B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PSUVer.F.0E:bd09/14/2009:svnHewlett-Packard:pnHPEliteBook2530p:pvrF.0E:rvnHewlett-Packard:rn30E1:rvrKBCVersion03.1B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2530p dmi.product.version: F.0E dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 17 09:10:33 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4663 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1546645 Title: de ve de Status in xorg package in Ubuntu: New Bug description: stopped working have 2 manually restart comp ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 17 09:58:26 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e1] Subsystem: Hewlett-Packard Company Device [103c:30e1] InstallationDate: Installed on 2016-02-07 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP EliteBook 2530p ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=UUID=7c6ca150-58b9-41a9-ae1e-8c085fe4d980 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PSU Ver. F.0E dmi.board.name: 30E1 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Vers
[Touch-packages] [Bug 1529554] [NEW] letter fonts display icons have zoomed almosted every single day since it happened few days ago
Public bug reported: i need a breif demo or how i am able to return these back to the normal sizes they were . . i can barely read some icon descriptions due to fact they are way to zoomed in and somehow cant read some pop up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 28 18:48:17 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-34-generic, x86_64: installed DpkgLog: GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0349] Subsystem: Acer Incorporated [ALI] Device [1025:0349] InstallationDate: Installed on 2014-08-24 (491 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Acer AO533 ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=b813f8db-a23e-48ca-bed5-519ddeb19d01 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AO533 dmi.board.vendor: Acer dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd06/07/2010:svnAcer:pnAO533:pvrV1.05:rvnAcer:rnAO533:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.name: AO533 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 28 14:25:34 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 661 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 fonts trusty 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/1529554 Title: letter fonts display icons have zoomed almosted every single day since it happened few days ago Status in xorg package in Ubuntu: New Bug description: i need a breif demo or how i am able to return these back to the normal sizes they were . . i can barely read some icon descriptions due to fact they are way to zoomed in and somehow cant read some pop up ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 28 18:48:17 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-34-generic, x86_64: installed DpkgLog: GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0349] Subsystem: Acer Incorporated [ALI] Device [1025:0349] InstallationDate: Installed on 2014-08-24 (491 day
[Touch-packages] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04
Same problem with Audiobox 22 VSL. Unplugged and plugged back in twice and the device is now recognised. -- 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/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in alsa-driver package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Bug description: Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+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 1573205] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: caused when upgrading to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 20:01:39 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-04 (200 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1573205 Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: New Bug description: caused when upgrading to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 20:01:39 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-10-04 (200 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1573205/+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 1445436] Re: Segmentation faults in libapt-pkg.so.4.12.0
I can confirm that this bug applies for Mint 17.2 and that the workaround provided by Ken works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1445436 Title: Segmentation faults in libapt-pkg.so.4.12.0 Status in Linux Mint: Confirmed Status in apt package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Bug description: For no obvious reason whatsoever it is now completely impossible for me to use APT. Furthermore it is completely impossible for me to report a bug with apport. apport-gtk[4025]: segfault at aca04d24 ip b4b622f1 sp aebe7240 error 6 in libapt-pkg.so.4.12.0[b4a8c000+125000] apt-get[4087]: segfault at b58bed24 ip b768c2f1 sp bfc6d800 error 6 in libapt-pkg.so.4.12.0[b75b6000+125000] apt-cache[4827]: segfault at b58fbd24 ip b76c82f1 sp bfc7ece0 error 6 in libapt-pkg.so.4.12.0[b75f2000+125000] apport-gtk[4886]: segfault at ab92fd24 ip b4b8d2f1 sp b46d4240 error 6 in libapt-pkg.so.4.12.0[b4ab7000+125000] apt-get[4929]: segfault at b5953d24 ip b77212f1 sp bfb75f40 error 6 in libapt-pkg.so.4.12.0[b764b000+125000] apt-get[5110]: segfault at b58c9d24 ip b7697281 sp bf9cf750 error 6 in libapt-pkg.so.4.12.0[b75c1000+125000] apt-get[5258]: segfault at b58f0d24 ip b76bd281 sp bfa1fe40 error 6 in libapt-pkg.so.4.12.0[b75e7000+125000] apt-get[5381]: segfault at b58bad24 ip b7687281 sp bfdaf300 error 6 in libapt-pkg.so.4.12.0[b75b1000+125000] apt-get[5991]: segfault at b595ed24 ip b772c281 sp bff062a0 error 6 in libapt-pkg.so.4.12.0[b7656000+125000] apt-get[6104]: segfault at b5982d24 ip b7750281 sp bfdbeee0 error 6 in libapt-pkg.so.4.12.0[b767a000+125000] apt-get[6279]: segfault at b597dd24 ip b774b281 sp bfab9600 error 6 in libapt-pkg.so.4.12.0[b7675000+125000] apt-get[6814]: segfault at b58b4d24 ip b7682281 sp bfb1efe0 error 6 in libapt-pkg.so.4.12.0[b75ac000+125000] I have tried reinstalling libapt- pkg4.12_0.8.16~exp12ubuntu10.21_i386.deb but nothing changes. Last upgrade log: Start-Date: 2015-04-15 00:39:51 Commandline: /usr/bin/apt-get dist-upgrade Upgrade: libsdl1.2debian:i386 (1.2.14-6.4ubuntu3, 1.2.14-6.4ubuntu3.1), libxfixes3:i386 (5.0-4ubuntu4.3, 5.0-4ubuntu4.4), libx11-data:i386 (1.4.99.1-0ubuntu2.2, 1.4.99.1-0ubuntu2.3), libxi-dev:i386 (1.7.1.901-1ubuntu1~precise2, 1.7.1.901-1ubuntu1~precise3), libxrender-dev:i386 (0.9.6-2ubuntu0.1, 0.9.6-2ubuntu0.2), libx11-xcb1:i386 (1.4.99.1-0ubuntu2.2, 1.4.99.1-0ubuntu2.3), x11proto-core-dev:i386 (7.0.22-1ubuntu0.1, 7.0.22-1ubuntu0.2), libxext-dev:i386 (1.3.0-3ubuntu0.1, 1.3.0-3ubuntu0.2), xserver-xorg-video-vmware:i386 (12.0.1-1ubuntu1.1, 12.0.1-1ubuntu1.2), libxrender1:i386 (0.9.6-2ubuntu0.1, 0.9.6-2ubuntu0.2), libxrandr-dev:i386 (1.3.2-2ubuntu0.2, 1.3.2-2ubuntu0.3), libx11-6:i386 (1.4.99.1-0ubuntu2.2, 1.4.99.1-0ubuntu2.3), ntpdate:i386 (4.2.6.p3+dfsg-1ubuntu3.3, 4.2.6.p3+dfsg-1ubuntu3.4), libx11-dev:i386 (1.4.99.1-0ubuntu2.2, 1.4.99.1-0ubuntu2.3), libx11-doc:i386 (1.4.99.1-0ubuntu2.2, 1.4.99.1-0ubuntu2.3), libxfixes-dev:i386 (5.0-4ubuntu4.3, 5.0-4ubuntu4.4), libxi6:i386 (1.7.1.9 01-1ubuntu1~precise2, 1.7.1.901-1ubuntu1~precise3), libxp6:i386 (1.0.1-2ubuntu0.12.04.1, 1.0.1-2ubuntu0.12.04.2), libxv1:i386 (1.0.6-2ubuntu0.1, 1.0.6-2ubuntu0.2), libxext6:i386 (1.3.0-3ubuntu0.1, 1.3.0-3ubuntu0.2), libxrandr2:i386 (1.3.2-2ubuntu0.2, 1.3.2-2ubuntu0.3) End-Date: 2015-04-15 00:40:43 Clearing the entire archive including *.bin* files didn't work. http://askubuntu.com/a/14552/170177 Increasing or disabling the cache limit made no difference. https://aziest.wordpress.com/2011/01/24/how-to-increase-your-apt-cache-limit/ Still looking and will update. --- ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 DistroRelease: Ubuntu 12.04 MarkForUpload: True NonfreeKernelModules: nvidia Package: apt 0.8.16~exp12ubuntu10.23 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Tags: precise package-from-proposed Uname: Linux 3.11.0-26-generic i686 UpgradeStatus: Upgraded to precise on 2014-12-07 (130 days ago) UserGroups: adm admin audio cdrom debian-tor dialout dip fax floppy fuse lp lpadmin plugdev sambashare scanner tape video To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1445436/+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 1483228] [NEW] my laptop is running like shit thought maybe you could help
Public bug reported: sent everything to you my laptop freezes all the time its slow its not right ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-62.101-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Aug 10 05:09:59 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-62-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:308f] Subsystem: Hewlett-Packard Company Device [103c:308f] InstallationDate: Installed on 2014-09-17 (327 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Hewlett-Packard HP Mini 110-1000 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=ae1cb9b1-6f1c-4c27-8b1f-c720151837f7 ro splash quiet nopat plymouth:debug=1=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.05 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.09 dmi.chassis.asset.tag: CNU9241TZH dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.05:bd05/11/2009:svnHewlett-Packard:pnHPMini110-1000:pvr03A8100010030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.09:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Mini 110-1000 dmi.product.version: 03A8100010030 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Aug 10 04:40:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4097 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/1483228 Title: my laptop is running like shit thought maybe you could help Status in xorg package in Ubuntu: New Bug description: sent everything to you my laptop freezes all the time its slow its not right ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-62.101-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Aug 10 05:09:59 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.13.0-62-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:308f] Subsystem: Hewlett-Packard Company Device [103c:308f] InstallationDate: Installed on 2014-09-17 (327 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Hewlett-Packard HP Mini 110-1000 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.
[Touch-packages] [Bug 1487632] [NEW] the phone shows "cell network indicator" ON but there is no telephony possible
Public bug reported: I have had a stange bug on my Meizu Mx4 at least 5 times till ota 5 ... but I wasn't able to reproduce it ...till yesterday It generally occured after a screen freeze ... my tel connection in task bar was ok : cell network icon triangle "filled".. ON but in fact the telephony service was not functional - when making a phone call there was "no connection available" when in the "phone call screen" .. - The people that called me during the problem heard the ring several times ..but I didn't receive any call or msg on the phone.. so i was probably connected to the cell network cause my account was receiving calls and they were not redirected to the message box directly.. but on my side the phone didn't ring nor receive msg -> I have tried to use plane mode on/off / changing the sim card /reboot ... nothing worked .. then after some times it returned to normal ... The main problem here is that you consider that the phone is working cause you see the triangle icon full in the indicator bar ... But you don't receive the phone calls ... like if you were ignoring phone calls Yesterday I found a way to reproduce the bug ... and the workaround that makes the telephony-service work again after the bug how to reproduce the problem : 1. put wifi off and phone data off (2g/3g/4g) telephony triangle icon is filled 2. restart the phone 3. after restart the phone indicator bar shows full GSM cover with the triangle icon filled. 4. if you go in the phone dialer ... you have no network .. you can't make phone call .. and you can't receive phone calls nor sms Workaround: (to get your gsm back to normal) - to make the telephony work again : it's odd put you must only put wifi "on" from the indicator bar then telephony is functional again... and you get the operator name in phone app Kind regards ** Affects: telephony-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1487632 Title: the phone shows "cell network indicator" ON but there is no telephony possible Status in telephony-service package in Ubuntu: New Bug description: I have had a stange bug on my Meizu Mx4 at least 5 times till ota 5 ... but I wasn't able to reproduce it ...till yesterday It generally occured after a screen freeze ... my tel connection in task bar was ok : cell network icon triangle "filled".. ON but in fact the telephony service was not functional - when making a phone call there was "no connection available" when in the "phone call screen" .. - The people that called me during the problem heard the ring several times ..but I didn't receive any call or msg on the phone.. so i was probably connected to the cell network cause my account was receiving calls and they were not redirected to the message box directly.. but on my side the phone didn't ring nor receive msg -> I have tried to use plane mode on/off / changing the sim card /reboot ... nothing worked .. then after some times it returned to normal ... The main problem here is that you consider that the phone is working cause you see the triangle icon full in the indicator bar ... But you don't receive the phone calls ... like if you were ignoring phone calls Yesterday I found a way to reproduce the bug ... and the workaround that makes the telephony-service work again after the bug how to reproduce the problem : 1. put wifi off and phone data off (2g/3g/4g) telephony triangle icon is filled 2. restart the phone 3. after restart the phone indicator bar shows full GSM cover with the triangle icon filled. 4. if you go in the phone dialer ... you have no network .. you can't make phone call .. and you can't receive phone calls nor sms Workaround: (to get your gsm back to normal) - to make the telephony work again : it's odd put you must only put wifi "on" from the indicator bar then telephony is functional again... and you get the operator name in phone app Kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1487632/+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 1385889] Re: Graphical interface freezes.
I agree, the entire interface freezes and I can not seem to give any keyboard or mouse input without restarting. -- 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/1385889 Title: Graphical interface freezes. Status in “xorg” package in Ubuntu: Confirmed Bug description: Graphical interface freezes some time after switching from Intel Gpu to the discrete graphics card Nvidia GeForce 720M. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 26 17:05:04 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed nvidia-331-updates, 331.89, 3.16.0-23-generic, x86_64: installed nvidia-331-updates-uvm, 331.89, 3.16.0-23-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-23-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2014-10-23 (2 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=ru_RU.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed root=UUID=92b225c1-0807-4944-8b18-4a5672bebec2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sun Oct 26 16:51:54 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 987 vendor LGD xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1385889/+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 1360246] Re: Crash / can not access Printer Configuration - Server Settings
It seems fixed since cups 1.5.3-0ubuntu8.5, no crash until now since the upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1360246 Title: Crash / can not access Printer Configuration - Server Settings Status in “cups” package in Ubuntu: Confirmed Status in “system-config-printer” package in Ubuntu: Confirmed Status in “system-config-printer-kde” package in Ubuntu: Confirmed Bug description: Can not access Server Settings in Printer Configuration. First try will introduce crash. Next try will generates pop up box with error message: "The password maybe incorrect" I realized this problem since using fresh install Kubuntu 12.04.5 x86, latest update also has this problem. But it's not happen while I tested Kubuntu 12.04.3 x86. If running from console: $ /usr/bin/kcmshell4 system-config-printer-kde Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. KDE Daemon (kded) already running. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... Traceback (most recent call last): File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 437, in on_tvMainList_cursor_changed self.fillServerTab() File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 1790, in fillServerTab self.ui.tvMainList.get_selection().unselect_all() AttributeError: 'PyKcm' object has no attribute 'tvMainList' Problem not occured if using root access (sudo). $ uname -a Linux kubuntu-3 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1360246/+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 1360246] Re: Crash / can not access Printer Configuration - Server Settings
** Project changed: cups => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1360246 Title: Crash / can not access Printer Configuration - Server Settings Status in Unofficial Package Updates for Kubuntu: New Status in “cups” package in Ubuntu: New Status in “system-config-printer-kde” package in Ubuntu: New Bug description: Can not access Server Settings in Printer Configuration. First try will introduce crash. Next try will generates pop up box with error message: "The password maybe incorrect" I realized this problem since using fresh install Kubuntu 12.04.5 x86, latest update also has this problem. But it's not happen while I tested Kubuntu 12.04.3 x86. If running from console: $ /usr/bin/kcmshell4 system-config-printer-kde Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. KDE Daemon (kded) already running. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... Traceback (most recent call last): File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 437, in on_tvMainList_cursor_changed self.fillServerTab() File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 1790, in fillServerTab self.ui.tvMainList.get_selection().unselect_all() AttributeError: 'PyKcm' object has no attribute 'tvMainList' Problem not occured if using root access (sudo). $ uname -a Linux kubuntu-3 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1360246/+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 1360246] Re: Crash / can not access Printer Configuration - Server Settings
Just tested cups 1.5.3-0ubuntu8.3 -> works as expected So that problem introduced since cups 1.5.3-0ubuntu8.4 (I also experienced unstable system with this version, random crash in other area) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1360246 Title: Crash / can not access Printer Configuration - Server Settings Status in Unofficial Package Updates for Kubuntu: New Status in “cups” package in Ubuntu: New Status in “system-config-printer-kde” package in Ubuntu: New Bug description: Can not access Server Settings in Printer Configuration. First try will introduce crash. Next try will generates pop up box with error message: "The password maybe incorrect" I realized this problem since using fresh install Kubuntu 12.04.5 x86, latest update also has this problem. But it's not happen while I tested Kubuntu 12.04.3 x86. If running from console: $ /usr/bin/kcmshell4 system-config-printer-kde Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. KDE Daemon (kded) already running. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... Traceback (most recent call last): File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 437, in on_tvMainList_cursor_changed self.fillServerTab() File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 1790, in fillServerTab self.ui.tvMainList.get_selection().unselect_all() AttributeError: 'PyKcm' object has no attribute 'tvMainList' Problem not occured if using root access (sudo). $ uname -a Linux kubuntu-3 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1360246/+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 1360246] Re: Crash / can not access Printer Configuration - Server Settings
Also happen in Ubuntu 12.04 gnome ** Project changed: kubuntu-ppa => system-config-printer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1360246 Title: Crash / can not access Printer Configuration - Server Settings Status in “cups” package in Ubuntu: New Status in “system-config-printer” package in Ubuntu: New Status in “system-config-printer-kde” package in Ubuntu: New Bug description: Can not access Server Settings in Printer Configuration. First try will introduce crash. Next try will generates pop up box with error message: "The password maybe incorrect" I realized this problem since using fresh install Kubuntu 12.04.5 x86, latest update also has this problem. But it's not happen while I tested Kubuntu 12.04.3 x86. If running from console: $ /usr/bin/kcmshell4 system-config-printer-kde Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. KDE Daemon (kded) already running. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... Traceback (most recent call last): File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 437, in on_tvMainList_cursor_changed self.fillServerTab() File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 1790, in fillServerTab self.ui.tvMainList.get_selection().unselect_all() AttributeError: 'PyKcm' object has no attribute 'tvMainList' Problem not occured if using root access (sudo). $ uname -a Linux kubuntu-3 3.2.0-67-generic-pae #101-Ubuntu SMP Tue Jul 15 18:04:54 UTC 2014 i686 i686 i386 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1360246/+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 1317449] Re: Please update to a version > 3.8.2
Please fix that ASAP, I can't really use digikam anymore due to it... ** Changed in: sqlite3 (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1317449 Title: Please update to a version > 3.8.2 Status in digiKam - digital photo management: Won't Fix Status in SQLite: Won't Fix Status in “sqlite3” package in Ubuntu: Confirmed Bug description: According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 3.8.2 causes crashes in digikam (and possibly other software) in various situations. There are several reports, that versions > 3.8.2 fix the issue. I'm using the 3.8.4.3 package from debian testing right now and can't trigger crashes anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/digikam/+bug/1317449/+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 997269] Re: dovecot imap broken by apparmor policy
** Bug watch added: Debian Bug tracker #732184 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732184 ** Also affects: apparmor (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732184 Importance: Unknown Status: Unknown -- 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/997269 Title: dovecot imap broken by apparmor policy Status in “apparmor” package in Ubuntu: Expired Status in “dovecot” package in Ubuntu: Invalid Status in “apparmor” package in Debian: Unknown Bug description: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor="ALLOWED" operation="getattr" parent=10922 profile="/usr/sbin/dovecot//null-107 //null-10b//null-118" name="/home/foobar/Maildir/.foobar/dovecot.index.log" pid=10937 comm="imap" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has "flags=(complain)", but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the "usr.lib.dovecot.imap" policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in "complain" mode. What are these "//null-NNN/" strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) Package: apparmor 2.7.102-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Tags: precise Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+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 997269] Re: dovecot imap broken by apparmor policy
** Changed in: apparmor (Ubuntu) Status: Expired => Incomplete -- 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/997269 Title: dovecot imap broken by apparmor policy Status in “apparmor” package in Ubuntu: Incomplete Status in “dovecot” package in Ubuntu: Invalid Status in “apparmor” package in Debian: Confirmed Bug description: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor="ALLOWED" operation="getattr" parent=10922 profile="/usr/sbin/dovecot//null-107 //null-10b//null-118" name="/home/foobar/Maildir/.foobar/dovecot.index.log" pid=10937 comm="imap" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has "flags=(complain)", but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the "usr.lib.dovecot.imap" policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in "complain" mode. What are these "//null-NNN/" strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) Package: apparmor 2.7.102-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Tags: precise Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+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 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Thank you for taking the time to report this bug and helping to make Ubuntu (Studio) better. @Bluesbrother (or the original posted to askubu..) Can you please add what your installation media was, ie. `cat /var/log/installer/media-info` as your original post on askubu implies you release-upgraded to noble, and thus this issue may only occur on upgrades, rather than fresh installs. Ideally an `apport-collect` would gather this (& more details), but you aren't the original report of this bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 2055270] Re: Buy Tramadol Online At Lowest Prices
requested delete via https://answers.launchpad.net/launchpad/+question/709435 -- 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/2055270 Title: Buy Tramadol Online At Lowest Prices Status in systemd package in Ubuntu: Invalid Bug description: Buy Tramadol Online 100mg USA Overnight ➤Order here: https://t.ly/N0hN9 ➤Shop Here: https://t.ly/N0hN9 Tramadol 100mg may interact with other medications, including certain antidepressants, antipsychotics, and medications that affect serotonin levels. It's important to inform your healthcare provider about all medications you are taking, including prescription, over-the-counter, and herbal supplements, to avoid potential interactions. Tramadol should not be used in combination with alcohol or other substances that depress the central nervous system, as this can increase the risk of respiratory depression and other serious side effects. People with a history of substance abuse or addiction should use tramadol with caution, as it has the potential for misuse, dependence, and addiction. Tramadol is not recommended for use in children under the age of 12, as its safety and efficacy in this population have not been established. Older adults may be more sensitive to the side effects of tramadol, particularly dizziness and drowsiness, and may require lower doses or closer monitoring. It's essential to follow your healthcare provider's instructions carefully when taking tramadol 100mg and to report any side effects or concerns promptly. Additionally, do not stop taking tramadol suddenly without consulting your doctor, as this can lead to withdrawal symptoms. If you have any questions or uncertainties about tramadol or its use, don't hesitate to discuss them with your healthcare provider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055270/+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 2055418] Re: autoinstall crashing on 24.04 desktop daily build
Hi, Thanks for your report and providing some logs! Could you try the install again and run `sudo apport-cli -u 2055418 -c /var/crash/*.crash` in the terminal? This should collect a bit more information and dump it here so we can investigate further. Thank you, Chris ** Also affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: New Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+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 2057944] Re: pidwait doesn't work. Instead behaves like pgrep
This is the case for jammy - for numbat the pwait -> pidwait change has happened upstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2057944 Title: pidwait doesn't work. Instead behaves like pgrep Status in procps package in Ubuntu: New Bug description: pidwait doesn't work at all. Seems like pidwait was renamed in an Ubuntu patch from upstream pwait - however the executable that is built acts as "pgrep" unless it's called as "pwait"; this check also needs to be updated with the executable name "pidwait". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+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 2057944] [NEW] pidwait doesn't work. Instead behaves like pgrep
Public bug reported: pidwait doesn't work at all. Seems like pidwait was renamed in an Ubuntu patch from upstream pwait - however the executable that is built acts as "pgrep" unless it's called as "pwait"; this check also needs to be updated with the executable name "pidwait". ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2057944 Title: pidwait doesn't work. Instead behaves like pgrep Status in procps package in Ubuntu: New Bug description: pidwait doesn't work at all. Seems like pidwait was renamed in an Ubuntu patch from upstream pwait - however the executable that is built acts as "pgrep" unless it's called as "pwait"; this check also needs to be updated with the executable name "pidwait". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2057944/+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 2058310] [NEW] Dummy output with Celeron Silver audio
Public bug reported: Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there is no sound. I believe the CPU sound unit is essx-8336. Many people have reported similar problems, with the system sound being "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do work with this machine, as does the Win 11 dual boot, so the hardware works. Will this problem be fixed in version 24.04? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 21:29:33 2024 InstallationDate: Installed on 2024-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2058310 Title: Dummy output with Celeron Silver audio Status in alsa-driver package in Ubuntu: New Bug description: Built in speakers have alsa driver as sof-audio-pci-intel-apl, but there is no sound. I believe the CPU sound unit is essx-8336. Many people have reported similar problems, with the system sound being "dummy output". My bluetooth ear buds do work. Endeavour-OS and Fedora 39 live images do work with this machine, as does the Win 11 dual boot, so the hardware works. Will this problem be fixed in version 24.04? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 21:29:33 2024 InstallationDate: Installed on 2024-03-11 (7 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-16T20:22:40.610992 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2058310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packa
[Touch-packages] [Bug 2058435] [NEW] After recent update, pulseaudio crashes
Public bug reported: Intel ALC269VB Analog worked fine until today's update. Now all I get is "dummy output" and after running ubuntu-bug, the diagnostic says that pulseaudio has crashed. Reloading does not help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_46_49_generic_97 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 22:28:54 2024 InstallationDate: Installed on 2018-12-04 (1932 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2058435 Title: After recent update, pulseaudio crashes Status in pulseaudio package in Ubuntu: New Bug description: Intel ALC269VB Analog worked fine until today's update. Now all I get is "dummy output" and after running ubuntu-bug, the diagnostic says that pulseaudio has crashed. Reloading does not help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_46_49_generic_97 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 19 22:28:54 2024 InstallationDate: Installed on 2018-12-04 (1932 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd07/02/2018:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:sku: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2058435/+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 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2059872 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration Status in openssh package in Ubuntu: New Bug description: Recently introduced sshd-socket-generator for socket activation in openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or ListenAddress entries in the sshd configuration. If you have multiple Port or ListenAddress and one of them is for port 22, it just skips it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+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 2060080] [NEW] 23.13.9-2ubuntu5 is FTBFS on armhf
Public bug reported: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz ** Affects: accountsservice (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Changed in: accountsservice (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf Status in accountsservice package in Ubuntu: In Progress Bug description: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+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 2060080] Re: 23.13.9-2ubuntu5 is FTBFS on armhf
So something changed to add -Werror=implicit-function-declaration at build time (gcc didn't change so maybe dpkg?), which should have caused the other arches to fail as well but since they ran at different times they pulled different versions of build dependencies. This will likely get fixed on a rebuild and these are getting queued en masse, so I'm marking as invalid unless we have a reason to track this later. ** Changed in: accountsservice (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2060080 Title: 23.13.9-2ubuntu5 is FTBFS on armhf Status in accountsservice package in Ubuntu: Invalid Bug description: The armhf build fails with the following build error: ../subprojects/mocklibc-1.0/src/netgroup-debug.c: In function ‘netgroup_debug_print_entry’: ../subprojects/mocklibc-1.0/src/netgroup-debug.c:25:3: error: implicit declaration of function ‘print_indent’ [-Werror=implicit-function-declaration] 25 | print_indent(stream, indent); | ^~~~ cc1: some warnings being treated as errors See the logs here: https://launchpadlibrarian.net/722843641/buildlog_ubuntu-noble- armhf.accountsservice_23.13.9-2ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2060080/+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 2060335] [NEW] upower/1.90.2-8build3 autopkgtest failure on arm64
Public bug reported: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz ** Affects: upower (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Tags: update-excuse ** Description changed: - autopkgtests fail, only on arm64, with the following output: + autopkgtests fail, only on arm64, after a no-change-rebuild, with the + following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' - 689s + 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 - 689s + 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 - 689s + 689s 689s -- 689s Ran 66 tests in 194.378s - 689s + 689s 689s FAILED (fai
[Touch-packages] [Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
I estimate another ncr could fix the issue. Building and testing in a ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: In Progress Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+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 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
Yes, a no-change rebuild fixes the issue. Please see attached debdiff for the fix. I have provided a PPA with the build and tests: PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower arm64 autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/log.gz arm64 autopkgtests artifacts: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/artifacts.tar.gz ** Patch added: "upower_1.90.2-8build3_1.90.2-8build4.debdiff" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+attachment/5762206/+files/upower_1.90.2-8build3_1.90.2-8build4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: In Progress Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+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 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
That works! Thanks Andreas. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 Status in upower package in Ubuntu: Fix Committed Bug description: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+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 2061327] Re: 24.04 beta hangs at desktop
duplicate filing of https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061326 ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061327 Title: 24.04 beta hangs at desktop Status in mesa package in Ubuntu: Invalid Bug description: I have a Thinkpad T510 dual boot windows and Ubuntu Budgie 22.04 Booting the 24.04 Ubuntu Budgie livecd, I notice that instead of the nice desktop graphics for Budgie I get a text line saying Ubuntu Budgie 24.04. Then when the desktop finally loads the liveCD locks up tight. Only a hard reset works. I have tried the Ubuntu 24.04 beta with same results. If I take the boot option "safe graphics" the live cd session loads correctly and does not hang. /$ inxi -FZRa System: Host: rob-ThinkPad-T510 Kernel: 6.8.0-11-generic arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=35c54a5b-4746-419b-a598-d3d408c9066a ro quiet splash vt.handoff=7 Desktop: Budgie v: 10.9.1 tk: GTK v: 3.24.41 wm: budgie-wm with: budgie-panel,plank tools: gnome-screensaver,gsd-screensaver-proxy dm: LightDM v: 1.30.0 Distro: Budgie 24.04 LTS (Noble Numbat) base: Ubuntu Machine: Type: Laptop System: LENOVO product: 4384AJ9 v: ThinkPad T510 serial: Chassis: type: 10 serial: Mobo: LENOVO model: 4384AJ9 serial: uuid: BIOS: LENOVO v: 6MET92WW (1.52 ) date: 09/26/2012 Battery: ID-1: BAT0 charge: 47.8 Wh (97.8%) condition: 48.9/47.5 Wh (103.0%) volts: 11.7 min: 10.8 model: LGC 42T4848 type: Li-ion serial: 39414 status: discharging Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 serial: 22-c2-4c-cc charge: 55% (should be ignored) rechargeable: yes status: discharging CPU: Info: model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6 model-id: 0x25 (37) stepping: 2 microcode: 0x11 Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB Speed (MHz): avg: 1720 high: 2667 min/max: 1199/2667 boost: enabled scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1199 2: 2667 3: 1553 4: 1463 bogomips: 21280 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports: active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300 Display: x11 server: X.Org v: 21.1.11 compositor: budgie-wm driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31") Monitor-1: LVDS-1 model: Lenovo 0x40b0 built: 2010 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6") ratio: 16:9 modes: 1366x768 API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus inactive: gbm,wayland API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.0.3-1ubuntu3 glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (ILK) device-ID: 8086:0046 memory: 1.46 GiB unified: yes Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 5 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56 class-ID: 0403 API: ALSA v: k6.8.0-11-generic status: kernel-api tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin tools: pw-cat,pw-cli,wpctl Network: Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e
[Touch-packages] [Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
Hi Jeff, apologies for the delay in getting back to you. Based on the crash report provided it looks like it was a bug with the tracker package. I think this should be sorted by now though! ** Changed in: subiquity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build Status in subiquity: Invalid Status in tracker package in Ubuntu: New Bug description: Classis 24.04 Daily build 02-28-2024 AMD64 Using the following autoinstall user-data file, the installer crashes as soon as it loads in the GUI. ``` #cloud-config autoinstall: version: 1 apt: geoip: true preserve_sources_list: false primary: - arches: [amd64, i386] uri: http://archive.ubuntu.com/ubuntu - arches: [default] uri: http://ports.ubuntu.com/ubuntu-ports kernel: package: linux-generic-hwe-22.04 codecs: install: false drivers: install: false oem: install: auto source: id: ubuntu-desktop-minimal search_drivers: false timezone: America/Chicago updates: security identity: hostname: tiny password: $6$NtXwPsM/enBpRMOS$lxsTsJPuSzovFVWJdN3TF89yaqVzLTeqthUD8feRljnTs6EENgkOqttrkd3fiNWJFqRqi.5/m7RUi6.IgKkwb0 username: ubuntu keyboard: layout: us toggle: null variant: '' locale: en_US #refresh-installer: # update: yes storage: layout: name: hybrid encrypted: yes ssh: allow-pw: true install-server: true authorized-keys: - [key-1] - [key-2] ``` An ubuntu GUI crash report window appears, saying that the process /usr/libexec/tracker-extract-3 is what crashed. Attached is the entirety of the /var/log/installer directory. This same autoinstall file used in conjunction with a 23.10.1 ISO works perfectly fine. TPM+FDE and all. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+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 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@trurl42, does the sound used to work before (older kernel than 6.5)? >From the kernel log, the line out has no trivial problem. I need to know is >this a regression or something else. Thanks [5.221075] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [5.221080] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) -- 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/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822
Booted an install made earlier today on hp_compaq_dc7700 of lubuntu noble (20240424) ; https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300235/testcases/1701/results/ sudo apt update; sudo apt full-upgrade & no updates are available. (software-properties-qt 0.99.48.1) Following the "Intended Functionality" listed in the Bug.Description at the top of this bug report and behavior is what I'd expect. The `/etc/apt/sources.list` file contained comments only ; with all subsequent changes being reflected in `/etc/apt/sources.list.d/ubuntu.sources` and looked appropriate to me. However I'm tired, and fear I've missed something (that I can't 'put my finger on'), but I've repeated steps 1..7 twice & didn't locate what 'irks' me sorry. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-properties source package in Noble: Confirmed Bug description: [ Impact ] Ubuntu 24.04 now uses deb822 to represent software sources for deb packages, instead of /etc/apt/sources.list. The complete rationale for this change can be found here: https://discourse.ubuntu.com/t/spec- apt-deb822-sources-by-default/29333 software-properties has two graphical frontends for editing these software sources, one is GTK-based and the other is Qt-based. When the underlying change to deb822 sources was made, the GTK-based frontend and the DBus backend interface gained support. The original bug report shown below informed us of the lack of deb822 support in the Qt frontend, which results in a broken, non-functional interface when attempting to view or edit most values on the first two tabs. The fix for this is to implement a Qt dialog for deb822 sources that somewhat matches the existing GTK interface. [ Test Plan ] Install software-properties-qt 0.99.48 or earlier. Reproducing the bug: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. 3. Move to the Other Software tab and observe that there are no items in the list. Upgrade to software-properties-qt 0.99.49. Intended functionality: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. 4. Switch to the Other Software tab, there should be one item in the list. 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. [ Where problems could occur ] This is well-tested code. That being said, the following small edge cases exist: - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. In a future update, this functionality could be broken by one or more of the following underlying changes: - Changes to the software-properties backend which are only implemented for the GTK frontend. - Changes to the location or formatting of the ubuntu.sources file. - Regressions in the Python bindings for Qt 5, which are rare but possible. - Regressions in Python itself. [ Other Info ] Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. [ Original Report ] Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.9
[Touch-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@ Paramvir Could you try new kernel and update the information? Thanks ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- 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/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+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 2063545] Re: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/2063545 Title: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1 Status in click package in Ubuntu: New Bug description: I was updating to new unity sorry i really dont know i am newbie ProblemType: Package DistroRelease: Ubuntu 24.04 Package: click 0.5.2-2ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 25 21:27:28 2024 ErrorMessage: new click package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-11 (75 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: click Title: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2063545/+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 1926139] Re: dhclient doesn't receive dhcp offer from kernel
** Attachment added: "sequential test" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5593046/+files/test-sequential.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient doesn't receive dhcp offer from kernel Status in isc-dhcp package in Ubuntu: New Bug description: Platform: Qemu/libvirt on AMD64 Ubuntu version: 20.04 isc-dhcp-client version: 4.4.1-2.1ubuntu5 Problem: When dhclient is used during boot every few reboots the DHCP OFFER packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no read event is triggered. Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still occurs. So this issue might also be kernel related. Attached diff shows a strace of all threads and a pcap showing the tcpdump output. Edit: - Sometimes the dhclient command does receive the OFFER packet and connection is restored. - In my testing running dhclient manually from the terminal when the OFFERs aren't received will result in a new dhclient session which does receive the OFFER packet and connection is restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+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 1926139] Re: dhclient doesn't receive dhcp offer from kernel
We've been investigating a similar issue in Ubuntu 20.04 (and now 22.04) on Azure where Running PPS re-use fails to perform DHCP for 5 minutes when dhclient is invoked by cloud-init. dhclient is run by cloud-init, but sees no DHCPOFFER. It varies due to unknown reasons but it has affected a ~0.3-2% of deployments in this scenario over time. We instrumented our images to capture network traffic and see what is happening and sure enough DHCP offers are coming through to the guest by dhclient doesn't see them. We instrumented dhclient and the "got_one()" callback is never invoked in these failures. 18.04 does not have this issue. This behavior can be reproduced multiple ways: - Reproduce similar test environment to above scenario using cloud-init (switch hyperv nic to a different vnet while waiting the link status to reset, then perform dhcp). This test case will reproduce in ~1,500 runs, though it varies and requires more complex setup. - Repeatedly run dhclient in a loop until it fails (see test-sequential.sh). It may take a while, but even this simple test will reproduce this behavior in ~50k runs for me in an LXD VM. - Simply launch instances of dhclient in parallel (see test-parallel.sh). There is an excellent chance at least one of those dhclients will fail this way. I noticed the uprev of bind9 libs in focal: focal (net): 1:9.11.16+dfsg-3~build1 focal-updates (net): 1:9.11.16+dfsg-3~ubuntu1 impish (net): 1:9.11.19+dfsg-2.1ubuntu1 jammy (net): 1:9.11.19+dfsg-2.1ubuntu3 kinetic (net): 1:9.11.19+dfsg-2.1ubuntu3 I couldn't find any related issue on the isc-dhcp tracker, etc. I did build dhclient from the Debian master branch (https://salsa.debian.org/debian/isc-dhcp/-/commits/master/debian) which uses the in-tree bind libs and that seems to have addressed the issue for all scenarios. Not that it helps much to bisect this just yet. ** Attachment added: "parallel test" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5593045/+files/test-parallel.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient doesn't receive dhcp offer from kernel Status in isc-dhcp package in Ubuntu: New Bug description: Platform: Qemu/libvirt on AMD64 Ubuntu version: 20.04 isc-dhcp-client version: 4.4.1-2.1ubuntu5 Problem: When dhclient is used during boot every few reboots the DHCP OFFER packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no read event is triggered. Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still occurs. So this issue might also be kernel related. Attached diff shows a strace of all threads and a pcap showing the tcpdump output. Edit: - Sometimes the dhclient command does receive the OFFER packet and connection is restored. - In my testing running dhclient manually from the terminal when the OFFERs aren't received will result in a new dhclient session which does receive the OFFER packet and connection is restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+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 1977676] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1977676 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: kmod:amd64: Install libkmod2:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 5 08:55:45 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-24 (527 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977676/+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 1977683] Re: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Lubuntu has used sddm for all LXQt releases (ie. since Lubuntu 18.10), and the upgrade from an release that used lightdm/LXDE is unsupported due to breakage as was warned about in documentation, eg. https://lubuntu.me/focal-2-released/ "Note, due to the extensive changes required for the shift in desktop environments, the Lubuntu team does not support upgrading from 18.04 or below to any greater release. Doing so will result in a broken system. If you are on 18.04 or below and would like to upgrade, please do a fresh install." The error you are describing is a user-created issue by using unsupported upgrade procedures that were documented as creating issues later, and this is warned about breakage. The fresh install would have prevented this. As such I've marked this bug report as "opinion". If you believe I'm in error, please leave a comment explaining why and the bug report can then be returned to "New" (you may find it'll then be marked as "Won't Fix") ** Changed in: lightdm (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1977683 Title: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04 Status in lightdm package in Ubuntu: Opinion Bug description: Hi, I have updated several machines from Lubuntu 20.04 to Lubuntu 22.04 with do-release-update -d On all but one machine this worked well, but one machine, that formerly worked without problems, now has no ssh-agent running after login, and the ~/.xsession-errors shows several xsession files to fail for the same reason: /etc/X11/Xsession.d/30x11-common_xresources: Zeile 16: has_option: Befehl nicht gefunden /etc/X11/Xsession.d/75dbus_dbus-launch: Zeile 9: has_option: Befehl nicht gefunden /etc/X11/Xsession.d/90x11-common_ssh-agent: Zeile 9: has_option: Befehl nicht gefunden (german for: has_option: command not found) Formerly mentioned in bug #1922414 (marked as solved) and its duplicate #1940779 , but it isn't solved. That's why there is no ssh-agent. I have done some debugging to find, why it works on all but one of my machines, and what's the reason. Reason: has_option is not a command, but a shell function defined in /etc/X11/Xsession On the good machines, the display manager is sddm, which seems to do the job well. The machine, that fails, is somewhat older and had formerly 18.04 running and been updated to 20.04 then. It runs the display manager lightdm. That's the problem: lightdm runs /usr/bin/lxqt-session and /usr/bin/lxqt-session directly opens and executes the scripts in /etc/X11/Xsession.d without running /etc/X11/Xsession. Therefore, the shell function has_optionis never defined, but used in the scripts, which do fail then. Therefore, either lxqt-session needs to be made compatible with /etc/X11/Xsession, or the upgrade-procedure 20.04 to 22.04 must replace lightdm by sddm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Jun 5 14:48:42 2022 InstallationDate: Installed on 2018-04-28 (1498 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: Upgraded to jammy on 2022-06-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1977683/+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 1978316] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Went to execute update. Got the report ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 10 14:19:09 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1978316 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Went to execute update. Got the report ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 10 14:19:09 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.8 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1978316/+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 1978380] Re: External monitor not detected
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: xorg (Ubuntu) => linux (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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: New Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+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
