[Touch-packages] [Bug 1797893] Re: batter management is not working properly on mac air
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- 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/1797893 Title: batter management is not working properly on mac air Status in upower package in Ubuntu: Expired Bug description: battery status can not be trigger instantly when cable are wired or not. the volume of current battery is wrong. unable to charging properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1797893/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
uname -a: Linux Imagined 4.20.17-042017-generic NVIDIA Driver Version: 418.56 Resumed 3 times from sleep with the 4.20 kernel, so far sound is working fine. Sometimes the issues does not appear until the next day (warm vs cold hw?), so I will report back tomorrow. If sound works for next few days, I will try editing /proc/modprobe.d /alsa-base.conf and reboot into the 5.0 kernel. -- 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/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1823583] Re: Xorg freeze ( also Nvidia freeze (tested) )
Next time a freeze happens, restart the system and then run this command to collect the log from the previous (frozen) boot: journalctl -b-1 > prevboot.txt and then send us the file 'prevboot.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- 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/1823583 Title: Xorg freeze ( also Nvidia freeze (tested) ) Status in Ubuntu: Incomplete Bug description: Hi, I have been using Ubuntu 14.04 LTS for 6 years without problem and I decided to renew my operating system to Ubuntu 18.04 LTS with fresh install 5 months ago. When I started to use ubuntu 18.04 LTS, I encountered some desktop freezes randomly. While it was happening, I can heart that my laptop's fan noise was incredibly increasing abnormally at that moment. So I have decided to change my driver from X.org Server to Nvidia (recommended). When I switch my driver from open source graphic driver to proprietary graphic driver, I hoped that the problem might be solved. But after a week, the problem occured again. After that in the same day the same freezes occur continuosly as much as 3 or 4 times. I don't know why it happens. The only thing I know is Ubuntu 14.04 LTS was using Unity Desktop, and Ubuntu 18.04 LTS is using GNOME Desktop anymore. I tried to alt + f2 and r command to refresh gnome desktop. Also ctrl + alt + f3 for instance, and typing gnome-shell --replace & disown to refresh gnome dektop. They sometimes works, but only if I notice early that the freezes coming. If I miss that moment, the screen completely freezes and neither cursor click nor keyboard input works What should I do? 1) & 2) My system info: = Description: Ubuntu 18.04.2 LTS Release: 18.04 Ubuntu Software: 3.28.1 = 3) I shouldn't have had to restart my system again, again and again due to desktop freezes. While it happens, session cannot be rescued. It damages my personal / work data on the RAM at that moment. I mean I encountered data loss a lot of times on the gedit or the web browser mostly, while writing or doing something. I was expecting this issue was reported someone in the internet since 5 months. Because of this, I didn't deal with it. But I guess so this is not common issue. Because, there is no patch for it. I am looking details of system update when it has come each time, but no patch there until this now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 04:35:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-46-generic, x86_64: installed nvidia, 390.116, 4.15.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0817] Subsystem: Dell GM108M [GeForce MX130] [1028:0817] InstallationDate: Installed on 2018-11-02 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0c45:6717 Microdia Bus 001 Device 002: ID 1038:1707 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=880beb69-81b9-441e-bd97-f469b15dab9f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0RMKK4 dmi.board.vendor: Dell Inc. dmi.board.ve
[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Tags removed: raring saucy ** Summary changed: - Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair + Creative Recon3d & Sound Blaster Z (CA0132), No sound at all -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No sound at all Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: 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:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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 1823572] Re: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all
This sounds like bug 1166529, but I am hesitant to mark any bug a duplicate of that because if it's a port routing issue then that's unique to the motherboard model and not unique to the sound chip. -- 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/1823572 Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound output. I don't see the CA0132 devices listed in the sound settings GUI either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: archeetos 1879 F pulseaudio /dev/snd/controlC1: archeetos 1879 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:04:20 2019 InstallationDate: Installed on 2017-03-18 (749 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1476 F pulseaudio archeetos 1879 F pulseaudio /dev/snd/controlC1: gdm1476 F pulseaudio archeetos 1879 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to bionic on 2019-04-07 (0 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22m dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22m:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 7 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1823572/+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 1823573] Re: Bluetooth headset not available as output device
Please try some older kernels (like 4.18 which was in Ubuntu 18.10) and tell us if that fixes the problem: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Changed in: alsa-driver (Ubuntu) Status: New => 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/1823573 Title: Bluetooth headset not available as output device Status in alsa-driver package in Ubuntu: Incomplete Bug description: Connecting my Bluetooth headset (Beoplay H8) appears to be working, and everything looks correct in the Bluetooth settings: However, the headset is not listed under "Output devices" in the sound menu after connecting, and all sounds are channeled through the built-in speakers. Media buttons on the headset are also rendered useless, not that there would be much use for them without sound anyways. Still worth noting, as everything including media buttons worked perfectly in 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stein 2603 F pulseaudio /dev/snd/pcmC0D0c: stein 2603 F...m pulseaudio /dev/snd/pcmC0D0p: stein 2603 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 23:00:38 2019 InstallationDate: Installed on 2018-05-09 (332 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN16WW(V2.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1823573/+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 1823573] Re: Bluetooth headset not available as output device
Thanks for the bug report. The intermediate sound layer (PulseAudio) hasn't changed between 18.10 and 19.04 so this is either going to be a kernel problem or a GUI problem (gnome-control-center). -- 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/1823573 Title: Bluetooth headset not available as output device Status in alsa-driver package in Ubuntu: Incomplete Bug description: Connecting my Bluetooth headset (Beoplay H8) appears to be working, and everything looks correct in the Bluetooth settings: However, the headset is not listed under "Output devices" in the sound menu after connecting, and all sounds are channeled through the built-in speakers. Media buttons on the headset are also rendered useless, not that there would be much use for them without sound anyways. Still worth noting, as everything including media buttons worked perfectly in 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stein 2603 F pulseaudio /dev/snd/pcmC0D0c: stein 2603 F...m pulseaudio /dev/snd/pcmC0D0p: stein 2603 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 23:00:38 2019 InstallationDate: Installed on 2018-05-09 (332 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN16WW(V2.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1823573/+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 1261211] Re: No multichannel support on Creative CA0132
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1261211 Title: No multichannel support on Creative CA0132 Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Multichannel sound is not working on my Creative CA0132 sound card. Stereo is working just fine but I cannot get 5.1 to work. when I run 'speaker-test -c 6' sound only comes out of the front 2 speakers and if I add '-Dsurround51' it returns "Channels count (6) not available for playbacks: Invalid argument". My alsa info http://www.alsa- project.org/db/?f=3a5ca77035da6be08769128daa43dcbc59badb93 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: somedude 1605 F lxpanel somedude 4927 F firefox /dev/snd/pcmC0D0p: somedude 4927 F...m firefox /dev/snd/timer: somedude 4927 f firefox Date: Sun Dec 15 15:58:33 2013 InstallationDate: Installed on 2013-12-15 (0 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: Z87 Professional dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Professional:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1261211/+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 1243056] Re: Master Volume Ignored on Recon3D (CA0132) With Alsamixer/PA
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- 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/1243056 Title: Master Volume Ignored on Recon3D (CA0132) With Alsamixer/PA Status in alsa-driver package in Ubuntu: Won't Fix Bug description: It began when I installed gnome-shell from a minimal CD in Ubuntu 13.10, then I wasn't able to change volume with the volume slider which controls ALSA's Master control, but after installing the rest of ubuntu-desktop I completely lost sound on my Recon3D. I tried installing Ubuntu 13.10 again and still wasn't able to get any sound at all as soon as I installed the rest of ubuntu-desktop. I decided to go back to Ubuntu 13.04 with a fresh install, but although I can get sound with my Recon3D here 100% of the time, I cannot get the master volume controls to work. You can raise and lower them in alsamixer but they simply won't have any effect. Similarly, you can enable/disable some features in alsamixer and they won't have any effect, even though before they worked fine. However, if I switch to HDMI audio, the master control works, so the problem is with how alsa ignores various options in my Recon3D ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.12.0-031200rc5-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Oct 22 01:13:56 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm 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: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1243056/+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 1043621] Re: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1043621
Title:
[M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
Status in alsa-driver package in Ubuntu:
Won't Fix
Bug description:
Originally there was no sound, I modified the file /etc/modprobe.d
/alsa-base.conf adding the following: "snd-hda-intel index=0
model=intel" and now I have sound (maybe that model is not the best
option), but when I plug the headphones there is sound from the
speakers and the headphones. I installed gnome alsa mixer but it
doesn't open. thanks
using ubuntu 12.04.1 LTS
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gerardo1836 F pulseaudio
/dev/snd/pcmC0D0p: gerardo1836 F...m pulseaudio
Card0.Amixer.info:
Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1:
amixer: Mixer load hw:0 error: Invalid argument
Card hw:0 'PCH'/'HDA Intel PCH at 0xd271 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:11020011,1028057b,00100918
HDA:80862806,1028057b,0010'
Controls : 27
Card0.Amixer.values: Error: command ['amixer', '-c', '0'] failed with exit
code 1: amixer: Mixer hw:0 load error: Invalid argument
Date: Wed Aug 29 21:42:38 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No auto-mute between outputs
Symptom_amixerStderr: a m i x e r : M i x e r h w : P C H l o a d e r
r o r : I n v a l i d a r g u m e n t
Title: [M17xR4, Creative CA0132, Green Headphone Out, Front] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Alienware
dmi.bios.version: A02
dmi.board.name: M17xR4
dmi.board.vendor: Alienware
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A02
dmi.modalias:
dmi:bvnAlienware:bvrA02:bd02/08/2012:svnAlienware:pnM17xR4:pvrA02:rvnAlienware:rnM17xR4:rvrA02:cvnAlienware:ct8:cvrA02:
dmi.product.name: M17xR4
dmi.product.version: A02
dmi.sys.vendor: Alienware
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-24T17:11:29.363163
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1043621/+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 1184838] Re: [M14xR2, Creative CA0132, Green Headphone Out, Front] No sound at all
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.
** Tags removed: precise
** Tags added: trusty
--
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/1184838
Title:
[M14xR2, Creative CA0132, Green Headphone Out, Front] No sound at all
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
This bug is on a m14x alienware laptop. I have no sound at all. I have tried
alsamixer and has made no difference. I have
this in syslog on boot
May 27 21:14:02 philip-M14xR2 kernel: [ 33.520418] hda-codec: out of range
cmd 0:0:6:707:fffc
May 27 21:14:02 philip-M14xR2 kernel: [ 33.520860] hda-codec: out of range
cmd 0:0:6:707:fffc
May 27 21:14:02 philip-M14xR2 kernel: [ 33.522722] hda-codec: out of range
cmd 0:0:6:707:fffc
May 27 21:14:02 philip-M14xR2 kernel: [ 33.528097] hda-codec: out of range
cmd 0:0:6:707:fffc
May 27 21:14:02 philip-M14xR2 kernel: [ 33.534398] hda-codec: out of range
cmd 0:0:6:707:fffc
May 27 21:14:02 philip-M14xR2 kernel: [ 33.540062] hda-codec: out of range
cmd 0:0:6:707:fffc
I have tried using previous kernels and that has not worked either.
Other info:
Description: Ubuntu 12.04.2 LTS
Release: 12.04
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-31.52~precise1-generic 3.5.7.11
Uname: Linux 3.5.0-31-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: philip 2112 F pulseaudio
/dev/snd/controlC0: philip 2112 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd271 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:11020011,10280552,00100918
HDA:80862806,10280552,0010'
Controls : 13
Simple ctrls : 6
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xd100 irq 17'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,10280552,00100100'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Mon May 27 21:26:01 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
2112 2112 philipF pulseaudio
/dev/snd/controlC0: philipF pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [M14xR2, Creative CA0132, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2013
dmi.bios.vendor: Alienware
dmi.bios.version: A11
dmi.board.name: M14xR2
dmi.board.vendor: Alienware
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A11
dmi.modalias:
dmi:bvnAlienware:bvrA11:bd01/31/2013:svnAlienware:pnM14xR2:pvrA11:rvnAlienware:rnM14xR2:rvrA11:cvnAlienware:ct8:cvrA11:
dmi.product.name: M14xR2
dmi.product.version: A11
dmi.sys.vendor: Alienware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1184838/+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 1527377] Re: [G1.Sniper Z97, Creative CA0132, Green Line Out, Rear] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- 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/1527377 Title: [G1.Sniper Z97, Creative CA0132, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Using earphones, connected to the amplified port on the motherboard. PC dual boots with Windows 8.1, audio works just fine on Windows. $ inxi -Fi System:Host: Cube Kernel: 4.2.0-21-generic x86_64 (64 bit) Desktop: Gnome 3.16.4 Distro: Ubuntu 15.10 wily Machine: Mobo: Gigabyte model: G1.Sniper Z97 v: x.x Bios: American Megatrends v: F7 date: 04/21/2015 CPU: Quad core Intel Core i7-4790K (-HT-MCP-) cache: 8192 KB clock speeds: max: 4400 MHz 1: 4400 MHz 2: 2013 MHz 3: 4400 MHz 4: 4399 MHz 5: 4400 MHz 6: 4400 MHz 7: 4400 MHz 8: 2936 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Hawaii XT [Radeon R9 290X] Display Server: X.Org 1.17.2 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz GLX Renderer: Gallium 0.4 on AMD HAWAII (DRM 2.43.0, LLVM 3.6.2) GLX Version: 3.0 Mesa 11.0.2 Audio: Card-1 Advanced Micro Devices [AMD/ATI] Hawaii HDMI Audio driver: snd_hda_intel Card-2 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.2.0-21-generic ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anan 1313 F pulseaudio anan 1761 F alsamixer /dev/snd/controlC1: anan 1313 F pulseaudio CurrentDesktop: GNOME Date: Thu Dec 17 22:01:08 2015 InstallationDate: Installed on 2015-12-15 (1 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [G1.Sniper Z97, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: G1.Sniper Z97 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnG1.SniperZ97:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnG1.SniperZ97:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: G1.Sniper Z97 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1527377/+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 1267675] Re: [13.10] Alienware M14xR2 (CA0132) - External headphone/headset/microphone do not work when plugged in
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- 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/1267675 Title: [13.10] Alienware M14xR2 (CA0132) - External headphone/headset/microphone do not work when plugged in Status in alsa-driver package in Ubuntu: Won't Fix Bug description: The Alienware M14xR2 has 3 left-side audio jacks. A headphone jack, and headset jack, and a microphone jack. Audio will play through the internal speakers regardless of whether a device is plugged into any of these jacks, and sound will not play in the headphones regardless of which jack they're plugged into. External microphone does not work when plugged into either jack (microphone jack or headset jack). In sound settings, plugging headphones into the headphones jack does not register any change. When plugged into the headset jack, the "Play sound through" device will change from "Speakers" to "Headphones", but sound is not funneled to the headphones; the sound continues to play through the speakers. Also, in a semi-related note, unplugging the headphones seems to change the output device from "Speakers" to "Digital Output (S/PDIF)", which does not produce any sounds through internal speakers nor headphones/headset. Furthermore, if I run gnome-control-center from terminal to launch System Settings and click Sound, the following messages appear in the terminal: (gnome-control-center:4041): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output (gnome-control-center:4041): sound-cc-panel-WARNING **: active_input_update - couldn't find a stream from the supposed active input I'm trying to get a headset (headphones/microphone) to work well with Ubuntu to support Steam gaming on Linux and Linux gaming in general; having a functioning headset so I can communicate with others via Mumble would be of great help. Thanks for any insight on how to get this working. Have also tried the alsa-daily ppa (dkms) with no luck. lsb_release -rd: Description: Ubuntu 13.10 Release: 13.10 apt-cache policy alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu4 Candidate: 1.0.25+dfsg-0ubuntu4 Version table: *** 1.0.25+dfsg-0ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: earl 1937 F pulseaudio /dev/snd/controlC0: earl 1937 F pulseaudio /dev/snd/pcmC0D0p: earl 1937 F...m pulseaudio Date: Thu Jan 9 20:31:27 2014 InstallationDate: Installed on 2013-11-16 (54 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: GK107 HDMI Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2012 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: M14xR2 dmi.board.vendor: Alienware dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd06/29/2012:svnAlienware:pnM14xR2:pvrA09:rvnAlienware:rnM14xR2:rvrA09:cvnAlienware:ct8:cvrA09: dmi.product.name: M14xR2 dmi.product.version: A09 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267675/+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
[Touch-packages] [Bug 1823572] Re: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all
I'm slightly concerned about this, although if Jack is not running then it shouldn't matter: !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes Jack: Installed - Yes (/usr/bin/jackd) Running - No Still, please uninstall Jack if you can. -- 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/1823572 Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound output. I don't see the CA0132 devices listed in the sound settings GUI either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: archeetos 1879 F pulseaudio /dev/snd/controlC1: archeetos 1879 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:04:20 2019 InstallationDate: Installed on 2017-03-18 (749 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1476 F pulseaudio archeetos 1879 F pulseaudio /dev/snd/controlC1: gdm1476 F pulseaudio archeetos 1879 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to bionic on 2019-04-07 (0 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22m dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22m:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 7 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1823572/+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 1823590] Re: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_structure_new_id_empty_with_size() from gs
** Summary changed: - /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:gst_structure_new_id_empty_with_size:gst_structure_new_id_empty + totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_structure_new_id_empty_with_size() from gst_structure_new_id_empty() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1823590 Title: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_structure_new_id_empty_with_size() from gst_structure_new_id_empty() Status in gstreamer0.10 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer0.10. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/f047a4f2d54fac9f37903e1b0492344d8180ab4f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1823590/+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 1823587] [NEW] totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_buffer_new() from gst_buffer_copy_region
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer1.0. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/fa349f255c8a6919b90e34d3a1544a8b0bccf588 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic trusty xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823587 Title: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_buffer_new() from gst_buffer_copy_region() Status in gstreamer1.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer1.0. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/fa349f255c8a6919b90e34d3a1544a8b0bccf588 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1823587/+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 1823587] Re: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_buffer_new() from gst_buffer_copy_region()
** Summary changed: - /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:gst_buffer_new:gst_buffer_copy_region + totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_buffer_new() from gst_buffer_copy_region() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823587 Title: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_buffer_new() from gst_buffer_copy_region() Status in gstreamer1.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer1.0. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/fa349f255c8a6919b90e34d3a1544a8b0bccf588 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1823587/+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 1823585] Re: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() from g_type_create_instance()
** Summary changed: - /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance + totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() from g_type_create_instance() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1823585 Title: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() from g_type_create_instance() Status in gstreamer0.10 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer0.10. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/1c6eca42291e32908447890739d5bd8fe82212cc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1823585/+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 1823590] [NEW] totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_structure_new_id_empty_with_size() from
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer0.10. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/f047a4f2d54fac9f37903e1b0492344d8180ab4f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic saucy trusty vivid wily xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1823590 Title: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from gst_structure_new_id_empty_with_size() from gst_structure_new_id_empty() Status in gstreamer0.10 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer0.10. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/f047a4f2d54fac9f37903e1b0492344d8180ab4f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1823590/+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 1823585] [NEW] totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() from g_type_create_instance
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer0.10. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/1c6eca42291e32908447890739d5bd8fe82212cc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic precise quantal trusty utopic vivid xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1823585 Title: totem crashed with SIGSEGV in magazine_chain_pop_head() from thread_memory_magazine1_alloc() from g_slice_alloc() from g_slice_alloc0() from g_type_create_instance() Status in gstreamer0.10 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gstreamer0.10. This problem was most recently seen with package version 3.26.2-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/1c6eca42291e32908447890739d5bd8fe82212cc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1823585/+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 1823336] Re: Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake
IMHO, the mouse wheel shouldn't apply to horizontal sliders at all. It's too unintuitive, contentious about what the correct direction is (for Natural Scrolling), and a needless attempt at helping the user to avoid clicking and dragging. Plus, obviously, it causes this bug. ** Package changed: gnome-control-center (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823336 Title: Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake Status in gtk+3.0 package in Ubuntu: New Bug description: = Steps to reproduce = 1. Open the control center 2. Open the sound panel 3. Position the mouse in the middle of the panel and scroll up and down with the wheel 4. If a slider box moves to be under the mouse then the slider is moved instead of scrolling the window A video to try and show this is here: https://www.youtube.com/watch?v=IgqP25wYymU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1823336/+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 1796251] Re: gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real
** Summary changed: - gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() + gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1796251 Title: gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() Status in GNOME Shell: Fix Released Status in gdk-pixbuf package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1796251/+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 1823583] [NEW] Xorg freeze ( also Nvidia freeze (tested) )
Public bug reported: Hi, I have been using Ubuntu 14.04 LTS for 6 years without problem and I decided to renew my operating system to Ubuntu 18.04 LTS with fresh install 5 months ago. When I started to use ubuntu 18.04 LTS, I encountered some desktop freezes randomly. While it was happening, I can heart that my laptop's fan noise was incredibly increasing abnormally at that moment. So I have decided to change my driver from X.org Server to Nvidia (recommended). When I switch my driver from open source graphic driver to proprietary graphic driver, I hoped that the problem might be solved. But after a week, the problem occured again. After that in the same day the same freezes occur continuosly as much as 3 or 4 times. I don't know why it happens. The only thing I know is Ubuntu 14.04 LTS was using Unity Desktop, and Ubuntu 18.04 LTS is using GNOME Desktop anymore. I tried to alt + f2 and r command to refresh gnome desktop. Also ctrl + alt + f3 for instance, and typing gnome-shell --replace & disown to refresh gnome dektop. They sometimes works, but only if I notice early that the freezes coming. If I miss that moment, the screen completely freezes and neither cursor click nor keyboard input works What should I do? 1) & 2) My system info: = Description: Ubuntu 18.04.2 LTS Release: 18.04 Ubuntu Software: 3.28.1 = 3) I shouldn't have had to restart my system again, again and again due to desktop freezes. While it happens, session cannot be rescued. It damages my personal / work data on the RAM at that moment. I mean I encountered data loss a lot of times on the gedit or the web browser mostly, while writing or doing something. I was expecting this issue was reported someone in the internet since 5 months. Because of this, I didn't deal with it. But I guess so this is not common issue. Because, there is no patch for it. I am looking details of system update when it has come each time, but no patch there until this now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 04:35:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-46-generic, x86_64: installed nvidia, 390.116, 4.15.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0817] Subsystem: Dell GM108M [GeForce MX130] [1028:0817] InstallationDate: Installed on 2018-11-02 (156 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0c45:6717 Microdia Bus 001 Device 002: ID 1038:1707 SteelSeries ApS Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=880beb69-81b9-441e-bd97-f469b15dab9f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0RMKK4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0RMKK4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-v
[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
** Summary changed: - Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled + System wakes up immediately after suspend if Bluetooth is still enabled -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: New Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1823336] [NEW] Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake
You have been subscribed to a public bug: = Steps to reproduce = 1. Open the control center 2. Open the sound panel 3. Position the mouse in the middle of the panel and scroll up and down with the wheel 4. If a slider box moves to be under the mouse then the slider is moved instead of scrolling the window A video to try and show this is here: https://www.youtube.com/watch?v=IgqP25wYymU ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New -- Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake https://bugs.launchpad.net/bugs/1823336 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- 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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Darin, In that case please follow comment #6, and comment #13. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
Please try Ubuntu 19.04 when you can, which when updated now has gnome- bluetooth 3.32.1 to solve a few pairing problems. -- 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/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: Incomplete Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://he
[Touch-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged
Is there any reason why there's upower task at the top of this bug? ** Changed in: upower (Ubuntu Bionic) Status: New => Incomplete ** Changed in: upower (Ubuntu Cosmic) Status: New => Incomplete ** Changed in: upower (Ubuntu Disco) Status: New => Incomplete -- 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/1823175 Title: Battery status shows "Estimating..." when fully charged Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in upower package in Ubuntu: Incomplete Status in gnome-shell source package in Bionic: Triaged Status in upower source package in Bionic: Incomplete Status in gnome-shell source package in Cosmic: Triaged Status in upower source package in Cosmic: Incomplete Status in gnome-shell source package in Disco: Fix Released Status in upower source package in Disco: Incomplete Bug description: My battery is fully charged and it shows 100%. When it's connected to charger, Battery symbol changes to battery-missing-symbol. It also shows "Estimating..." for time remaining. I'm using "Asus VivoBook x510uf" My battery status when connected to AC power: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 40.367 Wh energy-empty:0 Wh energy-full: 40.367 Wh energy-full-design: 43.046 Wh energy-rate: 0 W voltage: 11.55 V percentage: 100% capacity:93.7764% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 15543934180.000 unknown History (rate): 15543934180.000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago) has history: no has statistics: no battery present: yes state: unknown warning-level: none energy: 40.367 Wh energy-full: 40.367 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 17:04:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-30 (4 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1823175/+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 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Added a xorg-server task, because I recall that needed rebuilding with EGLStreams support enabled in Xwayland. Maybe that's the only problem here? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+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 1823578] Re: scp doesn't work; required GLIBC versions not found; connection lost
I replicated this bug in a virtual machine scp -r /home/talib/Desktop/Week\ 2\ Lab talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection ldd /usr/bin/scp linux-vdso.so.1 (0x7ffca9135000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb62020) /lib64/ld-linux-x86-64.so.2 (0x7fb62041a000) strings /lib64/libc.so.6 | grep GLIBC strings: '/lib64/libc.so.6': No such file Distributor ID: Ubuntu Description:Ubuntu Disco Dingo (development branch) Release:19.04 Codename: disco libc6-dbg/disco,now 2.29-0ubuntu1 amd64 [installed,automatic] libc6-dev/disco,now 2.29-0ubuntu1 amd64 [installed,automatic] libc6/disco,now 2.29-0ubuntu1 amd64 [installed,automatic] -- 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/1823578 Title: scp doesn't work; required GLIBC versions not found; connection lost Status in openssh package in Ubuntu: New Bug description: Command: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection Notes: ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28 libc6 is already the newest version (2.28-0ubuntu1) I created symlink to libc.so.6 to see if that was the problem: sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6 yet the problem persisted Does this have anything to do with [https://wiki.ubuntu.com/MultiarchSpec Multiarch]? List installed packages: glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed] glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed] libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic] libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic] Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIBC_2.26 GLIBC_2.27 GLIBC_2.28 GLIBC_PRIVATE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:20:03 2019 InstallationDate: Installed on 2019-02-11 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1823578/+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 1823578] Re: scp doesn't work; required GLIBC versions not found; connection lost
I've just tested and had the same problem on Fedora 28, so it is highly likely that it is my fault (user error) or syccuxas01.pcc.edu's fault (server error). -- 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/1823578 Title: scp doesn't work; required GLIBC versions not found; connection lost Status in openssh package in Ubuntu: New Bug description: Command: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection Notes: ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28 libc6 is already the newest version (2.28-0ubuntu1) I created symlink to libc.so.6 to see if that was the problem: sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6 yet the problem persisted Does this have anything to do with [https://wiki.ubuntu.com/MultiarchSpec Multiarch]? List installed packages: glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed] glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed] libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic] libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic] Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIBC_2.26 GLIBC_2.27 GLIBC_2.28 GLIBC_PRIVATE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:20:03 2019 InstallationDate: Installed on 2019-02-11 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1823578/+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 1823578] Re: scp doesn't work; required GLIBC versions not found; connection lost
** Description changed: Command: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection - Notes: ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28 - libc6 is already the newest version (2.28-0ubuntu1). + libc6 is already the newest version (2.28-0ubuntu1) + + I created symlink to libc.so.6 to see if that was the problem: + sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6 + yet the problem persisted + + Does this have anything to do with + [https://wiki.ubuntu.com/MultiarchSpec Multiarch]? List installed packages: glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed] glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed] libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic] libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic] - Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) - Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIBC_2.26 GLIBC_2.27 GLIBC_2.28 GLIBC_PRIVATE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:20:03 2019 InstallationDate: Installed on 2019-02-11 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1823578 Title: scp doesn't work; required GLIBC versions not found; connection lost Status in openssh package in Ubuntu: New Bug description: Command: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection Notes: ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28 libc6 is already the newest version (2.28-0ubuntu1) I created symlink to libc.so.6 to see if that was the problem: sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6 yet the problem persisted Does this have anything to do with [https://wiki.ubuntu.com/MultiarchSpec Multiarch]? List installed packages: glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed] glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed] libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic] libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic] Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIB
[Touch-packages] [Bug 1823578] Re: scp doesn't work; required GLIBC versions not found; connection lost
** Description changed: - Command I ran: + Command: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ - Password: + Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection + + Notes: + ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28 + + libc6 is already the newest version (2.28-0ubuntu1). + + + List installed packages: + glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed] + glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] + glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] + libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed] + libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed] + libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed] + libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed] + libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed] + libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic] + libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic] + + Diagnostic information: ldd /usr/bin/scp - linux-vdso.so.1 (0x7ffd04f57000) - libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) - /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) + linux-vdso.so.1 (0x7ffd04f57000) + libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) + /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) + Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIBC_2.26 GLIBC_2.27 GLIBC_2.28 GLIBC_PRIVATE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:20:03 2019 InstallationDate: Installed on 2019-02-11 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: - ssh-askpass N/A - libpam-sshN/A - keychain N/A - ssh-askpass-gnome N/A + ssh-askpass N/A + libpam-sshN/A + keychain N/A + ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1823578 Title: scp doesn't work; required GLIBC versions not found; connection lost Status in openssh package in Ubuntu: New Bug description: Command: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection Notes: ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28 libc6 is already the newest version (2.28-0ubuntu1) I created symlink to libc.so.6 to see if that was the problem: sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6 yet the problem persisted Does this have anything to do with [https://wiki.ubuntu.com/MultiarchSpec Multiarch]? List installed packages: glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed] glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed] libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed] libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed] libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic] libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic] Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25
[Touch-packages] [Bug 1823578] [NEW] scp doesn't work; required GLIBC versions not found; connection lost
Public bug reported: Command I ran: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIBC_2.26 GLIBC_2.27 GLIBC_2.28 GLIBC_PRIVATE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:20:03 2019 InstallationDate: Installed on 2019-02-11 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1823578 Title: scp doesn't work; required GLIBC versions not found; connection lost Status in openssh package in Ubuntu: New Bug description: Command I ran: scp -r '/home/talib/Desktop/Week 2 Lab' talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/ Password: scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp) scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp) lost connection Diagnostic information: ldd /usr/bin/scp linux-vdso.so.1 (0x7ffd04f57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000) /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000) Diagnostic information: strings /lib64/libc.so.6 | grep GLIBC GLIBC_2.2.5 GLIBC_2.2.6 GLIBC_2.3 GLIBC_2.3.2 GLIBC_2.3.3 GLIBC_2.3.4 GLIBC_2.4 GLIBC_2.5 GLIBC_2.6 GLIBC_2.7 GLIBC_2.8 GLIBC_2.9 GLIBC_2.10 GLIBC_2.11 GLIBC_2.12 GLIBC_2.13 GLIBC_2.14 GLIBC_2.15 GLIBC_2.16 GLIBC_2.17 GLIBC_2.18 GLIBC_2.22 GLIBC_2.23 GLIBC_2.24 GLIBC_2.25 GLIBC_2.26 GLIBC_2.27 GLIBC_2.28 GLIBC_PRIVATE ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: openssh-client 1:7.7p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 17:20:03 2019 InstallationDate: Installed on 2019-02-11 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1823578/+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 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
The issue: * exists with the following themes - Ambiant-MATE, Ambiant-MATE-Dark, BlackMATE, GreenLaguna, Radiant-MATE, TraditionalGreen, TraditionalOk; *does not exist with BlueMenta, Blue-Submarine, Green-Submarine, High Contrast, High Contrast Inverse, Menta. So all default `mate-themes` themes should be changed to have normal font in aforementioned dropdown menus. See BlueMenta as good example in attachment. ** Attachment added: "BlueMenta theme is not affected" https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1823550/+attachment/5253813/+files/bluementa.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Fix Released Status in gtk+3.0 package in Ubuntu: New Status in gtksourceview3 package in Ubuntu: New Status in mate-themes package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+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 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
** Changed in: gtksourceview Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Fix Released Status in gtk+3.0 package in Ubuntu: New Status in gtksourceview3 package in Ubuntu: New Status in mate-themes package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+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 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
** Also affects: mate-themes (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Unknown Status in gtk+3.0 package in Ubuntu: New Status in gtksourceview3 package in Ubuntu: New Status in mate-themes package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+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 1823573] [NEW] Bluetooth headset not available as output device
Public bug reported: Connecting my Bluetooth headset (Beoplay H8) appears to be working, and everything looks correct in the Bluetooth settings: However, the headset is not listed under "Output devices" in the sound menu after connecting, and all sounds are channeled through the built-in speakers. Media buttons on the headset are also rendered useless, not that there would be much use for them without sound anyways. Still worth noting, as everything including media buttons worked perfectly in 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stein 2603 F pulseaudio /dev/snd/pcmC0D0c: stein 2603 F...m pulseaudio /dev/snd/pcmC0D0p: stein 2603 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 23:00:38 2019 InstallationDate: Installed on 2018-05-09 (332 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN16WW(V2.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1823573 Title: Bluetooth headset not available as output device Status in alsa-driver package in Ubuntu: New Bug description: Connecting my Bluetooth headset (Beoplay H8) appears to be working, and everything looks correct in the Bluetooth settings: However, the headset is not listed under "Output devices" in the sound menu after connecting, and all sounds are channeled through the built-in speakers. Media buttons on the headset are also rendered useless, not that there would be much use for them without sound anyways. Still worth noting, as everything including media buttons worked perfectly in 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stein 2603 F pulseaudio /dev/snd/pcmC0D0c: stein 2603 F...m pulseaudio /dev/snd/pcmC0D0p: stein 2603 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 23:00:38 2019 InstallationDate: Installed on 2018-05-09 (332 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN16WW(V2.00) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bu
[Touch-packages] [Bug 1823572] [NEW] [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all
Public bug reported: No sound output. I don't see the CA0132 devices listed in the sound settings GUI either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: archeetos 1879 F pulseaudio /dev/snd/controlC1: archeetos 1879 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:04:20 2019 InstallationDate: Installed on 2017-03-18 (749 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1476 F pulseaudio archeetos 1879 F pulseaudio /dev/snd/controlC1: gdm1476 F pulseaudio archeetos 1879 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to bionic on 2019-04-07 (0 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22m dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22m:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 7 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1823572 Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound output. I don't see the CA0132 devices listed in the sound settings GUI either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: archeetos 1879 F pulseaudio /dev/snd/controlC1: archeetos 1879 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 14:04:20 2019 InstallationDate: Installed on 2017-03-18 (749 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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 failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1476 F pulseaudio archeetos 1879 F pulseaudio /dev/snd/controlC1: gdm1476 F pulseaudio archeetos 1879 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to bionic on 2019-04-07 (0 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22m dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22m:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 7 dmi.product.version: Default s
[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
** Description changed: - Some gkt2 applications randomly crash with same error. See attached + GTK2 applications randomly crash or freeze with same error. See attached files. ** Changed in: gtk+2.0 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: GTK2 applications randomly crash or freeze with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
** Summary changed: - !xcb_xlib_threads_sequence_lost error + !xcb_xlib_threads_sequence_lost error with GTK2 applications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: Some gkt2 applications randomly crash with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error
Related pcmanfm bug https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: Some gkt2 applications randomly crash with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
** Bug watch added: gitlab.gnome.org/GNOME/gtksourceview/issues #52 https://gitlab.gnome.org/GNOME/gtksourceview/issues/52 ** Also affects: mate-desktop via https://gitlab.gnome.org/GNOME/gtksourceview/issues/52 Importance: Unknown Status: Unknown ** Project changed: mate-desktop => gnome-desktop ** Project changed: gnome-desktop => gtksourceview -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Unknown Status in gtk+3.0 package in Ubuntu: New Status in gtksourceview3 package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+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 1659534] Reminder of SRU verification policy change
Thank you for taking the time to verify this stable release fix. We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE). Please remove the verification-done tag and add one for the release you have tested the package in. Thank you! https://wiki.ubuntu.com/StableReleaseUpdates#Verification -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+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 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu
** Description changed: Steps to reproduce: - 1. Have Ubuntu MATE 17.04 installed - 2. Open Pluma + 1. Have Ubuntu 17.04 or later installed + 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font - Notes: - * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. + * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in gtk+3.0 package in Ubuntu: New Status in gtksourceview3 package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1823550/+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 1823550] Re: Pluma wrongly has monospaced font in dropdown (context) menu
** Also affects: gtksourceview3 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Pluma wrongly has monospaced font in dropdown (context) menu + GtkSourceView wrongly has monospaced font in dropdown (context) menu ** Changed in: pluma (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView wrongly has monospaced font in dropdown (context) menu Status in gtk+3.0 package in Ubuntu: New Status in gtksourceview3 package in Ubuntu: New Status in pluma package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu MATE 17.04 installed 2. Open Pluma 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1823550/+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 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also affects Disco ** Tags added: disco -- 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/1820074 Title: Running glxgears with Indirect GLX crashes Xorg Status in mesa package in Ubuntu: New Bug description: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Touch-packages] [Bug 1823550] Re: Context menu in Pluma wrongly has monospaced font in dropdown menu
The correct (expected) font is presented on the screenshot from Ubuntu MATE 16.04 LTS. ** Attachment added: "correct dropdown menu in Ubuntu MATE 16.04 LTS" https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1823550/+attachment/5253755/+files/pluma-dropdown-1604.png ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Context menu in Pluma wrongly has monospaced font in dropdown menu + Pluma wrongly has monospaced font in dropdown menu ** Summary changed: - Pluma wrongly has monospaced font in dropdown menu + Pluma wrongly has monospaced font in dropdown (context) menu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: Pluma wrongly has monospaced font in dropdown (context) menu Status in gtk+3.0 package in Ubuntu: New Status in pluma package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu MATE 17.04 installed 2. Open Pluma 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1823550/+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 992194] Re: BOM symbols in ru_RU.aff affect some package installation
Still affects Ubuntu 16.04 on installation of Postgres 9.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+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 992194] Re: BOM symbols in ru_RU.aff affect some package installation
The files /usr/share/hunspell/ru_RU.aff and /usr/share/hunspell/ru_RU.dic also have wrong line endings: "\r\n" instead of just "\n". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+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 1821462] Re: Ubuntu 19.04 Desktop:slow boot
** Tags added: disco -- 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/1821462 Title: Ubuntu 19.04 Desktop:slow boot Status in systemd package in Ubuntu: Confirmed Bug description: Hello, I have my ubuntu desktop set to boot text only mode. it seems a removable hard drive was pplugged into my machine some time ago. On every boot the boot takes a minute and a half to search to see if that drive is plugged in. I ran systemd-analyze blame Below is my output: 37.816s apt-daily.service 2.383s dev-sda4.device 2.381s NetworkManager-wait-online.service 1.198s man-db.service 1.112s dev-loop9.device 1.108s dev-loop8.device 1.098s dev-loop4.device 1.083s dev-loop6.device 1.071s dev-loop10.device 1.057s dev-loop13.device 1.057s dev-loop11.device 1.051s dev-loop7.device 1.051s dev-loop12.device 1.046s dev-loop2.device 1.032s dev-loop14.device 1.024s apt-daily-upgrade.service 1.017s snap-core18-782.mount 988ms snap-vice\x2djz-22.mount 983ms snap-gnome\x2dcalculator-260.mount 949ms dev-loop15.device 930ms dev-loop3.device 905ms dev-loop5.device 901ms dev-loop1.device 899ms dev-loop0.device 891ms dev-loop16.device 878ms snap-gnome\x2d3\x2d26\x2d1604-78.mount 868ms snap-remmina-2831.mount 855ms snap-gnome\x2dcharacters-139.mount 845ms snap-youtube\x2ddl\x2dsnap-1.mount 844ms dev-loop17.device 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount 814ms snap-remmina-2823.mount 803ms snap-gnome\x2dclocks-85.mount 798ms snap-gnome\x2dcharacters-206.mount 793ms snap-core-6350.mount 783ms snap-core-6531.mount 776ms udisks2.service 773ms snap-gnome\x2dlogs-45.mount 763ms snap-vice\x2djz-20.mount 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount 744ms snap-core-6405.mount 734ms snap-vice\x2djz-19.mount 733ms snap-gnome\x2dcharacters-124.mount 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount 719ms dev-loop18.device 715ms snap-core18-731.mount 706ms snap-core18-719.mount 695ms snap-gnome\x2dcalculator-238.mount 680ms upower.service 662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount 646ms dev-loop19.device 643ms snap-gtk\x2dcommon\x2dthemes-818.mount 638ms dev-loop23.device 626ms snap-gnome\x2dlogs-57.mount 626ms dev-loop26.device 610ms snap-gnome\x2dsystem\x2dmonitor-70.mount 596ms dev-loop21.device 589ms dev-loop25.device 587ms dev-loop20.device 583ms dev-loop24.device 528ms logrotate.service 523ms systemd-journal-flush.service 496ms dev-loop22.device 491ms dev-loop30.device 490ms dev-loop27.device 487ms dev-loop28.device 433ms networkd-dispatcher.service 427ms snapd.service 397ms ModemManager.service 382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount 379ms snap-gnome\x2dcalculator-352.mount 369ms snap-remmina-2819.mount 362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount 359ms snap-gnome\x2dsystem\x2dmonitor-57.mount 340ms accounts-daemon.service 307ms systemd-logind.service 281ms keyboard-setup.service 280ms kmod-static-nodes.service 261ms dev-hugepages.mount 260ms avahi-daemon.service 259ms sys-kernel-debug.mount 259ms ufw.service 255ms apport-autoreport.service 251ms systemd-udev-trigger.service 242ms systemd-modules-load.service 232ms systemd-journald.service 230ms fwupd.service 206ms apport.service 196ms dev-mqueue.mount 194ms apparmor.service 186ms rsyslog.service 184ms dev-loop29.device 182ms NetworkManager.service 181ms systemd-remount-fs.service 180ms gdm.service 174ms nmbd.service 164ms smbd.service 164ms wpa_supplicant.service 157ms dev-loop32.device 154ms networking.service 142ms thermald.service 137ms virtualbox.service 124ms systemd-sysusers.service
[Touch-packages] [Bug 1763942] Re: Text selection in dialog windows have low contrast
Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763942 Title: Text selection in dialog windows have low contrast Status in gtk+3.0 package in Ubuntu: New Status in ubuntu-mate-artwork package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS 2. Launch `mate-terminal`, select *Help*, *About*, select text *A terminal emulator for the MATE desktop*. Expected results: * selected text has good contrast Actual results: * selected text has bad contrast as it is not selected. Note: you can find other examples of low contrast text. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-mate-desktop 1.222 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: MATE Date: Sat Apr 14 16:02:42 2018 InstallationDate: Installed on 2018-04-14 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) SourcePackage: ubuntu-mate-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763942/+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 1787368] Re: Caja does not show previews of text files on Bionic and newer versions
Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787368 Title: Caja does not show previews of text files on Bionic and newer versions Status in MATE Desktop: New Status in caja package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS (or upgrade from 16.04 LTS) 2. Create text file somewhere (in home folder for example) with `echo text > ~/file.txt`. 3. Open Caja in home folder Expected results: * Caja shows preview (the contents) of `file.txt` in Icon view. Actual results: * Caja does not show preview of `file.txt`. Notes: 1. all settings in Preview tab are set to *Local Only* 2. this happens on clean user profile and/or after `dconf reset -f /` and `gsettings reset-recursively org.mate.caja` 3. Problem first seen on AskUbuntu ( https://askubuntu.com/q/1065825/66509 ). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Aug 16 12:36:57 2018 InstallationDate: Installed on 2018-04-26 (111 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1787368/+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 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color
Really it was started to appear with 16.10, so all 16.10, 17.04, 17.10, 18.04 LTS, 18.10 and 19.04 are affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1721955 Title: Human, Human-Clearlooks and other themes have incorrect gray window title color Status in community-themes package in Ubuntu: New Status in compiz package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in human-theme package in Ubuntu: Confirmed Status in marco package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE 2. Install Human theme from `human-theme` package 3. Select Human theme from `mate-control-center` Appearance Expected results: window title color is set to Ubuntu's orange (#FFBE6B) Actual results: window title color is set to different gray/silver color (#a5a5a2) Note: other themes are affected too. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: human-theme 0.39.2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 15:43:03 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170925.1) PackageArchitecture: all SourcePackage: human-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+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 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed -- 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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+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 1763942] Re: Text selection in dialog windows have low contrast
** Tags added: cosmic disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763942 Title: Text selection in dialog windows have low contrast Status in gtk+3.0 package in Ubuntu: New Status in ubuntu-mate-artwork package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS 2. Launch `mate-terminal`, select *Help*, *About*, select text *A terminal emulator for the MATE desktop*. Expected results: * selected text has good contrast Actual results: * selected text has bad contrast as it is not selected. Note: you can find other examples of low contrast text. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-mate-desktop 1.222 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: MATE Date: Sat Apr 14 16:02:42 2018 InstallationDate: Installed on 2018-04-14 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) SourcePackage: ubuntu-mate-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763942/+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 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+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 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1823516 Title: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+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 1763942] Re: Text selection in dialog windows have low contrast
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763942 Title: Text selection in dialog windows have low contrast Status in gtk+3.0 package in Ubuntu: New Status in ubuntu-mate-artwork package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install Ubuntu MATE 18.04 LTS 2. Launch `mate-terminal`, select *Help*, *About*, select text *A terminal emulator for the MATE desktop*. Expected results: * selected text has good contrast Actual results: * selected text has bad contrast as it is not selected. Note: you can find other examples of low contrast text. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-mate-desktop 1.222 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: MATE Date: Sat Apr 14 16:02:42 2018 InstallationDate: Installed on 2018-04-14 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) SourcePackage: ubuntu-mate-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763942/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Already verified in 0.90ubuntu0.5 for Xenial, not additional test is
needed.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Released
Status in unattended-upgrades source package in Zesty:
Fix Released
Status in unattended-upgrades package in Debian:
Fix Released
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
Change WantedBy to multi-user.target. This requires working around Debian Bug
#797108 which causes the new unit not to be enabled.
Remove the unneeded override_dh_isntallinit
Add Default-Start levels to the SysV initscript
Improve DEP8 testing
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
Upgrade has been tested on Xenial, Yakkety, Zesty. do-release-upgrade has
been tested from Trusty to Xenial. All behave as expected.
A change of behavior may occur now that the systemd unit is correctly
enabled, which would make functionalities like InstallOnShutdown to
work as expected whereas it could have been broken previously. This
cannot be considered as a regression as it is expected behavior.
Shutdown may be slowed down as it now correctly depends on /var and
/boot to be available so the unit will run earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1823532] [NEW] Não Entra no google. E as vezes fica com a tela azul
Public bug reported: As vezes a tela fica azul ou preta impossibilita acessar as funções e tela e preta . As não entra no google e nas outras funções, e parece algo relacionado ao software que impedi e baixar e atualiza . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evolution-data-server 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 7 09:39:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-02-24 (41 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: evolution-data-server Title: package evolution-data-server 3.18.5-1ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Summary changed: - não entra no google as vezes e tela azul + Não Entra no google e as vezes e tela azul ** Summary changed: - Não Entra no google e as vezes e tela azul + Não Entra no google. e as vezes e tela azul ** Summary changed: - Não Entra no google. e as vezes e tela azul + Não Entra no google. E as vezes fica com a tela azul -- 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/1823532 Title: Não Entra no google. E as vezes fica com a tela azul Status in evolution-data-server package in Ubuntu: New Bug description: As vezes a tela fica azul ou preta impossibilita acessar as funções e tela e preta . As não entra no google e nas outras funções, e parece algo relacionado ao software que impedi e baixar e atualiza . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evolution-data-server 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 7 09:39:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-02-24 (41 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: evolution-data-server Title: package evolution-data-server 3.18.5-1ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1823532/+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 1446552] Re: Unattended upgrades handles new dependencies inconsistently
Verified 1.1ubuntu1.18.04.7~16.04.2 on Ubuntu Xenial. I changed a different, but equivalent way of verifying the fix, in /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages I bumped the version of bash-doc to 4.3-14ubuntu1.3, bumped git's version in updates to 1:2.7.4-0ubuntu1.7 and made git depend on bash-doc (>= 4.3-14ubuntu1) in both -updates and -security. Bash-doc was not installed originally on the system. With unfixed u-u it fails to upgrade git: root@x-uu-ref:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] Checking: git ([]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals root@x-uu-ref:~# vi /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages root@x-uu-ref:~# vi /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages root@x-uu-ref:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] adjusting candidate version: 'git=1:2.7.4-0ubuntu1.6' Checking: git ([]) pkg 'bash-doc' not in allowed origin sanity check failed adjusting candidate version: 'git=1:2.7.4-0ubuntu1.6' pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: adjusting candidate version: 'git=1:2.7.4-0ubuntu1.6' Packages that are auto removed: 'libfreetype6' Packages were successfully auto-removed InstCount=0 DelCount=0 BrokenCount=0 With fixed u-u, git is upgraded: root@x-uu-verify:~# unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages Using (^linux-image-4\.18\.0\-17\-generic$|^linux-headers-4\.18\.0\-17\-generic$|^linux-image-extra-4\.18\.0\-17\-generic$|^linux-modules-4\.18\.0\-17\-generic$|^linux-modules-extra-4\.18\.0\-17\-generic$|^linux-signed-image-4\.18\.0\-17\-generic$|^kfreebsd-image-4\.18\.0\-17\-generic$|^kfreebsd-headers-4\.18\.0\-17\-generic$|^gnumach-image-4\.18\.0\-17\-generic$|^.*-modules-4\.18\.0\-17\-generic$|^.*-kernel-4\.18\.0\-17\-generic$|^linux-backports-modules-.*-4\.18\.0\-17\-generic$|^linux-modules-.*-4\.18\.0\-17\-generic$|^linux-tools-4\.18\.0\-17\-generic$|^linux-cloud-tools-4\.18\.0\-17\-generic$) regexp to find running kernel packages Checking: git ([]) adjusting candidate version: git=1:2.7.4-0ubuntu1.6 adjusting candidate version: bash-doc=4.3-14ubuntu1.2 pkgs that look like they should be upgraded: git Get:1 http://security.ubuntu.com/ubuntu xenial-security/main amd64 bash-doc all 4.3-14ubuntu1.2 [1151 kB] Fetched 1151 kB in 0s (0 B/s) fetch.run() result: 0 http://security.ubuntu.com/ubuntu/pool/main/b/bash/bash-doc_4.3-14ubuntu1.2_all.deb' ID:1 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/bash-doc_4.3-14ubuntu1.2_all.deb) No conffiles in deb /var/cache/apt/archives/bash-doc_4.3-14ubuntu1.2_all.deb (There is no member named 'conffiles') http://security.ubuntu.com/ubuntu/pool/main/g/git/git_2.7.4-0ubuntu1.6_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/git_1%3a2.7.4-0ubuntu1.6_amd64.deb) found pkg: git conffile line: /etc/bash_completion.d/git-prompt - blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: git Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log adjusting candidate version: bash-doc=4.3-14ubuntu1.2 adjusting c
[Touch-packages] [Bug 1654070] Re: sanity check can fail for packages missing dependencies
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654070 Title: sanity check can fail for packages missing dependencies Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: I've been getting mail for days about pulseaudio-module-gconf and -module-zeroconf being upgraded, come to find out its not really happening. bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose Initial blacklisted packages: nvidia-304 Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] Checking: pulseaudio-module-gconf ([]) Checking: pulseaudio-module-zeroconf ([]) pkgs that look like they should be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: ['nvidia-304'] whitelist: [] Checking the black and whitelist: pulseaudio-module-gconf Checking the black and whitelist: pulseaudio-module-zeroconf Packages that will be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 12:27:12' Sending mail to 'bdmurray@bizarro.watchtower.local' mail returned: 0 bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf pulseaudio-module-gconf: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3.1 Version table: 1:8.0-0ubuntu3.1 500 500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages *** 1:8.0-0ubuntu3 500 500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1654070] Re: sanity check can fail for packages missing dependencies
Verified with 1.1ubuntu1.18.04.7~16.04.2: Added a not existing dep to git: # vi /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_xenial-security_main_binary-amd64_Packages # apt-cache show git ... Package: git Architecture: amd64 Version: 1:2.7.4-0ubuntu1.6 Multi-Arch: foreign Priority: optional Section: vcs Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Gerrit Pape Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 23556 Provides: git-completion, git-core Depends: libc6 (>= 2.16), libcurl3-gnutls (>= 7.16.2), libexpat1 (>= 2.0.1), libpcre3, zlib1g (>= 1:1.2.0), perl-modules, liberror-perl, git-man (>> 1:2.7.4), git-man (<< 1:2.7.4-.), zz-not-existing-dep ... # installed old git # apt install git=1:2.7.4-0ubuntu1 ... # unattended-upgrade --dry-run --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial ... Checking: git ([]) pkg git not in allowed origin sanity check failed pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: InstCount=0 DelCount=0 BrokenCount=0 # Now git is not listed among packages to be installed. The message of not being in an allowed origin is correct, git from -updates is installable. There could be a better debug message and when I add the missing dep to the version in -updates, only the "sanity check failed" is printed. Users can turn to APT to explain: root@x-uu-verify:~# apt install git Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: git : Depends: zz-missing-dep-updates but it is not installable E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654070 Title: sanity check can fail for packages missing dependencies Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: I've been getting mail for days about pulseaudio-module-gconf and -module-zeroconf being upgraded, come to find out its not really happening. bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose Initial blacklisted packages: nvidia-304 Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] Checking: pulseaudio-module-gconf ([]) Checking: pulseaudio-module-zeroconf ([]) pkgs that look like they should be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: ['nvidia-304'] whitelist: [] Checking the black and whitelist: pulseaudio-module-gconf Checking the black and whitelist: pulseaudio-module-zeroconf Packages that will be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 12:27:12' Sending mail to 'bdmurray@bizarro.watchtower.local' mail returned: 0 bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf pulseaudio-module-gconf: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3.1 Version table: 1:8.0-0ubuntu3.1 500 500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages *** 1:8.0-0ubuntu3 500 500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+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 1821491] Re: DNS lookup fails for local hosts
** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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 1823503] Re: systemd-resolved ignores /etc/network/interfaces on Ubuntu 18.04
For new installations, the /etc/network/interfaces file does have text explaining that ifupdown is no longer used and network config is now done via netplan. For upgrades of systems using ifupdown, it is not removed, and should still manage the networking, and changes to /e/n/i should still work. To address your bug that systemd-resolved ignores any settings in e/n/i, that's correct that systemd-resolved will not *directly* look at the e/n/i config to find nameserver configuration. However, if ifupdown is managing your system networking, then it will provide nameserver details to systemd-resolved. The specific mechanism depends on your specific network configuration (e.g. static vs dhcp) and if you have resolvconf installed or not. If you are having a specific problem with your system networking, please feel free to add details about what is wrong. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1823503 Title: systemd-resolved ignores /etc/network/interfaces on Ubuntu 18.04 Status in systemd package in Ubuntu: Incomplete Bug description: dns-nameservers entry in /etc/network/interfaces is ignored by systemd-resolved-- all of the other settings work, which adds quite a bit of confusion and frustration since Ubuntu recently switched to using netplan. It would be a **VERY** good idea to add a comment at the top of /etc/network/interfaces that this file is now deprecated, and provide information about the new netplan utility. Something similar was done to /etc/resolv.conf years back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823503/+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 1823521] [NEW] on_ac_power returns 1 if battery is not present
Public bug reported: on_ac_power should return 0 (as exit code). Besides Xfce Power Manager tells in Devices tab that Line power is "Not plugged in". Tested by an old Macbook. (I don't have battery to test with.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: powermgmt-base 1.33 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 7 14:02:36 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (821 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: powermgmt-base UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-power-manager Importance: Undecided Status: New ** Affects: powermgmt-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: xfce4-power-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1823521 Title: on_ac_power returns 1 if battery is not present Status in xfce4-power-manager: New Status in powermgmt-base package in Ubuntu: New Bug description: on_ac_power should return 0 (as exit code). Besides Xfce Power Manager tells in Devices tab that Line power is "Not plugged in". Tested by an old Macbook. (I don't have battery to test with.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: powermgmt-base 1.33 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 7 14:02:36 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (821 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: powermgmt-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1823521/+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 1714705] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1714705 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: jefff@jefff-System-Product-Name:~$ sudo apt-get -f install util-linux Reading package lists... Done Building dependency tree Reading state information... Done util-linux is already the newest version (2.27.1-6ubuntu3.3). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Product-Name:~$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.8.0-36 linux-headers-4.8.0-36-generic linux-headers-4.8.0-53 linux-headers-4.8.0-53-generic linux-image-4.8.0-36-generic linux-image-4.8.0-53-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-53-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: grub-common grub-pc grub-pc-bin grub2-common Suggested packages: multiboot-doc grub-emu xorriso desktop-base The following packages will be upgraded: grub-common grub-pc grub-pc-bin grub2-common 4 upgraded, 0 newly installed, 0 to remove and 221 not upgraded. 2 not fully installed or removed. Need to get 4,337 kB of archives. After this operation, 5,120 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 util-linux i386 2.27.1-6ubuntu3.3 [875 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc i386 2.02~beta2-36ubuntu3.12 [197 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc-bin i386 2.02~beta2-36ubuntu3.12 [915 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub2-common i386 2.02~beta2-36ubuntu3.12 [545 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-common i386 2.02~beta2-36ubuntu3.12 [1,806 kB] Fetched 4,337 kB in 0s (6,404 kB/s) Preconfiguring packages ... dpkg: error processing package util-linux (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) jefff@jefff-System-Product-Name:~$ jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed grub-pc-bin : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 2.02~beta2-36ubuntu3.12 is to be installed grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 2.02~beta2-36ubuntu3.12 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Product-Name:~$ jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub2-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed E: Unmet dependencies. Try 'apt-get -f install' w
[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
Hi, I think I have enabled pre-released updates. Is the kernel version (4.18.0-17-generic), the one that should have this patch? I am wondering because wifi does not seem to work with this kernel. Thank ** Attachment added: "devel-enabled.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818204/+attachment/5253636/+files/devel-enabled.png -- 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/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in network-manager source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Committed Status in network-manager source package in Cosmic: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol
[Touch-packages] [Bug 1714705] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1714705 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: jefff@jefff-System-Product-Name:~$ sudo apt-get -f install util-linux Reading package lists... Done Building dependency tree Reading state information... Done util-linux is already the newest version (2.27.1-6ubuntu3.3). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Product-Name:~$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.8.0-36 linux-headers-4.8.0-36-generic linux-headers-4.8.0-53 linux-headers-4.8.0-53-generic linux-image-4.8.0-36-generic linux-image-4.8.0-53-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-53-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: grub-common grub-pc grub-pc-bin grub2-common Suggested packages: multiboot-doc grub-emu xorriso desktop-base The following packages will be upgraded: grub-common grub-pc grub-pc-bin grub2-common 4 upgraded, 0 newly installed, 0 to remove and 221 not upgraded. 2 not fully installed or removed. Need to get 4,337 kB of archives. After this operation, 5,120 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 util-linux i386 2.27.1-6ubuntu3.3 [875 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc i386 2.02~beta2-36ubuntu3.12 [197 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc-bin i386 2.02~beta2-36ubuntu3.12 [915 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub2-common i386 2.02~beta2-36ubuntu3.12 [545 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-common i386 2.02~beta2-36ubuntu3.12 [1,806 kB] Fetched 4,337 kB in 0s (6,404 kB/s) Preconfiguring packages ... dpkg: error processing package util-linux (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) jefff@jefff-System-Product-Name:~$ jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed grub-pc-bin : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 2.02~beta2-36ubuntu3.12 is to be installed grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 2.02~beta2-36ubuntu3.12 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Product-Name:~$ jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub2-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed E: Unmet dependencies. Try 'apt-get -f inst
[Touch-packages] [Bug 1823516] [NEW] Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
Public bug reported: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco nvidia-drm.modeset third-party-packages ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Nvidia-418 installed but GLX is using LLVMpipe/Mesa in Wayland sessions + Nvidia-418 installed but GLX and EGL are using LLVMpipe/Mesa in Wayland sessions ** Description changed: - Nvidia-418 installed but GLX is using LLVMpipe/Mesa in Wayland sessions. + Nvidia-418 installed but GLX and EGL are using LLVMpipe/Mesa in Wayland + sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Nvidia-418 installed but GLX and EGL are using LLVMpipe/Mesa in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: + $ es2_info | grep ^GL + GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 + GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) + + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux
[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
https://wiki.ubuntu.com/Testing/EnableProposed -- 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/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in network-manager source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Committed Status in network-manager source package in Cosmic: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session wayland-ses
