[Touch-packages] [Bug 2007355] Re: current curl and libcurl 7.81 in Ubuntu 22.04.1 LTS contain annoying bug
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2007355 Title: current curl and libcurl 7.81 in Ubuntu 22.04.1 LTS contain annoying bug Status in curl package in Ubuntu: Confirmed Bug description: Hi team, Current curl and libcurl 7.81.0 in Ubuntu 22.04 contain annoying bug: "cURL error 35: error:0A00010B:SSL routines::wrong version number" It is described in curl repo there https://github.com/curl/curl/issues/9931 and fixed in curl and libcurl 7.87 Could you kindly update curl and libcurl packages for Ubuntu 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2007355/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
I confirm the issue on a desktop with Intel HD Graphics 530 (rev 06) (Core i7-6700 CPU). At present time I found that it can be worked around in two ways: 1) Using the '--disable-gpu-driver-bug-workarounds' option: # google-chrome-stable --disable-gpu-driver-bug-workarounds 2) Defining MESA_LOADER_DRIVER_OVERRIDE=i965 in the environment in which chrome is executed: # MESA_LOADER_DRIVER_OVERRIDE=i965 google-chrome-stable I can send any further information (or make any test) that can help you in fixing the issue. -- 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/2020604 Title: After mesa upgrades, Chrome won't show graphics Status in mesa package in Ubuntu: Confirmed Bug description: After today's Ubuntu 22.04 mesa upgrades many of our users reported problems viewing graphics when using Google Chrome (Stable). The mesa upgrades we installed were: [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 22.2.5-0ubuntu0.1~22.04.2 We documented the problem in AskUbuntu before we realized it was probably related to mesa, so wanted to link to that report here: https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa- updates-chrome-wont-display-website-graphi There is a bypass listed in that article. Not sure if this is an issue with mesa or Chrome or specific machine graphics or an interaction between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+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 1956875] [NEW] [HDA-Intel - HD-Audio Generic, recording] Recording problem: Headset mic not detected
Public bug reported: In my laptop (Huawei MateBook 14 2020 AMD R5, Model KLVL-WFH9) there is a single 3.5mm jack port which allows audio input and output. I've got a headset with a single cable, sound can be heard very good, microphone is not detected. The disk runs Windows 10 in one partition and in the other one Ubuntu 20.04. I also had trouble with Windows in recognizing the headset's mic but now that has been solved. However, in Ubuntu it is only detected and "categorized" as Headphone. There is no way to use the microphone of the headset. I've tried to find some similar issues but nothing has helped me so far. Thanks in advance, Lorenzo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.7.17-050717-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 17:51:26 2022 InstallationDate: Installed on 2021-03-29 (286 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic_1 failed Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HD-Audio Generic, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2020 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.06 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.06:bd09/14/2020:svnHUAWEI:pnKLVL-WXX9:pvrM1130:rvnHUAWEI:rnKLVL-WXX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXX9 dmi.product.sku: C100 dmi.product.version: M1130 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-01-06T13:57:39.54 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1956875 Title: [HDA-Intel - HD-Audio Generic, recording] Recording problem: Headset mic not detected Status in alsa-driver package in Ubuntu: New Bug description: In my laptop (Huawei MateBook 14 2020 AMD R5, Model KLVL-WFH9) there is a single 3.5mm jack port which allows audio input and output. I've got a headset with a single cable, sound can be heard very good, microphone is not detected. The disk runs Windows 10 in one partition and in the other one Ubuntu 20.04. I also had trouble with Windows in recognizing the headset's mic but now that has been solved. However, in Ubuntu it is only detected and "categorized" as Headphone. There is no way to use the microphone of the headset. I've tried to find some similar issues but nothing has helped me so far. Thanks in advance, Lorenzo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.7.17-050717-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 17:51:26 2022 InstallationDate: Installed on 2021-03-29 (286 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 successful Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic_1 failed Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HD-Audio Generic, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2020 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.06 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1130 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1130 dmi.modalias: dmi:bvnHUAWEI:bvr1.06:bd09/14/2020:svnHUAWEI:pnKLVL-WXX9:pvrM1130:rvnHUAWEI:rnKLVL-WXX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130: dmi.product.family: MateBook 14 dmi.produc
[Touch-packages] [Bug 1948710] [NEW] Suspend issues with nvidia proprietary driver
Public bug reported: When I suspend my system, after the screen goes black, the desktop and the suspend login screen are briefly shown in succession, and only then the screen, power LED and fan turn off like normally. The timing of the brief "fake resume" is not consistent: sometimes it only shows the login screen, sometimes it stops the suspension until briefly after I login. When resuming after this has happened, the login screen appears as normal, but I have to wait for any internet connection to restart, and my second screen remains blacks despite it being detected and the display mode remaining on "join displays", until I change the display mode back and forth to fix it. These issues occur after switching to the nvidia-driver-470 driver on a fresh install of Ubuntu 21.10, but I have been experiencing at least the "fake-resume" since at least 20.10, without being able to find any solution. These issues persist (with slightly altered timing) if I switch to an older proprietary driver (I tried nvidia-driver-390 and nvidia- driver-460), but do not appear while using the nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.74 Mon Sep 13 23:09:15 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 25 21:09:03 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.74, 5.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2021-10-21 (3 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: ASUSTeK COMPUTER INC. N551JK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=64128e5f-ba67-49c1-aa02-c19feef6be26 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:br4.6:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:skuASUS-NotebookSKU:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N551JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish nvidia suspend-resume ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948710 Title: Suspend issues with nvidia proprietary driver Status in xorg package in Ubuntu: New Bug description: When I suspend my system, after the screen goes black, the desktop and the suspend login screen are brief
[Touch-packages] [Bug 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)
** Summary changed: - Cursor blinks on screen refresh (only on built in monitor) + Cursor blinks/flickers on screen refresh (only on built in monitor) -- 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/1882212 Title: Cursor blinks/flickers on screen refresh (only on built in monitor) Status in xorg package in Ubuntu: New Bug description: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. When I use the mouse on the external screen the cursor has no problem but when I go on the built-in monitor the pointer will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). My current display settings are: Display Mode: Join Displays Primary Display: either doesn't make any difference Built in display: - Orientation: Landscape - Resolution: 3840x2160 - Refresh Rate: 60,00Hz - Scale: 200% - Fractional Scaling: ON External Display: - Orientation: Landscape - Resolution: 1920x1080 - Refresh Rate: 60,00Hz - Scale: 100% - Fractional Scaling: ON Ubuntu release: 20.04 LTS Xorg version: 1:7.7+19ubuntu14 Expected behavior: Pointer doesn't blink Current behavior: Pointer blinks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 10:27:31 2020 DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2019-07-04 (336 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882212/+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 1882212] Re: Cursor blinks on screen refresh (only on built in monitor)
** Summary changed: - Arrow blinks on screen refresh (only on built in monitor) + Cursor blinks on screen refresh (only on built in monitor) ** Description changed: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. - When I use the mouse on the external screen the arrow indicator has no problem but when I go on the built-in monitor the arrow indicator will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). + When I use the mouse on the external screen the cursor has no problem but when I go on the built-in monitor the pointer will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). My current display settings are: Display Mode: Join Displays Primary Display: either doesn't make any difference Built in display: - Orientation: Landscape - Resolution: 3840x2160 - Refresh Rate: 60,00Hz - Scale: 200% - Fractional Scaling: ON External Display: - Orientation: Landscape - Resolution: 1920x1080 - Refresh Rate: 60,00Hz - Scale: 100% - Fractional Scaling: ON Ubuntu release: 20.04 LTS Xorg version: 1:7.7+19ubuntu14 - Expected behavior: Arrow doesn't blink - Current behavior: Arrow blinks + Expected behavior: Pointer doesn't blink + Current behavior: Pointer blinks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 10:27:31 2020 DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - nvidia, 440.64, 5.4.0-31-generic, x86_64: installed - nvidia, 440.64, 5.4.0-33-generic, x86_64: installed + nvidia, 440.64, 5.4.0-31-generic, x86_64: installed + nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] -Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] + Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] + Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2019-07-04 (336 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1882212 Title: Cursor blinks on screen refresh (only on built in monitor) Status in xorg package in Ubuntu: New Bug description: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. When I use the mouse on
[Touch-packages] [Bug 1882212] [NEW] Cursor blinks on screen refresh (only on built in monitor)
Public bug reported: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. When I use the mouse on the external screen the arrow indicator has no problem but when I go on the built-in monitor the arrow indicator will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). My current display settings are: Display Mode: Join Displays Primary Display: either doesn't make any difference Built in display: - Orientation: Landscape - Resolution: 3840x2160 - Refresh Rate: 60,00Hz - Scale: 200% - Fractional Scaling: ON External Display: - Orientation: Landscape - Resolution: 1920x1080 - Refresh Rate: 60,00Hz - Scale: 100% - Fractional Scaling: ON Ubuntu release: 20.04 LTS Xorg version: 1:7.7+19ubuntu14 Expected behavior: Arrow doesn't blink Current behavior: Arrow blinks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 10:27:31 2020 DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2019-07-04 (336 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago) dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N501VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882212 Title: Cursor blinks on screen refresh (only on built in monitor) Status in xorg package in Ubuntu: New Bug description: I have a double monitor setup, my laptop has a built-in 4k screen and my external is 1080p. When I use the mouse on the external screen the arrow indicator has no problem but when I go on the built-in monitor the arrow indicator will blink (disappear and reappear) every time there is some kind of refresh on either screen (e.g. I type something or something is displaying text in the terminal). My current display settings are: Display Mode: Join Displays Primary Display: either doesn't make any difference Built in display: - Orientation: Landscape - Resolution: 3840x2160 - Refresh Rate: 60,00Hz - Scale: 200% - Fractional Scaling: ON External Display: - Orientation: Landscape - Resolution: 1920x1080 - Refresh Rate: 60,00Hz - Scale: 100% - Fractional Scaling: ON Ubuntu release: 20.04 LTS Xorg version: 1:7.7+19ubuntu14 Expected behavior: Arrow doesn't blink Current behavior: Arrow blinks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
I confirm the bug on 19.10 for DDS files ( from a mod for HOI4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1825963] Re: Abysmal memory leak on tracker-extract
I confirm the bug with DDS files (for an HOI4 mod) in 19.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas
It is possible that this bug is open from 2014 and no one fixed the bug?
I've been last couple of days trying to create a gschema.override file
with relocatable schemas and now I understands that there is a bug
unfixed.
I'm on Debian 9.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1281580
Title:
glib-compile-schemas doesn't compile relocatable schemas
Status in GLib:
Expired
Status in glib2.0 package in Ubuntu:
Confirmed
Bug description:
Dear Developers,
I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10
and, because my wife is using this system as well, I defined some settings in a
gschema.override file.
Everything is working right, except applying settings related to custom
key-bindings.
I added following lines my gschema.override file:
[org.gnome.settings-daemon.plugins.media-keys]
www='w'
email='e'
custom-keybindings =
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
name = 'Launch Gedit'
command = 'gedit'
binding = 'g'
I put my gschema.override file in the '/usr/share/glib-2.0/schemas'
directory. After I added these lines, I ran 'glib-compile-schemas
/usr/share/glib2.0/schemas' and no error was reported.
For testing purposes I created a new user, logged out, and logged in with the
new user. In the best case, the custom key-binding were applied automatically,
but this has not happened. Other defined key-bindings were applied correctly.
In the gnome-control-center's key-bindings tab, the table containing custom
shortcuts is empty, containing one row with empty columns.
Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
/media-keys/custom-keybindings/custom0/' shows, the name, command, and
binding key pairs contain empty ('') values.
If I manually run following commands, the custom key-binding is created
correctly:
gsettings set
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
name "Launch Gedit"
gsettings set
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
command "gedit"
gsettings set
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
binding "g"
Am I doing anything wrong when I want to add a custom key-bindings in
my schema file, or is 'glib-compile-schemas' really not applying this
part from the schema file?
Attila
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglib2.0-bin 2.39.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu4
Architecture: i386
CurrentDesktop: GNOME
Date: Tue Feb 18 13:58:37 2014
InstallationDate: Installed on 2013-12-13 (67 days ago)
InstallationMedia: BeLin 3.02 i386
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1281580/+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 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
Editing source in audacity to "pulse: Internal Mic 0" works on Ubuntu 18.04 and official audacity packager from their ppa version: 2.2.2-1build1 -- 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/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in alsa-driver package in Ubuntu: Expired Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. Steps to reproduce : 1) Install audacity 2.0.3 from official Ubuntu repositories 2) Open Audacity and play something with it 3) That's it : no more headphones sound. - alsa log created with 'alsa-info.sh' (https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/ - pulse log when I plug in my headphones, I run a MP3 file with VLC, close VLC then unplug headphones (https://wiki.ubuntu.com/PulseAudio/Log) : http://paste.ubuntu.com/7131713/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+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 1721880] Re: can't disable wi-fi and system hangs on shutdown
Hi again, I've got an interesting piece of news: I've recently discovered that the problem only appears when I'm connected to the optical fiber network in the flat where I live during the week; when I use ubuntu with the wi-fi at my home (much slower, at 7 Mbps) everything is working just fine. I don't know if there is a problem with the management of the fiber network in Ubuntu or if the issue is caused by a wrong configuration of the router. -- 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/1721880 Title: can't disable wi-fi and system hangs on shutdown Status in network-manager package in Ubuntu: Confirmed Bug description: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1721880/+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 1721880] [NEW] can't disable wi-fi and system hangs on shutdown
Public bug reported: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1721880 Title: can't disable wi-fi and system hangs on shutdown Status in network-manager package in Ubuntu: New Bug description: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled
[Touch-packages] [Bug 1712708] [NEW] USB Keyboard+SmartPad
Public bug reported: The scroll of touchpad dont work, my touchpad is Synaptics, but the system recognizes it as USB Keyboard+SmartPad. More information: I: Bus=0003 Vendor=04f3 Product=0740 Version=0110 N: Name="USB Keyboard+SmartPad" P: Phys=usb-:00:1a.0-1.3.1/input1 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:04F3:0740.0006/input/input15 U: Uniq= H: Handlers=kbd mouse2 event10 B: PROP=0 B: EV=10001f B: KEY=3007f 0 0 48317aff32d bf56 1f0003 130c130b17c000 267bfad941dfed 9e16804400 1002 B: REL=1c3 B: ABS=1f01 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 23 22:01:58 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e1] InstallationDate: Installed on 2017-08-23 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=fd28929f-93e7-4355-acd3-2688ff9aba77 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P10AAT.050.140215.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: XE700T1C-A01CL dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01CL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A: dmi.product.name: 700T1C dmi.product.version: P10AAT dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 23 21:51:10 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1712708 Title: USB Keyboard+SmartPad Status in xorg package in Ubuntu: New Bug description: The scroll of touchpad dont work, my touchpad is Synaptics, but the system recognizes it as USB Keyboard+SmartPad. More information: I: Bus=0003 Vendor=04f3 Product=0740 Version=0110 N: Name="USB Keyboard+SmartPad" P: Phys=usb-:00:1a.0-1.3.1/input1 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:04F3:0740.0006/input/input15 U: Uniq= H: Handlers=kbd mouse2 event10 B: PROP=0 B: EV=10001f B: KEY=3007f 0 0 48317aff32d bf56 1f0003 130c130b17c000 267bfad941dfed 9e16804400 1002 B: REL=1c3 B: ABS=1f01 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture:
[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
Comment #8 worked for me too. Thank you! I'm on an Asus E402S with internal soundcard model Realtek ALC256. I'm running elementaryOS Loki. -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
** Also affects: msttcorefonts (Ubuntu) Importance: Undecided Status: New ** Changed in: msttcorefonts (Ubuntu) Status: New => Invalid ** No longer affects: msttcorefonts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in apt package in Debian: New Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1578951] Re: Libreoffice is crashing causing the session to be booted back to the login screen
It worked only for some time, now (after activating OpenGl renderer) X doesn't crash but Libreoffice exit some seconds after showing CSV import window. On console I receive: intel_do_flush_locked failed: Bad address ** Attachment added: "window showed (with some glitches that occurs with OpenGl renderer)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578951/+attachment/4767560/+files/CSV%20import.png -- 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/1578951 Title: Libreoffice is crashing causing the session to be booted back to the login screen Status in xorg package in Ubuntu: Confirmed Bug description: If I click in a diolog box in Libreoffice, I get a black dialog screen flashing followed by a crash. It goes back to the logon screen within a few seconds. So if after a crash I click in any of the options to recover a document, it crashes again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 6 09:55:58 2016 DistUpgraded: 2016-04-25 20:55:16,587 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed nvidia-304, 304.131, 4.2.0-35-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] InstallationDate: Installed on 2015-05-14 (357 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=9b27492d-b9b9-44b6-aa52-282b2cdd909f ro splash screen vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago) dmi.bios.date: 08/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/28/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67+git1603170630.49041c~gd~w version.libgl1-mesa-dri: libgl1-mesa-dri 11.3~git1603190730.a100d8~gd~w version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.3~git1603190730.a100d8~gd~w version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578951/+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 1578951] Re: Libreoffice is crashing causing the session to be booted back to the login screen
I could always replicate the crash opening a CSV file. Activating OpenGl renderer is a workaround. -- 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/1578951 Title: Libreoffice is crashing causing the session to be booted back to the login screen Status in xorg package in Ubuntu: Confirmed Bug description: If I click in a diolog box in Libreoffice, I get a black dialog screen flashing followed by a crash. It goes back to the logon screen within a few seconds. So if after a crash I click in any of the options to recover a document, it crashes again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 6 09:55:58 2016 DistUpgraded: 2016-04-25 20:55:16,587 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed nvidia-304, 304.131, 4.2.0-35-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] InstallationDate: Installed on 2015-05-14 (357 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=9b27492d-b9b9-44b6-aa52-282b2cdd909f ro splash screen vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago) dmi.bios.date: 08/28/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/28/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67+git1603170630.49041c~gd~w version.libgl1-mesa-dri: libgl1-mesa-dri 11.3~git1603190730.a100d8~gd~w version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.3~git1603190730.a100d8~gd~w version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578951/+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 1567578] [NEW] libnl should be updated to support up to 63 VFs per single PF
Public bug reported: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 14.04.4 libnl nova-compute openstack sriov ubuntu vf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF Status in libnl3 package in Ubuntu: Confirmed Bug description: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1520162] Re: compiled binaries don't work on arm64 64k pages kernel due to alignment
Yes, even though some of the executables are 64K aligned (eg /bin/bash and I can use that as init= without an issue), I do not know why that's the case or if I did something wrong while updating packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1520162 Title: compiled binaries don't work on arm64 64k pages kernel due to alignment Status in binutils package in Ubuntu: New Bug description: Some binaries in 15.10 for aarch64 seem to be compiled with maxpagesize=4K which triggers issues when run on 64K pages arm64 kernels (tested on all kernels back to 4.0). I spotted this while trying to boot an arm64 kernel with 64K pages enabled on 15.10 Ubuntu filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1520162/+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 1520162] Re: Systemd init failure on arm64 64k pages
The following splat is from an aarch64 4.4-rc2 kernel, compiled with 64K pages support, system can't reach user space since systemd fails to execute (the same set-up works for 4K pages kernel). Freeing unused kernel memory: 576K (fe83 - fe8c) Starting init: /sbin/init exists but couldn't execute it (error -22) Starting init: /etc/init exists but couldn't execute it (error -13) Starting init: /bin/sh exists but couldn't execute it (error -14) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. CPU: 2 PID: 1 Comm: init Not tainted 4.4.0-rc2+ #11 Hardware name: ARM Juno development board (r0) (DT) Call trace: [] dump_backtrace+0x0/0x118 [] show_stack+0x14/0x20 [] dump_stack+0x94/0xd0 [] panic+0xd4/0x21c [] kernel_init+0xdc/0xe0 [] ret_from_fork+0x10/0x50 CPU1: stopping CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.0-rc2+ #11 Hardware name: ARM Juno development board (r0) (DT) Call trace: [] dump_backtrace+0x0/0x118 [] show_stack+0x14/0x20 [] dump_stack+0x94/0xd0 [] handle_IPI+0x190/0x1a0 [] gic_handle_irq+0x8c/0xa8 Exception stack(0xfe09401efdb0 to 0xfe09401efed0) fda0: e6c29688 fe007ec54c00 fdc0: fe09401eff00 fe49edf4 8045 fde0: fe09401ec000 0038 0001 fe00: 0002 001a76e7 05dc fe20: fe09401a8090 fe09401efed0 0730 fe40: 0003 ff80 fe60: fdfee27fa440 e6c29688 fe80: fe007ec54c00 fe947938 fea0: e68d40a0 fe90 fe09401ec000 fe007ec54c00 fec0: fe947878 fe09401eff00 [] el1_irq+0x68/0xd8 [] cpuidle_enter+0x18/0x20 [] call_cpuidle+0x24/0x50 [] cpu_startup_entry+0x144/0x218 [] secondary_start_kernel+0x11c/0x140 [<8009073c>] 0x8009073c CPU0: stopping CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-rc2+ #11 Hardware name: ARM Juno development board (r0) (DT) -- 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/1520162 Title: Systemd init failure on arm64 64k pages Status in systemd package in Ubuntu: Incomplete Bug description: Some binaries in 15.10 for aarch64 seem to be compiled with maxpagesize=4K which triggers issues when run on 64K pages arm64 kernels (tested on all kernels back to 4.0). I spotted this while trying to boot an arm64 kernel with 64K pages enabled on 15.10 Ubuntu filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1520162/+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 1520162] Re: Systemd init failure on arm64 64k pages
And this is where I think the problem is, in particular the align field for the LOAD headers. aarch64-linux-gnu-readelf -Wl /lib/systemd/systemd Elf file type is DYN (Shared object file) Entry point 0x2c8d0 There are 10 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align PHDR 0x40 0x0040 0x0040 0x000230 0x000230 R 0x8 INTERP 0x000270 0x0270 0x0270 0x1b 0x1b R 0x1 [Requesting program interpreter: /lib/ld-linux-aarch64.so.1] LOAD 0x00 0x 0x 0x120d5c 0x120d5c R E 0x1000 LOAD 0x120db0 0x00121db0 0x00121db0 0x01faf0 0x020438 RW 0x1000 DYNAMIC0x13f150 0x00140150 0x00140150 0x0002b0 0x0002b0 RW 0x8 NOTE 0x00028c 0x028c 0x028c 0x44 0x44 R 0x4 GNU_EH_FRAME 0x120d54 0x00120d54 0x00120d54 0x08 0x08 R 0x4 GNU_STACK 0x00 0x 0x 0x00 0x00 RW 0 TLS0x120db0 0x00121db0 0x00121db0 0x08 0x84 R 0x8 GNU_RELRO 0x120db0 0x00121db0 0x00121db0 0x01f250 0x01f250 RW 0x8 -- 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/1520162 Title: Systemd init failure on arm64 64k pages Status in systemd package in Ubuntu: Incomplete Bug description: Some binaries in 15.10 for aarch64 seem to be compiled with maxpagesize=4K which triggers issues when run on 64K pages arm64 kernels (tested on all kernels back to 4.0). I spotted this while trying to boot an arm64 kernel with 64K pages enabled on 15.10 Ubuntu filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1520162/+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 1520162] Re: Systemd init failure on arm64 64k pages
** Package changed: ubuntu => systemd (Ubuntu) -- 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/1520162 Title: Systemd init failure on arm64 64k pages Status in systemd package in Ubuntu: New Bug description: Some binaries in 15.10 for aarch64 seem to be compiled with maxpagesize=4K which triggers issues when run on 64K pages arm64 kernels (tested on all kernels back to 4.0). I spotted this while trying to boot an arm64 kernel with 64K pages enabled on 15.10 Ubuntu filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1520162/+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 1426490] Re: cups 2.0.2-1 100% cpu usage
I'm experiencing a similar problem on a fresh new Kubuntu 15.04, but 100% CPU only takes place when I try to add a printer (e.g., using http://localhost:631)... the only thing I find in the syslog is Apr 28 10:58:06 bettini-K53SV /hpfax: [8139]: error: Failed to create /var/spool/cups/tmp/.hplip By the way, when adding a new printer, adding a Samba printer is not proposed (though samba is installed) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1426490 Title: cups 2.0.2-1 100% cpu usage Status in cups package in Ubuntu: Incomplete Bug description: upgraded from xubuntu 14.10 to 15.04 and now it uses cups 2.x after every print cupsd starts using 100% cpu and don't close. have to kill it every time with "sudo pkill cupsd" printing still works fine Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 cups: Installiert: 2.0.2-1ubuntu3 Installationskandidat: 2.0.2-1ubuntu3 Versionstabelle: *** 2.0.2-1ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1426490/+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 1029289] Re: Need to authorize my google account each time I boot the computer
Hi, I'm posting my personal case history hoping this can be useful.
I had two laptops both running Ubuntu12.04 (Gnome, w/o Unity). One of them -
Acer - equipped by 32 bits version, the other - Asus - whith 64 bits version.
No troubles with both even when authenticating at the same time to my google
account. Both never asked me for authorization.
In both laptop I used the "contact" application to keep my google contacts.
Everything was fine.
Now I upgraded Asus to 14.04 (64Bit, of course). This kept about a couple oh
hours then everithing was fine, with the exception of a few details I solved in
the next hours.
Now the situation is as follows:
32 Bits 12.04 Acer everithing is fine, never asks for auth to my google
account. Contacts into the application are fine as ever.
64 Bits 14.04 Asus asks me auth every time I log on, and my contacts are
empty, even after hours from logon. Google account appears in the menu and it
is correctly chosen as contacs source ("Rubrica" in italian).
This situation is up to date at 30/08/2014. Both Ubuntu installations updated
and upgraded.
Hoping this can help developers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-plugin-oauth2 in
Ubuntu.
https://bugs.launchpad.net/bugs/1029289
Title:
Need to authorize my google account each time I boot the computer
Status in Online Accounts: Account plugins:
In Progress
Status in Online Accounts: OAuth2 plug-in:
Unknown
Status in Online Accounts: Sign-on UI:
Fix Released
Status in “account-plugins” package in Ubuntu:
Fix Released
Status in “evolution-data-server” package in Ubuntu:
Confirmed
Status in “signon-plugin-oauth2” package in Ubuntu:
Fix Released
Status in “account-plugins” source package in Quantal:
Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
Fix Released
Bug description:
[Test Case] Sometimes after one day, sometimes after one week, the
system indicator will turn red and the Google account will be marked
as needing reauthentication. Time can vary, but any period shorter
than one month is a symptom of the bug.
[Regression Potential] Minimal: the change to the Google plugin (in
account-plugins) simply changes the authentication method, in a way
that is well-documented. The change in signon-plugin-oauth2 affects
only those accounts/providers which use the OAuth refresh tokens --
which is only Google, at the moment -- and in a way that can't
possibly break any existing functionality; if the new code had some
mistake, the refresh token would be unusable and the system would
automatically fall back to requesting a new access token (which is
exactly what happens now, with this bug).
I'll try to find why the account-plugins package was not uploaded;
indeed, both are required in order to fix this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+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
