[Touch-packages] [Bug 2019940] Re: Directly manipulating NetworkManager keyfiles
Invalid for sosreport We collect NetworkManager and netplan data depending what is available ** Changed in: sosreport (Ubuntu) Status: New => Invalid -- 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/2019940 Title: Directly manipulating NetworkManager keyfiles Status in augeas package in Ubuntu: New Status in calamares package in Ubuntu: New Status in cloud-init package in Ubuntu: Invalid Status in cruft package in Ubuntu: Won't Fix Status in cruft-ng package in Ubuntu: New Status in dracut package in Ubuntu: New Status in forensic-artifacts package in Ubuntu: New Status in guestfs-tools package in Ubuntu: New Status in guix package in Ubuntu: New Status in ltsp package in Ubuntu: Invalid Status in netcfg package in Ubuntu: Won't Fix Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in refpolicy package in Ubuntu: New Status in sosreport package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Status in uhd package in Ubuntu: New Status in vagrant package in Ubuntu: New Bug description: The affected packages can manipulate NetworkManager keyfiles directly on disk, which might not be appropriate anymore on Ubuntu, since the Netplan integration was enabled in NetworkManager (starting with Mantic), migrating any keyfile configuration from /etc/NetworkManager/system-connections/*[.nmconnection] to /etc/netplan/90-NM-*.yaml See Netplan's documentation for how connections are handled: https://netplan.readthedocs.io/en/latest/netplan-everywhere/ PS: Packages were queried using: https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2019198] Re: Very laggy sound when I stream sounds from Android phone to Ubuntu 23.04 via Bluetooth
** Description changed: I have used Ubuntu 22.04 for a long time and I decided to install Ubuntu - 23.04. After installing, I paired my phone's Bluetooth to my laptop and - started to streaming my phone's sounds to be played by my laptop. I - experienced very laggy sound, which was not the case in the 22.04 - version. I had doubt that this problem may be related to my phone. So I - created a live USB from 22.04, and I booted my computer from that USB. - Then I clicked on Try Ubuntu and I paired my phone with live Ubuntu - 22.04 and every thing worked fine. I did the same thing with Ubuntu - 23.04 (booting Ubuntu from live USB and pairing with live OS) and the - problem persisted even with a live fresh OS which nothing had been - installed on it. So this Bluetooth issue is definitely is the 23.04 - problem. Maybe you should increase the latency for Bluetooth buffer. I - tried to fix this problem by installing pulseaudio, but no luck. + 23.04. After installing, I paired my phone's Bluetooth (Samsung Galaxy + A50) to my laptop and started to streaming my phone's sounds to be + played by my laptop. I experienced very laggy sound, which was not the + case in the 22.04 version. I had doubt that this problem may be related + to my phone. So I created a live USB from 22.04, and I booted my + computer from that USB. Then I clicked on Try Ubuntu and I paired my + phone with live Ubuntu 22.04 and every thing worked fine. I did the same + thing with Ubuntu 23.04 (booting Ubuntu from live USB and pairing with + live OS) and the problem persisted even with a live fresh OS which + nothing had been installed on it. So this Bluetooth issue is definitely + is the 23.04 problem. Maybe you should increase the latency for + Bluetooth buffer. I tried to fix this problem by installing pulseaudio, + but no luck. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 11 13:58:55 2023 InstallationDate: Installed on 2023-05-11 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_FMS dmi.board.vendor: CML dmi.board.version: V1.00 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd03/18/2020:br1.0:efr1.0:svnAcer:pnAspireA715-75G:pvrV1.00:rvnCML:rnAzalea_FMS:rvrV1.00:cvnAcer:ct10:cvrV1.00:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-75G dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.system.pa: 2023-05-11T06:24:04.990638 -- 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/2019198 Title: Very laggy sound when I stream sounds from Android phone to Ubuntu 23.04 via Bluetooth Status in pulseaudio package in Ubuntu: New Bug description: I have used Ubuntu 22.04 for a long time and I decided to install Ubuntu 23.04. After installing, I paired my phone's Bluetooth (Samsung Galaxy A50) to my laptop and started to streaming my phone's sounds to be played by my laptop. I experienced very laggy sound, which was not the case in the 22.04 version. I had doubt that this problem may be related to my phone. So I created a live USB from 22.04, and I booted my computer from that USB. Then I clicked on Try Ubuntu and I paired my phone with live Ubuntu 22.04 and every thing worked fine. I did the same thing with Ubuntu 23.04 (booting Ubuntu from live USB and pairing with live OS) and the problem persisted even with a live fresh OS which nothing had been installed on it. So this Bluetooth issue is definitely is the 23.04 problem. Maybe you should increase the latency for Bluetooth buffer. I tried to fix this problem by installing pulseaudio, but no luck. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 2018954] Re: 600+ duplicate icons exist in the ubuntu-themes packages including ubuntu-mono .
Hello there! It sounds like you're encountering an issue with duplicate icons in the ubuntu-themes package, including ubuntu-mono. This can be a frustrating problem to deal with, but there are a few potential solutions you could try. First, you could try removing and reinstalling the ubuntu-themes package. This can sometimes resolve issues with duplicate icons or other package errors. You could do this through the terminal using the following command: sudo apt-get remove ubuntu-themes && sudo apt-get install ubuntu-themes. Another potential solution is to manually delete the duplicate icons. To do this, you'll need to navigate to the directory where the icons are located and delete the duplicates. You can do this using the file manager or the terminal, depending on your preference. If neither of these solutions works, you could try reaching out to the Ubuntu community for assistance. There are forums and support channels where you can ask for help with Ubuntu-related issues. I hope one of these solutions helps you resolve the issue with the duplicate icons. Good luck, and let me know if there's anything else I can do to assist you!https://instanderapps.com/instander-for-ios/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/2018954 Title: 600+ duplicate icons exist in the ubuntu-themes packages including ubuntu-mono . Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: Using find for duplicates shows 1099 duplicate or related to duplicate files between the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/2018954/+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 2016082] Re: CUPS doesnt add my HP LasterJet MFP N280nw anymore
Source : https://bugs.launchpad.net/ubuntu/+source/android- androresolvd/+bug/1803663/comments/2 -- 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/2016082 Title: CUPS doesnt add my HP LasterJet MFP N280nw anymore Status in cups package in Ubuntu: New Bug description: With the latest update, I dont even get a printer added anymore. Also manual adding doesnt work. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 13 12:38:49 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS System Product Name Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016082/+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 2001721] [NEW] Ubuntu screen flickering
Public bug reported: Hi i did use ubuntu for more than a year on this laptop last a few days i used HDMI cable, today for a few hours i did use a new cable "longer one" now suddenly my laptop display went green as you can see in the attachment i did some search but can't find solution. https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534 Ali ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 4 22:41:41 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev e2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a] InstallationDate: Installed on 2021-12-20 (380 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 81N3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash acpi=force vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: AYCN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15AST dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST: dmi.product.family: IdeaPad S145-15AST dmi.product.name: 81N3 dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST dmi.product.version: Lenovo IdeaPad S145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 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 third-party-packages 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/2001721 Title: Ubuntu screen flickering Status in xorg package in Ubuntu: New Bug description: Hi i did use ubuntu for more than a year on this laptop last a few days i used HDMI cable, today for a few hours i did use a new cable "longer one" now suddenly my laptop display went green as you can see in the attachment i did some search but can't find solution. https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534 Ali ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 4 22:41:41 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev e2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a] InstallationDate: Installed on 2021-12-20 (380 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 81N3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash acpi=force vt.handoff=7 SourcePackage: xorg
[Touch-packages] [Bug 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort
Also tried folly (the dependency of mcrouter that was throwing the exception) and unit tests that previously failed because of this bug now pass. ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1999104 Title: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Bionic: Fix Committed Status in libunwind source package in Focal: Fix Committed Bug description: [Impact] On architectures other than i386 and amd64, the C++ exception support in libunwind appears to be broken, always failing and calling std::terminate() which leads to the program aborting. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0xf7c2daac in __GI_abort () at abort.c:79 #2 0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #3 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #4 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #5 0xf7e1f5e0 in __cxa_rethrow () from /lib/aarch64-linux-gnu/libstdc++.so.6 #6 0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #7 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #8 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #9 0xf7e1f574 in __cxa_throw () from /lib/aarch64-linux-gnu/libstdc++.so.6 #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9 #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9 Compiling libunwind with --enable-cxx-exceptions enabled leads to _Unwind_RaiseException being called during __cxa_throw(), which fails to find a handler, and the generic std::terminate() is called instead, aborting the program. On i386 and amd64 this doesn't seem to be the case, and the libunwind handlers seem to be present. To fix, we only enable the configure option --enable-cxx-exceptions on i386 and amd64 only, in debian/rules. This lets other architectures fall back to the symbols provided by libgcc_s, which implementation works correctly. [Testcase] Ali Sadi has provided a reproducer program. Start an arm64 instance, for example, a c6g.medium instance on AWS, with either Bionic or Focal. $ wget https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz $ sudo apt install -y build-essential libunwind-dev $ tar xvf libunwind.tar.gz && cd test $ make all There are two executable, main and main_unwind. main is not linked to libunwind, and main_unwind is linked to libunwind. $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) If you install the test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test $ make clean $ sudo apt install -y libunwind-dev $ make all $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main The exception is caught as expected the program does not abort. [Where problems could occur] For architectures other than i386 and amd64, we are changing from libunwind provided exception handlers for __cxa_throw(), and using those provided by libgcc_s instead. There are a few reverse dependencies for libunwind-dev and libunwind8, which need to be considered: $ apt rdepends libunwind-dev libunwind-dev Reverse Depends: Depends: libunwind-setjmp0-dev (= 1.2.1-9build1) Depends: libefl-all-dev t$ apt rdepends libunwind-dev8 libunwind8 Reverse Depends: Depends: libunwind-dev (= 1.2.1-9build1) Depends: xvfb Depends: xnest Depends: xdmx Depends: xwayland Depends: xserver-xorg-core Depends: xserver-xephyr Depends: linux-tools-5.4.0-* Depends: linux-raspi-tools-* Depends: linux-raspi2-tools-5.4.0-* Depends: linux-raspi2-5.4-tools-5.4.0-* Depends: linux-oracle-5.15-tools-5.15.0-* Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-* Depends: linux-hwe-5.8-tools-5.8.0-* Depends: linux-hwe-5.15-tools-5.15.0-* Depends: linux-gke-tools-5.4.0-* Depends: linux-gke-5.15-tools-5.15.0-* Depends: linux-gcp-tools-5.4.0-* Depends: linux-gcp-5.15-tools-5.15.0-* Depends: linux-azure-tools-5.4.0-* Depends: linux-azure-5.15-tools-5.15.0-* Depends: linux-aws-too
[Touch-packages] [Bug 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort
Tested on bionic with package libunwind8_1.2.1-8ubuntu0.1 and the reproducer ran successfully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1999104 Title: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Bionic: Fix Committed Status in libunwind source package in Focal: Fix Committed Bug description: [Impact] On architectures other than i386 and amd64, the C++ exception support in libunwind appears to be broken, always failing and calling std::terminate() which leads to the program aborting. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0xf7c2daac in __GI_abort () at abort.c:79 #2 0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #3 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #4 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #5 0xf7e1f5e0 in __cxa_rethrow () from /lib/aarch64-linux-gnu/libstdc++.so.6 #6 0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #7 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #8 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #9 0xf7e1f574 in __cxa_throw () from /lib/aarch64-linux-gnu/libstdc++.so.6 #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9 #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9 Compiling libunwind with --enable-cxx-exceptions enabled leads to _Unwind_RaiseException being called during __cxa_throw(), which fails to find a handler, and the generic std::terminate() is called instead, aborting the program. On i386 and amd64 this doesn't seem to be the case, and the libunwind handlers seem to be present. To fix, we only enable the configure option --enable-cxx-exceptions on i386 and amd64 only, in debian/rules. This lets other architectures fall back to the symbols provided by libgcc_s, which implementation works correctly. [Testcase] Ali Sadi has provided a reproducer program. Start an arm64 instance, for example, a c6g.medium instance on AWS, with either Bionic or Focal. $ wget https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz $ sudo apt install -y build-essential libunwind-dev $ tar xvf libunwind.tar.gz && cd test $ make all There are two executable, main and main_unwind. main is not linked to libunwind, and main_unwind is linked to libunwind. $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) If you install the test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test $ make clean $ sudo apt install -y libunwind-dev $ make all $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main The exception is caught as expected the program does not abort. [Where problems could occur] For architectures other than i386 and amd64, we are changing from libunwind provided exception handlers for __cxa_throw(), and using those provided by libgcc_s instead. There are a few reverse dependencies for libunwind-dev and libunwind8, which need to be considered: $ apt rdepends libunwind-dev libunwind-dev Reverse Depends: Depends: libunwind-setjmp0-dev (= 1.2.1-9build1) Depends: libefl-all-dev t$ apt rdepends libunwind-dev8 libunwind8 Reverse Depends: Depends: libunwind-dev (= 1.2.1-9build1) Depends: xvfb Depends: xnest Depends: xdmx Depends: xwayland Depends: xserver-xorg-core Depends: xserver-xephyr Depends: linux-tools-5.4.0-* Depends: linux-raspi-tools-* Depends: linux-raspi2-tools-5.4.0-* Depends: linux-raspi2-5.4-tools-5.4.0-* Depends: linux-oracle-5.15-tools-5.15.0-* Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-* Depends: linux-hwe-5.8-tools-5.8.0-* Depends: linux-hwe-5.15-tools-5.15.0-* Depends: linux-gke-tools-5.4.0-* Depends: linux-gke-5.15-tools-5.15.0-* Depends: linux-gcp-tools-5.4.0-* Depends: linux-gcp-5.15-tools-5.15.0-* Depends: linux-azure-tools-5.4.0-* Depends: linux-azure-5.15-tools-5.15.0-* Depends: linux-aws-tools-5.4.0-* Depends: linux-aws-5.8-tools-5.8.0-* Depends: linux-aws-5.15-tools-5.15.0-* Depends: xvfb Depends: xnest Depends: xdmx Depends: trafficserver Depend
[Touch-packages] [Bug 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort
Tested on focal with package libunwind8_1.2.1-9ubuntu0.1 and the reproducer ran successfully -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1999104 Title: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Bionic: Fix Committed Status in libunwind source package in Focal: Fix Committed Bug description: [Impact] On architectures other than i386 and amd64, the C++ exception support in libunwind appears to be broken, always failing and calling std::terminate() which leads to the program aborting. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0xf7c2daac in __GI_abort () at abort.c:79 #2 0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #3 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #4 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #5 0xf7e1f5e0 in __cxa_rethrow () from /lib/aarch64-linux-gnu/libstdc++.so.6 #6 0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #7 0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6 #8 0xf7e1f280 in std::terminate() () from /lib/aarch64-linux-gnu/libstdc++.so.6 #9 0xf7e1f574 in __cxa_throw () from /lib/aarch64-linux-gnu/libstdc++.so.6 #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9 #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9 Compiling libunwind with --enable-cxx-exceptions enabled leads to _Unwind_RaiseException being called during __cxa_throw(), which fails to find a handler, and the generic std::terminate() is called instead, aborting the program. On i386 and amd64 this doesn't seem to be the case, and the libunwind handlers seem to be present. To fix, we only enable the configure option --enable-cxx-exceptions on i386 and amd64 only, in debian/rules. This lets other architectures fall back to the symbols provided by libgcc_s, which implementation works correctly. [Testcase] Ali Sadi has provided a reproducer program. Start an arm64 instance, for example, a c6g.medium instance on AWS, with either Bionic or Focal. $ wget https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz $ sudo apt install -y build-essential libunwind-dev $ tar xvf libunwind.tar.gz && cd test $ make all There are two executable, main and main_unwind. main is not linked to libunwind, and main_unwind is linked to libunwind. $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) If you install the test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test $ make clean $ sudo apt install -y libunwind-dev $ make all $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main The exception is caught as expected the program does not abort. [Where problems could occur] For architectures other than i386 and amd64, we are changing from libunwind provided exception handlers for __cxa_throw(), and using those provided by libgcc_s instead. There are a few reverse dependencies for libunwind-dev and libunwind8, which need to be considered: $ apt rdepends libunwind-dev libunwind-dev Reverse Depends: Depends: libunwind-setjmp0-dev (= 1.2.1-9build1) Depends: libefl-all-dev t$ apt rdepends libunwind-dev8 libunwind8 Reverse Depends: Depends: libunwind-dev (= 1.2.1-9build1) Depends: xvfb Depends: xnest Depends: xdmx Depends: xwayland Depends: xserver-xorg-core Depends: xserver-xephyr Depends: linux-tools-5.4.0-* Depends: linux-raspi-tools-* Depends: linux-raspi2-tools-5.4.0-* Depends: linux-raspi2-5.4-tools-5.4.0-* Depends: linux-oracle-5.15-tools-5.15.0-* Depends: linux-lowlatency-hwe-5.15-tools-5.15.0-* Depends: linux-hwe-5.8-tools-5.8.0-* Depends: linux-hwe-5.15-tools-5.15.0-* Depends: linux-gke-tools-5.4.0-* Depends: linux-gke-5.15-tools-5.15.0-* Depends: linux-gcp-tools-5.4.0-* Depends: linux-gcp-5.15-tools-5.15.0-* Depends: linux-azure-tools-5.4.0-* Depends: linux-azure-5.15-tools-5.15.0-* Depends: linux-aws-tools-5.4.0-* Depends: linux-aws-5.8-tools-5.8.0-* Depends: linux-aws-5.15-tools-5.15.0-* Depends: xvfb Depends: xnest Depends: xdmx Depends: trafficserver Depends: tilix
[Touch-packages] [Bug 1999104] [NEW] libunwind causes crashes on arm64
Public bug reported: There is a bug in libunwind in both 18.04 and 20.04 on arm64 where when linked with libunwind instead of catching an exception, the program crashes. This was first seen on mcrouter, but attached is a small reproducer where `main_unwind` will crash. The libunwind shipping with 22.04 doesn't appear to have this problem, nor do unmodified upstream versions (including the 1.2.1 which is the 18.04 and 20.04 version). Attached is a small reproducer that demonstrates the problem. Ubuntu 22.04: ``` $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main ``` Ubuntu 20.04: ``` $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) ``` ** Affects: libunwind (Ubuntu) Importance: Undecided Status: New ** Attachment added: "small reproducer" https://bugs.launchpad.net/bugs/1999104/+attachment/5635122/+files/libunwind.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1999104 Title: libunwind causes crashes on arm64 Status in libunwind package in Ubuntu: New Bug description: There is a bug in libunwind in both 18.04 and 20.04 on arm64 where when linked with libunwind instead of catching an exception, the program crashes. This was first seen on mcrouter, but attached is a small reproducer where `main_unwind` will crash. The libunwind shipping with 22.04 doesn't appear to have this problem, nor do unmodified upstream versions (including the 1.2.1 which is the 18.04 and 20.04 version). Attached is a small reproducer that demonstrates the problem. Ubuntu 22.04: ``` $ ./main int throws lib int caught main $ ./main_unwind int throws lib int caught main ``` Ubuntu 20.04: ``` $ ./main int throws lib int caught main $ ./main_unwind terminate called after throwing an instance of 'int' terminate called recursively Aborted (core dumped) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
can this be a solution ?
https://stackoverflow.com/questions/2895816/how-do-i-strip-local-
symbols-from-linux-kernel-module-without-breaking-it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
[Touch-packages] [Bug 1968622] [NEW] [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card.
Public bug reported: Audio only had "Dummy output" as output but after running: $ echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf audio output changed to HDMI/Built-in-Audio however the sound is still not working sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 22:58:11 2022 InstallationDate: Installed on 2022-03-23 (19 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 2.19 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.19 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B4 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.19 dmi.modalias: dmi:bvnHUAWEI:bvr2.19:bd12/09/2021:br2.19:efr2.19:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1968622 Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. Status in pulseaudio package in Ubuntu: New Bug description: Audio only had "Dummy output" as output but after running: $ echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf audio output changed to HDMI/Built-in-Audio however the sound is still not working sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 22:58:11 2022 InstallationDate: Installed on 2022-03-23 (19 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 2.19 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.19 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B4 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.19 dmi.modalias: dmi:bvnHUAWEI:bvr2.19:bd12/09/2021:br2.19:efr2.19:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1942176] [NEW] While printing the printer is printing an error message on the sheet cups_handleerror
Public bug reported:
When using the printer it prints this on the sheet:
___
userdict dup(\004)cvn{}put (\004\004)cvn{}put
/cups_handleerror{
2B$error /newerror false put
(:PostScript error in") print cups_query_keywords print (": ) print
$error /errorname get 128 string cvs print
(;offending command:) print $error /command get 128 string cvs print(
) print flush
} bind def
errordict /timeout {} put
/cups_query_query_keyword(?Unknown) def
_
THIS IS THE TERMINAL OUTPUT
overlord@OverLord:~$ lsmod|grep usb
usbhid 57344 0
hid 135168 2 usbhid,hid_generic
btusb 61440 0
btrtl 24576 1 btusb
btbcm 16384 1 btusb
btintel28672 1 btusb
bluetooth 638976 15 btrtl,btintel,btbcm,bnep,btusb,rfcomm
overlord@OverLord:~$ tail -f /var/log/syslog
Aug 31 12:43:40 OverLord kernel: [71467.827350] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:43:40 OverLord systemd[1]: Started Configure Plugged-In Printer.
Aug 31 12:43:40 OverLord udev-configure-printer: add usb-001-006
Aug 31 12:43:41 OverLord udev-configure-printer: device devpath is
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1
Aug 31 12:43:41 OverLord udev-configure-printer: MFG:EPSON MDL:L220 Series
SERN:- serial:5647584B3134343800
Aug 31 12:43:41 OverLord kernel: [71468.715833] usb 1-1.1: USB disconnect,
device number 6
Aug 31 12:43:41 OverLord kernel: [71468.716232] usblp1: removed
Aug 31 12:43:41 OverLord udev-configure-printer: remove
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1
Aug 31 12:43:48 OverLord udev-configure-printer: no corresponding CUPS device
found
Aug 31 12:43:48 OverLord systemd[1]: configure-printer@usb-001-006.service:
Succeeded.
Aug 31 12:44:33 OverLord kernel: [71520.685232] usb 1-1.1: new full-speed USB
device number 7 using ehci-pci
Aug 31 12:44:34 OverLord kernel: [71520.957538] usb 1-1.1: New USB device
found, idVendor=04b8, idProduct=08d1, bcdDevice= 1.00
Aug 31 12:44:34 OverLord kernel: [71520.957549] usb 1-1.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Aug 31 12:44:34 OverLord kernel: [71520.957553] usb 1-1.1: Product: EPSON L220
Series
Aug 31 12:44:34 OverLord kernel: [71520.957556] usb 1-1.1: Manufacturer: EPSON
Aug 31 12:44:34 OverLord kernel: [71520.957559] usb 1-1.1: SerialNumber:
5647584B3134343800
Aug 31 12:44:34 OverLord kernel: [71521.306906] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:44:34 OverLord systemd[1]: Started Configure Plugged-In Printer.
Aug 31 12:44:34 OverLord udev-configure-printer: add usb-001-007
Aug 31 12:44:34 OverLord udev-configure-printer: device devpath is
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1
Aug 31 12:44:34 OverLord udev-configure-printer: MFG:EPSON MDL:L220 Series
SERN:- serial:5647584B3134343800
Aug 31 12:44:39 OverLord kernel: [71526.576813] usblp1: removed
Aug 31 12:44:40 OverLord kernel: [71527.090914] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:44:41 OverLord udev-configure-printer: URI contains USB serial number
Aug 31 12:44:41 OverLord udev-configure-printer: URI match:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1
Aug 31 12:44:41 OverLord udev-configure-printer: URI of detected printer:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1, normalized:
epson l220 series serial 5647584b3134343800 interface 1
Aug 31 12:44:41 OverLord udev-configure-printer: URI of print queue:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1, normalized:
epson l220 series serial 5647584b3134343800 interface 1
Aug 31 12:44:41 OverLord udev-configure-printer: Queue
ipp://localhost/printers/L220-Series has matching device URI
Aug 31 12:44:41 OverLord udev-configure-printer: Re-enabled printer
ipp://localhost/printers/L220-Series
Aug 31 12:44:41 OverLord systemd[1]: configure-printer@usb-001-007.service:
Succeeded.
Aug 31 12:44:46 OverLord telegram-desktop_telegram-desktop.desktop[53993]:
OpenType support missing for "DAOpenSansSemibold", script 12
^C
overlord@OverLord:~$ lsusb
Bus 002 Device 040: ID 04f2:b249 Chicony Electronics Co., Ltd
Bus 002 Device 044: ID 1a2c:4c5e China Resource Semico Co., Ltd
Bus 002 Device 043: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical
Mouse
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR
Bus 001 Device 007: ID 04b8:08d1 Seiko Epson Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002
[Touch-packages] [Bug 1938983] Re: missing modules after 5.11.0-25-generic update
it happened with me with with kubuntu 20.04.2.0 fresh install the problem first appeared during installing the first upgrades after OS installlation during the installation of linux 5.11.0-25 it showed me the same message that is in bug description such as "update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915" etc... remember this happened after fresh install first update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1938983 Title: missing modules after 5.11.0-25-generic update Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After updating to kernel 5.11.0-25-generic wireless driver failed to recognize WiFi card. Possible reasons/symptoms: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: July2021 Release: 20.04 Codename: focal Workaround: connected Ethernet. (Inconvenient) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+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 1939593] [NEW] package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 11 14:05:20 2021 DuplicateSignature: package:python3:3.8.2-0ubuntu2 Removing python3 (3.8.2-0ubuntu2) ... /var/lib/dpkg/info/python3.prerm: 5: py3clean: not found dpkg: error processing package python3 (--remove): installed python3 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed python3 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-12-20 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.6, Python 3.6.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1939593 Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 11 14:05:20 2021 DuplicateSignature: package:python3:3.8.2-0ubuntu2 Removing python3 (3.8.2-0ubuntu2) ... /var/lib/dpkg/info/python3.prerm: 5: py3clean: not found dpkg: error processing package python3 (--remove): installed python3 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed python3 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-12-20 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.6, Python 3.6.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1939593/+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 1939594] [NEW] package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127
*** This bug is a duplicate of bug 1939593 *** https://bugs.launchpad.net/bugs/1939593 Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 11 14:05:20 2021 DuplicateSignature: package:python3:3.8.2-0ubuntu2 Removing python3 (3.8.2-0ubuntu2) ... /var/lib/dpkg/info/python3.prerm: 5: py3clean: not found dpkg: error processing package python3 (--remove): installed python3 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed python3 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-12-20 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.6, Python 3.6.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1939594 Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 11 14:05:20 2021 DuplicateSignature: package:python3:3.8.2-0ubuntu2 Removing python3 (3.8.2-0ubuntu2) ... /var/lib/dpkg/info/python3.prerm: 5: py3clean: not found dpkg: error processing package python3 (--remove): installed python3 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed python3 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-12-20 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.6, Python 3.6.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1939594/+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 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working
Having the same problem with a 2017 12” Macbook (the Macbook10,2). The microphone shows up as “(unplugged)” in pavucontrol and pacmd regardless of if I have the headset plugged into the combo jack or not. Headphones are detected and work. The internal mic is still accessible and the Microphone input seems to be mirrorring it (could be to do with some chip-level switching that somehow doesn’t happen on Linux?). I’ve tried inputting all choices of model available in the CS4208 quirk list for PulseAudio (there isn’t one for my particular model) into alsa-base.conf and nothing has changed (having nothing in alsa-base.conf, which I did before attempting this fix, also makes no difference). I’m running Debian 10 with kernel 4.19.0-17-amd64. -- 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/1410618 Title: MacBook Air 6,2 TRRS Headset Mic Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello, I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus Logic CS4208 and would love to get the microphone part of the TRRS connector working. Mac OS picks up and utilizes the TRRS headset mic without issue so I know the hardware is a go. With the headset plugged in, running sudo hdajacksensetest -a results in: Pin 0x05 ( Digital Out, HDMI): present = No Pin 0x06 ( Digital Out, HDMI): present = No Pin 0x07 ( Digital Out, HDMI): present = No AlsaInfo output here: http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83 I opened up hdajackretask to find four pins: Green Headphone Pin ID: 0x10 Headphone Internal Speaker Pin ID: 0x12 Internal speaker Pink Mic Pin ID: 0x18 Not connected Internal Mic Pin ID: 0x1c Internal mic Unplugging and replugging the headset changes the Output device in sound settings from Headphones to Speakers so that works, but nothing in the input tab ever changes. It always lists two devices: Internal Microphone and Microphone. Both of these seem to actually be the internal microphone in the mac - either works without the headset connected at all. So I'm not really sure how to proceed from here, but I'd be happy to run whatever diagnostic tests might prove useful and/or even contribute code toward a fix - but I just have no idea where to start. Is it as simple as just finding the right pin and telling the system to use it as a microphone? Similar bug report here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+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 1933864] [NEW] Bluetooth sound card not detected.
Public bug reported: When the laptop starts then i can not turn bluetooth on, it remains off. To make bluetooth work i need to disable wifi and bluetooth hardware for a few minutes then enable it. 90 percent time it works. if this didn't start the service then enabling and disabling airplane mode works. Some times it really frustrates. kindly look at this bug. I have this old laptop through which i study. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 1464 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 23:35:37 2021 InstallationDate: Installed on 2021-06-22 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard ** 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/1933864 Title: Bluetooth sound card not detected. Status in alsa-driver package in Ubuntu: New Bug description: When the laptop starts then i can not turn bluetooth on, it remains off. To make bluetooth work i need to disable wifi and bluetooth hardware for a few minutes then enable it. 90 percent time it works. if this didn't start the service then enabling and disabling airplane mode works. Some times it really frustrates. kindly look at this bug. I have this old laptop through which i study. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 1464 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 23:35:37 2021 InstallationDate: Installed on 2021-06-22 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933864/+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 1933259] Re: Bluetooth not working/can't turn it on
I should mention that bluetooth was working on 20.04 and 20.10 but after upgrade to 21.04 it doesn't work anymore. -- 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/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1933259] [NEW] Bluetooth not working/can't turn it on
Public bug reported: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth bluetoothctl -- 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/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1932377] [NEW] [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i ne
Public bug reported: firstly bluetooth services is somehow dead. to make it work we need to disable the hardware for some time so that in power settings both wifi and bluetooth is turned off and them enable it again for bluetooth to work. and after that if bluetooth is connected automatically then the audio input and output both works from laptop and after removing and adding again the bluetooth then only output is given from headphone. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:26:55 2021 InstallationDate: Installed on 2021-01-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel MID, playback] No sound at all UpgradeStatus: Upgraded to hirsute on 2021-06-08 (9 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1932377 Title: [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i need to remove them from settings and addd them again. hp pavillion g6 Status in alsa-driver package in Ubuntu: New Bug description: firstly bluetooth services is somehow dead. to make it work we need to disable the hardware for some time so that in power settings both wifi and bluetooth is turned off and them enable it again for bluetooth to work. and after that if bluetooth is connected automatically then the audio input and output both works from laptop and after removing and adding again the bluetooth then only output is given from headphone. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:26:55 2021 InstallationDate: Installed on 2021-01-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel MID, playback] No sound at all UpgradeStatus: Upgraded to hirsute on 2021-06-08 (9 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias:
[Touch-packages] [Bug 1911472] Re: ubuntu 16.04.7 timedatectl
It seems that bug is now (2021/01/30) fixed by recent update. Thanks dev team :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1911472 Title: ubuntu 16.04.7 timedatectl Status in tzdata package in Ubuntu: New Bug description: Hello, after recent tzdata update in ubuntu 16.04.7 (Desktop), the "timedatectl" command shows this error: user@host:~$ timedatectl Assertion 'xstrftime: a[] must be big enough' failed at ../src/timedate/timedatectl.c:113, function print_status_info(). Aborting. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1911472/+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 1911472] [NEW] ubuntu 16.04.7 timedatectl
Public bug reported: Hello, after recent tzdata update in ubuntu 16.04.7 (Desktop), the "timedatectl" command shows this error: user@host:~$ timedatectl Assertion 'xstrftime: a[] must be big enough' failed at ../src/timedate/timedatectl.c:113, function print_status_info(). Aborting. Aborted (core dumped) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1911472 Title: ubuntu 16.04.7 timedatectl Status in tzdata package in Ubuntu: New Bug description: Hello, after recent tzdata update in ubuntu 16.04.7 (Desktop), the "timedatectl" command shows this error: user@host:~$ timedatectl Assertion 'xstrftime: a[] must be big enough' failed at ../src/timedate/timedatectl.c:113, function print_status_info(). Aborting. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1911472/+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 1909143] [NEW] df & mount aliases to hide reports for snap mounts
Public bug reported: I would purpose the following aliases as defaults for Hirsute: alias df="df -x squashfs" alias mount="mount -t nosquashfs,nocgroup,nsfs,tmpfs,fuse" My rationale: The output of df and mount are currently cluttered because of snap mounts. df & mount information on snap packages are usually irrelevant for most end-users and rather create more confusion. ** Affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1909143 Title: df & mount aliases to hide reports for snap mounts Status in bash package in Ubuntu: New Bug description: I would purpose the following aliases as defaults for Hirsute: alias df="df -x squashfs" alias mount="mount -t nosquashfs,nocgroup,nsfs,tmpfs,fuse" My rationale: The output of df and mount are currently cluttered because of snap mounts. df & mount information on snap packages are usually irrelevant for most end-users and rather create more confusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1909143/+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 1909132] [NEW] wavy diagonal line when scrolling in firefox
Public bug reported: Scrolling in Firefox moves the web page up and down, but also causes a wavy line to appear, that extends horizontally and diagonally across the page, and disappears once you stop scrolling. i use ubuntu20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 23 21:32:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-srv, 450.80.02, 5.4.0-58-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1b10] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:1b10] InstallationDate: Installed on 2020-12-19 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3496 IMC Networks Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542URV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-generic root=UUID=2b8aa80b-3a8c-4397-9c75-472b469e71ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542URV.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542URV 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.:bvrX542URV.308:bd05/21/2019:svnASUSTeKCOMPUTERINC.:pnX542URV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542URV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X542URV 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1909132 Title: wavy diagonal line when scrolling in firefox Status in xorg package in Ubuntu: New Bug description: Scrolling in Firefox moves the web page up and down, but also causes a wavy line to appear, that extends horizontally and diagonally across the page, and disappears once you stop scrolling. i use ubuntu20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
[Touch-packages] [Bug 1904525] [NEW] Audio balance settings is reset when the volume is turned down to the end.
Public bug reported: Audio balance settings is reset when the volume is turned down to the end. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alikosen 1560 F pulseaudio /dev/snd/pcmC0D0p: alikosen 1560 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 17 10:47:56 2020 InstallationDate: Installed on 2020-11-11 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dahili Ses - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Kas 17 09:05:03 LIPG500 dbus-daemon[770]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Kas 17 09:05:44 LIPG500 systemd[952]: pulseaudio.service: Succeeded. Kas 17 09:05:54 LIPG500 systemd[952]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [VIWGP, Conexant CX20757, Black Headphone Out, Left] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN25WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pnVIWGP:pvrINVALID:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: VIWGP dmi.product.sku: LENOVO_BI_IDEAPAD78 dmi.product.version: INVALID dmi.sys.vendor: LENOVO ** 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/1904525 Title: Audio balance settings is reset when the volume is turned down to the end. Status in alsa-driver package in Ubuntu: New Bug description: Audio balance settings is reset when the volume is turned down to the end. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alikosen 1560 F pulseaudio /dev/snd/pcmC0D0p: alikosen 1560 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 17 10:47:56 2020 InstallationDate: Installed on 2020-11-11 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dahili Ses - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Kas 17 09:05:03 LIPG500 dbus-daemon[770]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=125 pid=972 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Kas 17 09:05:44 LIPG500 systemd[952]: pulseaudio.service: Succeeded. Kas 17 09:05:54 LIPG500 systemd[952]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [VIWGP, Conexant CX20757, Black Headphone Out, Left] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN25WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pnVIWGP:pvrINVALID:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrINVALID: dmi.product.family: IDEAPAD dmi.product.name: VIWGP dmi.product.sku: LENOVO_BI_IDEAPAD78 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1693024] Re: can't start JACK with real-time scheduling even when in audio group
*** This bug is a duplicate of bug 1627769 *** https://bugs.launchpad.net/bugs/1627769 exactly same problem ubuntu 18.04.03 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1693024 Title: can't start JACK with real-time scheduling even when in audio group Status in jackd2 package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at http://jackaudio.org/faq/linux_rt_config.html But when I start JACK it reports Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error I am in the 'audio' group in /etc/group: adam:~$ grep audio /etc/group audio:x:29:pulse,adam adam:~$ (I restarted the machine after adding myself to this group.) 'ulimit' isn't showing real-time priority privileges for me: adam:~$ ulimit -a | grep real real-time priority (-r) 0 adam:~$ The file /etc/security/limits.d/audio.conf looks like this: === # Provided by the jackd package. # # Changes to this file will be preserved. # # If you want to enable/disable realtime permissions, run # #dpkg-reconfigure -p high jackd @audio - rtprio 95 @audio - memlockunlimited #@audio - nice -19 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1693024/+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 1857652] [NEW] Loud background hiss when using headphones (XPS 13 9350)
Public bug reported: Whenever I play audio, I head a loud hiss from my headphones. The hiss stops after a few seconds if I pause the audio, but starts again when I start it. The hiss goes away if I open 'alsamixer' and increase 'Headphone Mic Boost', but I'm not sure if this is expected behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: qasim 850 F pulseaudio /dev/snd/pcmC0D0p: qasim 850 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 26 16:33:21 2019 InstallationDate: Installed on 2019-12-21 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd01/22/2019:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.product.sku: 0704 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1857652 Title: Loud background hiss when using headphones (XPS 13 9350) Status in alsa-driver package in Ubuntu: New Bug description: Whenever I play audio, I head a loud hiss from my headphones. The hiss stops after a few seconds if I pause the audio, but starts again when I start it. The hiss goes away if I open 'alsamixer' and increase 'Headphone Mic Boost', but I'm not sure if this is expected behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: qasim 850 F pulseaudio /dev/snd/pcmC0D0p: qasim 850 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 26 16:33:21 2019 InstallationDate: Installed on 2019-12-21 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd01/22/2019:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.product.sku: 0704 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857652/+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 1840510] Re: Please enable PGO and LTO for arm64
Some of the subcomponents of the pyperformance suite: https://github.com/python/pyperformance/tree/master/pyperformance/benchmarks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1840510 Title: Please enable PGO and LTO for arm64 Status in python3-defaults package in Ubuntu: New Bug description: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+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 1834333] Re: Scaling problem with Qt apps
@mitya57 How can u use this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1834333 Title: Scaling problem with Qt apps Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: Hi I have problem with scaling for Qt apps. when i open Kolourpaint scaling is too small i have Ubuntu 18.04 and install from snap and apt i first report to bugs.kde.org and they tell me to report here https://bugs.kde.org/show_bug.cgi?id=407668 Kolourpaint its not only app with problem , anydesk , filezilla , pylon viewer , dukto , stacer , vmware horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1834333/+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 1840510] [NEW] Please enable PGO and LTO for arm64
Public bug reported: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1840510 Title: Please enable PGO and LTO for arm64 Status in python3-defaults package in Ubuntu: New Bug description: The rules file conditionally enables PGO and LTO in the python3 build and while it's enabled for many platforms it's not enabled for arm64. This is worth about 30% performance. Please enable it. A patch is available here with the original debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+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 1837330] [NEW] Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations
Public bug reported: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily repeatable if you have two monitors with two refresh rates, I suppose. After you set up your monitors, make sure to enable 144 Hz, then "test" it by moving your mouse around. It should feel smooth, just like it should on 144 Hz. Now move a window (such as a browser, or your file manager) around. You should notice that it still feels like it runs at 60 Hz. To sum up: What should happen: - The windows that are currently on the 144 Hz Monitor should be rendered at the specified refresh rate What actually happens - The refresh rate of rendered windows (excluding games) appears to be capped to the lowest refresh rate monitor I did test this further and it seemed to confirm my hypothesis. When I set my second, 60 Hz monitor, to run at 30 Hz, everything excluding my cursor was now being rendered at 30 Hz on both screens. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-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 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 19:47:07 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed nvidia, 418.56, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2019-07-16 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco refresh-rate 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/1837330 Title: Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations Status in xorg package in Ubuntu: New Bug description: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily
[Touch-packages] [Bug 1100326]
FYI, it's now easier to interface with Geoclue2 if you don't mind a dep on glib/gio: http://zee-nix.blogspot.co.uk/2015/10/geoclue-convenience-library-just-got.html http://www.freedesktop.org/software/geoclue/docs/libgeoclue/GClueSimple.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geoclue-providers in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Unknown Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1828718] [NEW] [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem.
Public bug reported: sound is very low for videos both hevc and h264 . even with amplification. and fine in youtube. overall sound is very much less than when i was in windows 10 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thanveer 1898 F pulseaudio /dev/snd/controlC0: thanveer 1898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 12 14:45:17 2019 InstallationDate: Installed on 2019-05-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EF dmi.board.vendor: HP dmi.board.version: 63.47 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd08/29/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T33PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1828718 Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem. Status in alsa-driver package in Ubuntu: New Bug description: sound is very low for videos both hevc and h264 . even with amplification. and fine in youtube. overall sound is very much less than when i was in windows 10 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: thanveer 1898 F pulseaudio /dev/snd/controlC0: thanveer 1898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 12 14:45:17 2019 InstallationDate: Installed on 2019-05-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EF dmi.board.vendor: HP dmi.board.version: 63.47 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd08/29/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T33PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828718/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
same here -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1539465] Re: invoking "sudo systemctl start network-1manager.service" in systemd rescue shell causes it to be unresponsive
** Also affects: systemd Importance: Undecided Status: New -- 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/1539465 Title: invoking "sudo systemctl start network-1manager.service" in systemd rescue shell causes it to be unresponsive Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: After a corruption of a btrfs mountpoint in `/etc/fstab` (not `/` or `/home/`) the `systemd` rescue shell was started. After invoking `sudo systemctl start network-manager.service` Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-quark, 1) Hung up was printed and the shell became unresponsive to keyboard input (only Ctrl+Alt+F[>1] changed to screens with blinking cursors; not even 7 Ctrl+Alt+Del within two seconds triggered reboot which normally happends in `systemd` rescue shell. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 Uname: Linux 4.3.3-040303-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 28 05:16:47 2016 InstallationDate: Installed on 2015-12-12 (46 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.3-040303-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: systemd UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1539465/+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 520546] Re: Alt-f2 switches to virtual terminal 2
I'm experiencing this on a fresh install of Kubuntu 18.04 as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1766332] [NEW] need help
Public bug reported: my graphics not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Tue Apr 24 00:24:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-38-generic, x86_64: installed nvidia-384, 384.130, 4.13.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3808] InstallationDate: Installed on 2018-04-17 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 174f:14e9 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Q7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=ec0e44e0-f209-4a9f-908f-c907644c99a3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD5CN31WW:bd12/03/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q7 dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Apr 23 23:56:44 2018 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 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/1766332 Title: need help Status in xorg package in Ubuntu: New Bug description: my graphics not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Tue Apr 24 00:24:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-38-generic, x86_64: installed nvidia-384, 384.130, 4.13.0-38-generic, x86_64: installed GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3808] InstallationDate: Installed on 2018-04-17 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
[Touch-packages] [Bug 1385611] Re: Laptop charger keeps disconnecting then re-connecting
Sorry, I just noticed that it also happens in Windows 10. I guess my charger is faulty... ** Changed in: unity8 (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1385611 Title: Laptop charger keeps disconnecting then re-connecting Status in kde-workspace package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Since upgrading my Samsung 540U4E-K01AU to Kubuntu 14.04 the battery charger keeps connecting and disconnecting as i change from application to application or another tab. It doesn't drop out if im not interacting with the laptop. I have tested the charger with a multi meter and the charger is physically working correctly. I didnt have this issue with Kubuntu 12.04, 13.04 or 13.10. If i boot from my tails live cd it seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: plasma-desktop 4:4.11.11-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: KDE Date: Sat Oct 25 19:40:49 2014 ExecutablePath: /usr/bin/plasma-desktop InstallationDate: Installed on 2014-10-15 (10 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: kde-workspace UpgradeStatus: Upgraded to trusty on 2014-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1385611/+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 1385611] Re: Laptop charger keeps disconnecting then re-connecting
My problem is similar. I haven't had this issue before. The charger keeps disconnecting and reconnecting at random intervals when the battery is full (and makes this annoying clicking noise, the sound of plugging a socket into a wall). This doesn't happen when the battery is charging and pc runs perfectly with the battery completely removed. It also doesn't happen in Windows 10. My system is Ubuntu 17.10 (x64) kernel: 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I am pretty much certain that my charger is working correctly. I'm not sure this problem is also related with the kde-workspace (Ubuntu) package. My machine runs on Unity 8. The lshw output of my system(This is while battery removed): jarvis-acer description: Notebook product: NC-V3-571G-736B1 (NC-V3-571G-736B1_0648_V2.21) vendor: Acer version: V2.21 serial: NXM7EEY00230501DA63400 width: 64 bits capabilities: smbios-2.7 dmi-2.7 smp vsyscall32 configuration: chassis=notebook family=Type1Family sku=NC-V3-571G-736B1_0648_V2.21 uuid=21484AFD-4E52-11E2-80EF-B888E3B386C1 *-core description: Motherboard product: VA50_HC_CR vendor: Acer physical id: 0 version: Type2 - Board Version serial: NBM7D1100130447CF63400 slot: Type2 - Board Chassis Location *-firmware description: BIOS vendor: Insyde Corp. physical id: 0 version: V2.21 date: 12/16/2013 size: 128KiB capacity: 3520KiB capabilities: pci upgrade shadowing cdboot bootselect edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi *-cpu description: CPU product: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz vendor: Intel Corp. physical id: 4 bus info: cpu@0 version: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz serial: To Be Filled By O.E.M. slot: U3E1 size: 1197MHz capacity: 4GHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts cpufreq configuration: cores=4 enabledcores=4 threads=8 *-cache:0 description: L1 cache physical id: b slot: L1 Cache size: 32KiB capacity: 32KiB capabilities: internal write-through instruction configuration: level=1 *-cache:1 description: L2 cache physical id: c slot: L2 Cache size: 256KiB capacity: 256KiB capabilities: internal write-through unified configuration: level=2 *-cache:2 description: L3 cache physical id: d slot: L3 Cache size: 6MiB capacity: 6MiB capabilities: internal write-back unified configuration: level=3 *-cache description: L1 cache physical id: a slot: L1 Cache size: 32KiB capacity: 32KiB capabilities: internal write-through data configuration: level=1 *-memory description: System Memory physical id: 1a slot: System board or motherboard size: 16GiB *-bank:0 description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) product: ACR16D3LS1KBG/8G vendor: Kingston physical id: 0 serial: 301B2144 slot: DIMM0 size: 8GiB width: 64 bits clock: 1600MHz (0.6ns) *-bank:1 description: DIMM [empty] product: Empty vendor: Empty physical id: 1 serial: Empty slot: DIMM1 *-bank:2 description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) product: ACR16D3LS1KBG/8G vendor: Kingston physical id: 2 serial: CD2253C8 slot: DIMM1 size: 8GiB width: 64 bits clock: 1600MHz (0.6ns) *-bank:3 description: DIMM [empty] product: Empty vendor: Empty physical id: 3 serial: Empty slot: DIMM3 *-pci
[Touch-packages] [Bug 1732889] [NEW] graphic bootloader
Public bug reported: i don't have graphical bootloader and i cant restart the PC. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 17 14:33:06 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3800] InstallationDate: Installed on 2017-11-13 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5664 IMC Networks Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=b72bf002-0c4a-44dc-a065-ecaa2bbb864c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K45914 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN39WW:bd10/11/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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: Thu Nov 16 07:06:50 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1732889 Title: graphic bootloader Status in xorg package in Ubuntu: New Bug description: i don't have graphical bootloader and i cant restart the PC. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Nov 17 14:33:06 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3800] InstallationDate: Installed on 2017-11-13 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5664 IMC Networks Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=b72bf002-0c4a-44dc-a065-ecaa2bbb864c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0K45914 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10
[Touch-packages] [Bug 1712308] [NEW] systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname()
*** This bug is a security vulnerability *** Public security bug reported: I don't know this bug ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 Date: Mon Aug 21 21:30:00 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2017-08-19 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. X555UB ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: sd_device_new_from_subsystem_sysname () from /lib/systemd/libsystemd-shared-234.so sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () from /lib/systemd/libsystemd-shared-234.so Title: systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname() UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago) UserGroups: audio pulse pulse-access video dmi.bios.date: 10/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace ** Information type changed from Private to Public Security -- 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/1712308 Title: systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname() Status in systemd package in Ubuntu: New Bug description: I don't know this bug ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 Date: Mon Aug 21 21:30:00 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2017-08-19 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. X555UB ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: sd_device_new_from_subsystem_sysname () from /lib/systemd/libsystemd-shared-234.so sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () from /lib/systemd/libsystemd-shared-234.so Title: systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname() UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago) UserGroups: audio pulse pulse-access video dmi.bios.date: 10/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555UB 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/systemd/+bug/1712308/+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 1692496] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: after cancel download ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 22 12:51:01 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-18 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692496 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: after cancel download ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 22 12:51:01 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-18 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692496/+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 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => ali salama (alisalama) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) Status in accountsservice package in Ubuntu: Confirmed Status in base-passwd package in Ubuntu: Invalid Status in ceph package in Ubuntu: Confirmed Status in ifmail package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in netqmail package in Ubuntu: Confirmed Bug description: "Technical" user libvirt Qemu appears in the list of user in Ligthdm, among the real regular users. It probably shouldn't ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libvirt-bin 2.5.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Feb 22 22:09:24 2017 InstallationDate: Installed on 2017-02-01 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) KernLog: SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+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 1637982] Re: segfault shortly after connection to an USB modem is established
In Ubuntu 16.10, this bug still exists. -- 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/1637982 Title: segfault shortly after connection to an USB modem is established Status in network-manager package in Ubuntu: New Bug description: I'm using my phone as an USB modem. It used to be working fine in 15.10, but now in 16.04 it disconnects within approximately 2 minutes when it connects. Here's dmesg log **before** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready And dmesg log **after** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: LGD8552e4244b8 [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready [ 2527.615086] NetworkManager[1042]: segfault at 4e8 ip 0046c810 sp 7ffdd47e0120 error 4 in NetworkManager[40+2b9000] [ 2529.423507] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2529.425511] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2529.728754] NetworkManager[4830]: segfault at 4e8 ip 0046c810 sp 7ffc5a4cfda0 error 4 in NetworkManager[40+2b9000] [ 2530.383596] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2530.394093] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2530.634992] NetworkManager[4866]: segfault at 4e8 ip 0046c810 sp 7fff61f7f060 error 4 in NetworkManager[40+2b9000] [ 2531.137181] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2531.139427] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready More info: Ubuntu 16.04.1 LTS network-manager 1.2.2-0ubuntu0.16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1637982/+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 1641293] [NEW] system freeze
Public bug reported: I'm experiencing sudden system freeze. don't know why and also i also had freezing in windows 10. I hope you can help me to find out where it came from. monitor freeze and i cant do anything. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 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: Sat Nov 12 16:15:50 2016 DistUpgraded: 2016-11-11 22:37:46,435 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d] InstallationDate: Installed on 2016-11-11 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic root=UUID=900b7ae5-ca9a-4e6d-96b4-31230865e373 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to vivid on 2016-11-11 (0 days ago) dmi.bios.date: 06/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.213:bd06/26/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Nov 12 15:49:18 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.17.1-0ubuntu3.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu vivid -- 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/1641293 Title: system freeze Status in xorg package in Ubuntu: New Bug description: I'm experiencing sudden system freeze. don't know why and also i also had freezing in windows 10. I hope you can help me to find out where it came from. monitor freeze and i cant do anything. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.8 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: Sat Nov 12 16:15:50 2016 DistUpgraded: 2016-11-11 22:37:46,435 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
[Touch-packages] [Bug 1637982] Re: segfault shortly after connection to an USB modem is established
** Tags added: usb-modem xenial -- 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/1637982 Title: segfault shortly after connection to an USB modem is established Status in network-manager package in Ubuntu: New Bug description: I'm using my phone as an USB modem. It used to be working fine in 15.10, but now in 16.04 it disconnects within approximately 2 minutes when it connects. Here's dmesg log **before** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready And dmesg log **after** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: LGD8552e4244b8 [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready [ 2527.615086] NetworkManager[1042]: segfault at 4e8 ip 0046c810 sp 7ffdd47e0120 error 4 in NetworkManager[40+2b9000] [ 2529.423507] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2529.425511] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2529.728754] NetworkManager[4830]: segfault at 4e8 ip 0046c810 sp 7ffc5a4cfda0 error 4 in NetworkManager[40+2b9000] [ 2530.383596] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2530.394093] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2530.634992] NetworkManager[4866]: segfault at 4e8 ip 0046c810 sp 7fff61f7f060 error 4 in NetworkManager[40+2b9000] [ 2531.137181] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2531.139427] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready More info: Ubuntu 16.04.1 LTS network-manager 1.2.2-0ubuntu0.16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1637982/+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 1637982] [NEW] segfault shortly after connection to an USB modem is established
Public bug reported: I'm using my phone as an USB modem. It used to be working fine in 15.10, but now in 16.04 it disconnects within approximately 2 minutes when it connects. Here's dmesg log **before** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready And dmesg log **after** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: LGD8552e4244b8 [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready [ 2527.615086] NetworkManager[1042]: segfault at 4e8 ip 0046c810 sp 7ffdd47e0120 error 4 in NetworkManager[40+2b9000] [ 2529.423507] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2529.425511] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2529.728754] NetworkManager[4830]: segfault at 4e8 ip 0046c810 sp 7ffc5a4cfda0 error 4 in NetworkManager[40+2b9000] [ 2530.383596] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2530.394093] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2530.634992] NetworkManager[4866]: segfault at 4e8 ip 0046c810 sp 7fff61f7f060 error 4 in NetworkManager[40+2b9000] [ 2531.137181] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 2531.139427] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready More info: Ubuntu 16.04.1 LTS network-manager 1.2.2-0ubuntu0.16.04.3 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1637982 Title: segfault shortly after connection to an USB modem is established Status in network-manager package in Ubuntu: New Bug description: I'm using my phone as an USB modem. It used to be working fine in 15.10, but now in 16.04 it disconnects within approximately 2 minutes when it connects. Here's dmesg log **before** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [ 2493.139903] usb 1-1.1: New USB device found, idVendor=1004, idProduct=6344 [ 2493.139907] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2493.139922] usb 1-1.1: Product: LGE Android Phone [ 2493.139923] usb 1-1.1: Manufacturer: LG Electronics Inc. [ 2493.139925] usb 1-1.1: SerialNumber: [ 2493.230445] cdc_acm 1-1.1:1.2: ttyACM0: USB ACM device [ 2493.230721] usbcore: registered new interface driver cdc_acm [ 2493.230723] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2493.268457] usbcore: registered new interface driver cdc_ether [ 2493.290079] rndis_host 1-1.1:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.1, RNDIS device, 02:4d:41:43:34:07 [ 2493.290108] usbcore: registered new interface driver rndis_host [ 2493.321367] rndis_host 1-1.1:1.0 enp0s26u1u1: renamed from usb0 [ 2493.343344] IPv6: ADDRCONF(NETDEV_UP): enp0s26u1u1: link is not ready And dmesg log **after** network manager fails: [ 2493.046646] usb 1-1.1: new high-speed USB device number 6 using ehci-pci [
[Touch-packages] [Bug 1610684] [NEW] ubuntu 16.04 won't shutdown : Reached target Shutdown[ok] also ubuntu 14.04 won't shut down : killing all procces [fail]
Public bug reported:
I had ubuntu 14.04 (DELL laptop INSPIRON N-4110 ) shutdown and reboot
worked correctly and without any problem but after a long time I wasn't
able to reboot or shutdown my machine.
and that was the log message was shown by pressing Esc during shutdown:
killing all procceses [fail]
and I tried all the tips I saw in askubuntu and others(like changing the
grub and shutdown - h now etc none of them have worked ! )
then I clean installed ubuntu 16.04 (current) but issue is not going to
solve.
now the log shows:
[ok] Reached target Shutdown
[135.486156] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0X0 action 0x6 frozen
[135.846776] ata2.00: cmd a0/00: 00:00:00:00/00:00:00:00:00/s0 tag 4 pio 16392
in
[135.846776] get event status notification 4a 01 00 10 00 00 00 00 00res
40/00:00:00:00
[135.848020] ata2.00:status: { DRDY }
[141.182090] ata2.00 revalidation failed (errno=-5)
I checked bug #1464917 and did instructions also but nothings changed .
UPDATE:
after updating to 16.04.1 (boot install) Ubuntu will shutdown if i do it
fast when OS is coming up but after a while it's not going to power off
again and Esc key won't work and does not show me log any more
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: shutdown systemd
--
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/1610684
Title:
ubuntu 16.04 won't shutdown : Reached target Shutdown[ok] also ubuntu
14.04 won't shut down : killing all procces [fail]
Status in systemd package in Ubuntu:
New
Bug description:
I had ubuntu 14.04 (DELL laptop INSPIRON N-4110 ) shutdown and reboot
worked correctly and without any problem but after a long time I
wasn't able to reboot or shutdown my machine.
and that was the log message was shown by pressing Esc during
shutdown:
killing all procceses [fail]
and I tried all the tips I saw in askubuntu and others(like changing
the grub and shutdown - h now etc none of them have worked ! )
then I clean installed ubuntu 16.04 (current) but issue is not going
to solve.
now the log shows:
[ok] Reached target Shutdown
[135.486156] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0X0 action 0x6 frozen
[135.846776] ata2.00: cmd a0/00: 00:00:00:00/00:00:00:00:00/s0 tag 4 pio
16392 in
[135.846776] get event status notification 4a 01 00 10 00 00 00 00 00res
40/00:00:00:00
[135.848020] ata2.00:status: { DRDY }
[141.182090] ata2.00 revalidation failed (errno=-5)
I checked bug #1464917 and did instructions also but nothings changed
.
UPDATE:
after updating to 16.04.1 (boot install) Ubuntu will shutdown if i do
it fast when OS is coming up but after a while it's not going to power
off again and Esc key won't work and does not show me log any more
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1610684/+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 1579265] Re: Qt dev package does not include webenginewidgets
Thanks for the updates and the links to the discussions. My understanding is that Debian doesn't wish to distribute Qt WebEngine because it is would be linked in statically and thus not receive any security updates. And changing it to use the library dynamically would be too much work. Is that a fair assessment? I did look into the Oxide packages. I tried to install several of them, including even the codecs. However, this still doesn't allow me to build my test project (see attachment). So, appears that Oxide is not a drop- in replacement for web engine. Also, I found hardly any documentation on Oxide other than a blog post. I also found https://launchpad.net/oxide but that is very scare on details or documentation. If you have any other pointers, please let us know. Otherwise, our best course of action is to package QT ourselves. Thanks again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1579265 Title: Qt dev package does not include webenginewidgets Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Attached is a sample project that uses several QT components. To build this, one needs to install the following packages: apt-get install libqt5core5a qtconnectivity5-dev qtmultimedia5-dev qt5-default libqt5webkit5-dev qt3d5-dev g++ Then, run qmake. The expected result should be output of a Makefile, Makefile.debug and Makefile.release. However, I get the following error: unknown modules: webenginewidgets I do not see any package that provides the web engine widgets component and must conclude that the QT package is missing this. Therefore am opening this bug and requesting that QT be packaged to include webengine. Or a separate package be provided with this. This is for 16.04 release which packages Qt 5.5.1. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1579265/+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 1579265] [NEW] Qt dev package does not include webenginewidgets
Public bug reported: Attached is a sample project that uses several QT components. To build this, one needs to install the following packages: apt-get install libqt5core5a qtconnectivity5-dev qtmultimedia5-dev qt5-default libqt5webkit5-dev qt3d5-dev g++ Then, run qmake. The expected result should be output of a Makefile, Makefile.debug and Makefile.release. However, I get the following error: unknown modules: webenginewidgets I do not see any package that provides the web engine widgets component and must conclude that the QT package is missing this. Therefore am opening this bug and requesting that QT be packaged to include webengine. Or a separate package be provided with this. This is for 16.04 release which packages Qt 5.5.1. Thanks. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Files to repro bug. Run qmake in directory after installing QT dev packages." https://bugs.launchpad.net/bugs/1579265/+attachment/4657612/+files/test_project.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1579265 Title: Qt dev package does not include webenginewidgets Status in qtbase-opensource-src package in Ubuntu: New Bug description: Attached is a sample project that uses several QT components. To build this, one needs to install the following packages: apt-get install libqt5core5a qtconnectivity5-dev qtmultimedia5-dev qt5-default libqt5webkit5-dev qt3d5-dev g++ Then, run qmake. The expected result should be output of a Makefile, Makefile.debug and Makefile.release. However, I get the following error: unknown modules: webenginewidgets I do not see any package that provides the web engine widgets component and must conclude that the QT package is missing this. Therefore am opening this bug and requesting that QT be packaged to include webengine. Or a separate package be provided with this. This is for 16.04 release which packages Qt 5.5.1. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1579265/+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 1569503] [NEW] Xorg crash
Public bug reported: whenever doing two or more task at a time the system restart from login page ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 12 23:39:32 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 3.13.0-76-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-85-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0651] InstallationDate: Installed on 2015-01-19 (449 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=b21e5ae6-b281-43f4-843f-e37c074abc16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 09V1VC dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 12 23:35:24 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5567 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1569503 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: whenever doing two or more task at a time the system restart from login page ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 12 23:39:32 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 3.13.0-76-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-85-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0651] InstallationDate: Installed on 2015-01-19 (449 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=b21e5ae6-b281-43f4-843f-e37c074abc16 ro quiet splash vt.handoff=7 SourcePackage:
[Touch-packages] [Bug 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be
Hi Dann,
Yes, that is expected. The Xgene doesn't have support for hardware
crypto instructions. I believe it's the only AArch64 platform without
them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1552939
Title:
arm64 build doesn't use asm and is 4x-16x slower than it could be
Status in OpenSSL:
New
Status in openssl package in Ubuntu:
Incomplete
Status in openssl package in Debian:
Unknown
Bug description:
The openssl build for arm64 doesn't compile in the assembly that is
present in openssl as of version 1.0.2 for aarch64 because the debian-
targets.patch that is applied specifies a target that doesn't have
assembly. The line at issue is debian-arm64 target which needs
${no_asm} changed to ${aarch64_asm}:linux64. Running openssl speed
-evp aes-128-gcm shows a 4x-16x improvement in performance with this
change made and the package rebuilt. Other aes and sha variants show
similar performance gains by enabling asm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1552939/+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 1552939] [NEW] arm64 build doesn't use asm and is 4x-16x slower than it could be
Public bug reported:
The openssl build for arm64 doesn't compile in the assembly that is
present in openssl as of version 1.0.2 for aarch64 because the debian-
targets.patch that is applied specifies a target that doesn't have
assembly. The line at issue is debian-arm64 target which needs ${no_asm}
changed to ${aarch64_asm}:linux64. Running openssl speed -evp
aes-128-gcm shows a 4x-16x improvement in performance with this change
made and the package rebuilt. Other aes and sha variants show similar
performance gains by enabling asm.
** Affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1552939
Title:
arm64 build doesn't use asm and is 4x-16x slower than it could be
Status in openssl package in Ubuntu:
New
Bug description:
The openssl build for arm64 doesn't compile in the assembly that is
present in openssl as of version 1.0.2 for aarch64 because the debian-
targets.patch that is applied specifies a target that doesn't have
assembly. The line at issue is debian-arm64 target which needs
${no_asm} changed to ${aarch64_asm}:linux64. Running openssl speed
-evp aes-128-gcm shows a 4x-16x improvement in performance with this
change made and the package rebuilt. Other aes and sha variants show
similar performance gains by enabling asm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1552939/+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
I just ran into this as well. Interestingly the only package I can find that has the issue is systemd. It looks like systemd was linked with gold and nothing else I have installed is. This issues was fixed in upstream bin-utils by the following change: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=3b0357dadaf2366cc418ec725dec55b1cea1a2e7 -- 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: Confirmed 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 1392176] Re: mounts cgroups unconditionally which causes undesired effects with cpu hotplug
Serge, Does the issue being moot apply to wiley or 16.04? Thanks, Ali -- 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/1392176 Title: mounts cgroups unconditionally which causes undesired effects with cpu hotplug Status in cgmanager package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: == Comment: #0 - Preeti U. Murthy <preeti.mur...@in.ibm.com> - 2014-10-20 04:40:12 == ---Problem Description--- Systemd mounts cgroups explicitly every boot. Since the user had no say in it, undesired consequences are observed in reaction to cpu hotplug operations. Here is how. Systemd moves the tasks to the cgroup mounted by it. This cgroup automatically becomes the child of the root cgroup which is present by default. The children cgroups are not expected to remember their configured cpusets after hotplug operations in the kernel. Hence when cpus are taken offline and brought back online they are no longer used for load balancing of tasks and hence remain unused. This is an undesired consequence because the user had not even asked for cgroups to be mounted, yet is not able to use the full capacity of the system. Only when the user himself creates cgroup hierarchies, should he be exposed to the side effects of cpu hotplug on cpusets. Else all online cpus must be made available to him which is not happening since systemd mounts cgroups on every boot. Hence please revert this feature or provide an explaination as to why this is being done. ---uname output--- Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Tuleta 8286-42A ---Debugger--- A debugger was configured, however the system did not enter into the debugger ---Steps to Reproduce--- $ taskset -p $$ $ 0-127 $ echo 0 > /sys/devices/system/cpu/cpu7/online $ taskset -p $$ $ 0-6,8-127 $ echo 1 > /sys/devices/system/cpu/cpu7/online $ taskset -p $$ $ 0-6,8-127 Userspace tool common name: systemd The userspace tool has the following bit modes: 64-bit Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb Userspace tool obtained from project website: 208-8ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1392176/+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 1486107] [NEW] package openssh-server 1:6.6p1-2ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: sddf ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openssh-server 1:6.6p1-2ubuntu2.3 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Aug 18 11:41:29 2015 DuplicateSignature: package:openssh-server:1:6.6p1-2ubuntu2.3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-06 (164 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: openssh Title: package openssh-server 1:6.6p1-2ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.ssh.conf: [deleted] modified.conffile..etc.pam.d.sshd: [modified] mtime.conffile..etc.pam.d.sshd: 2015-03-06T11:37:59.759379 ** Affects: openssh (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package trusty -- 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/1486107 Title: package openssh-server 1:6.6p1-2ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Confirmed Bug description: sddf ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openssh-server 1:6.6p1-2ubuntu2.3 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Aug 18 11:41:29 2015 DuplicateSignature: package:openssh-server:1:6.6p1-2ubuntu2.3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-06 (164 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: openssh Title: package openssh-server 1:6.6p1-2ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.ssh.conf: [deleted] modified.conffile..etc.pam.d.sshd: [modified] mtime.conffile..etc.pam.d.sshd: 2015-03-06T11:37:59.759379 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1486107/+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 1463264] Re: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed
I have also faced the same issue of application closing after Unlock using Ubuntu 14.04.01 on HP ProBook 450 G2 Rahat Ali Khan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1463264 Title: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed Status in lightdm package in Ubuntu: Confirmed Bug description: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1463264/+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 1463264] [NEW] When I lock ubuntu 14.04.2, all applications opened (complete session) crashed
Public bug reported: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1463264 Title: When I lock ubuntu 14.04.2, all applications opened (complete session) crashed Status in lightdm package in Ubuntu: New Bug description: Freshly installed ubuntu 14.04.2 with full updates. When I lock my desktop session, desktop halts for a couple of seconds, then session is locked, but I am taken back to Login screen. When I login, than Lock is presented, and when I unlock by providing password, all my previous session is gone, all applications crashed/closed. Its like when I just logged in for the first time, but with a twist that even the applications that were setup to be opened on startup like Skype are not auto started after this issue happen. [skype does autostart on normal login, as its added in startup applications list] I expect normal lock and unlock experience, not logout experience when locking. Using fglrx or X.Org open source display driver gives same issue. I am using HP ProBook 450 G2. Same issue was happening on 14.04.1. Same issue is happening on all of our same modal laptops, so for sure its a bug somewhere. Let me know if anyone needs more information or logs etc. I will try my best to provide these details. LIghtDM version is: 1.10.5-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 9 10:29:39 2015 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1463264/+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 1453545] [NEW] Error in software updater GUI
Public bug reported: In ubuntu14.04 software updater GUI the download process shows Kb of MB While 50% of the 15MB is downloaded. See the attached file please. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screenshot from 2015-05-10 15:28:48.png https://bugs.launchpad.net/bugs/1453545/+attachment/4394887/+files/Screenshot%20from%202015-05-10%2015%3A28%3A48.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1453545 Title: Error in software updater GUI Status in tzdata package in Ubuntu: New Bug description: In ubuntu14.04 software updater GUI the download process shows Kb of MB While 50% of the 15MB is downloaded. See the attached file please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1453545/+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 1100326]
(In reply to marius from comment #5) Seems like this is fixed in GeoClue2 codebase. I see that it is using libmm library, and see the use of MM_MODEM_LOCATION_SOURCE_3GPP_LAC_CI in src/gclue-modem-source.c as pointed to in comment #1. That is correct. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geoclue-providers in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in The Mozilla Firefox Browser: Confirmed Status in GeoClue: The Geoinformation Service: Won't Fix Status in The WebKit Open Source Project: Fix Released Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+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 1412614] [NEW] [HP Compaq 8510p, Analog Devices AD1981, Other SPDIF Out, Left] Playback problem
Public bug reported: left headphone is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 19 20:23:13 2015 InstallationDate: Installed on 2014-10-18 (93 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Other SPDIF Out, Left Symptom_Type: Only some of outputs are working Title: [HP Compaq 8510p, Analog Devices AD1981, Other SPDIF Out, Left] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.14 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.asset.tag: CNU84566N7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.14:bd08/19/2008:svnHewlett-Packard:pnHPCompaq8510p:pvrF.14:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510p dmi.product.version: F.14 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1412614 Title: [HP Compaq 8510p, Analog Devices AD1981, Other SPDIF Out, Left] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: left headphone is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 19 20:23:13 2015 InstallationDate: Installed on 2014-10-18 (93 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Other SPDIF Out, Left Symptom_Type: Only some of outputs are working Title: [HP Compaq 8510p, Analog Devices AD1981, Other SPDIF Out, Left] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.14 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.asset.tag: CNU84566N7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.14:bd08/19/2008:svnHewlett-Packard:pnHPCompaq8510p:pvrF.14:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510p dmi.product.version: F.14 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1412614/+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 1311316] Re: After locking screen there is no input field to type password for unlock
Today faced the problem and had to lose the whole development setup because of it... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1386714] Re: Window Spread's type-to-search conflicts in maximization of open windows
*** This bug is a duplicate of bug 1316265 *** https://bugs.launchpad.net/bugs/1316265 ** Summary changed: - Window Spread search conflicts in maximization of open windows + Window Spread's type-to-search conflicts in maximization of open windows -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386714 Title: Window Spread's type-to-search conflicts in maximization of open windows Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386714/+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 1386714] Re: Window Spread's type-to-search conflicts in maximization of open windows
*** This bug is a duplicate of bug 1316265 *** https://bugs.launchpad.net/bugs/1316265 This is NOT a duplicate of bug #1316265. This is different and ONLY occurs when you search for a window by TYPING. A workaround for this will be opening and closing the Window Spread (for exmple by pressing Super+W twice). ** Description changed: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); - 3. search for a window and select it; + 3. search for a window by typing and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity 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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1386714 Title: Window Spread's type-to-search conflicts in maximization of open windows Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window by typing and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386714/+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 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering
Comments #7 and #9 are describing a different bug related to using keyboard on window spread: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386714 This bug occurs for me when I disabled and re-enabled window spread in Unity Tweak Tool. I could solve the problem in a strange way: 1. selected Restore Settings of window spread on Unity Tweak Tool; 2. disabled and re-enabled the window spread on Unity Tweak Tool; Suddenly Ubuntu Unity Plugin got disabled and I lost window decorations and indicators. 3. I opened a Terminal, enter `ccsm` to open CompizConfig Settings Manager; 4. noticed Gnome Compatibility and Window Decorations are enabled, both of which conflict with Unity Plugin; 5. enabled Unity Plugin and resolve conflicts with those two. Now I can use window spread without problem except the type-to-search which I've described in lp: 1386714. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + W (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+W is performed. Try this out using Terminal. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1316265/+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 1386714] [NEW] Window Spread search conflicts in maximization of open windows
Public bug reported: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty utopic ** Attachment added: Window Spread serach conflicts in Maximization.mp4 https://bugs.launchpad.net/bugs/1386714/+attachment/4247115/+files/Window%20Spread%20serach%20conflicts%20in%20Maximization.mp4 ** Description changed: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. - Description: Ubuntu 14.04.1 LTS - Release: 14.04 - unity 7.2.2+14.04.20140714-0ubuntu1.1 - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity 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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1386714 Title: Window Spread search conflicts in maximization of open windows Status in “unity” package in Ubuntu: New Bug description: To reproduce the bug: 1. open multiple windows; 2. open Window Spread/Scale (Super+W); 3. search for a window and select it; 4. now switch to another window without using Window Spread again; 5. try to maximize/unmaximize window. You will see the maximized window is expanded horizontally and vertically, but there are two title bars i.e. the window keeps its title bar separate from the top indicator bar even after maximization. This bug doesn't affect windows opened after window spread search. Opening Window Spread again without searching will fix the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 Uname: Linux 3.16.0-031600-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 17:28:34 2014 InstallationDate: Installed on 2014-10-02 (25 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386714/+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 1104632] Re: Application spread view (Compiz scale) doesn't work properly after using Show Desktop
In fact, the non-minimized windows which get hidden by Show Desktop will be hidden from Window Spread too. ** Tags added: trusty utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1104632 Title: Application spread view (Compiz scale) doesn't work properly after using Show Desktop Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: What steps will reproduce the problem? 1. Open two or more windows of an application like Nautilus so that all are visible on the screen 2. Use the Show Desktop button to hide the windows 3. Activate the window spread by clicking at the icon of the application you launched two times What is the expected output? - all windows of the application (from current workspace) are shown in the spread, represented by a thumbnail What do you see instead? - all windows are technically shown but only the window activated by the first click at the icon has a working thumbnail - the area where the other window-thumbnails should be located is functional but the thumbnails are missing ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc-Version 4.7.2 (Ubuntu/Linaro 4.7.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 02:19:52 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-310, 310.19, 3.8.0-1-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8390] InstallationDate: Installed on 2013-01-22 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130122) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=db108b5c-1f1d-4fe4-99bd-234f619ae6cf ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: P67 Extreme4 Gen3 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.:bvrP2.20:bd05/11/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP67Extreme4Gen3: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. version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Thu Jan 24 15:13:16 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log
[Touch-packages] [Bug 1104632] Re: Application spread view (Compiz scale) doesn't work properly after using Show Desktop
I added trusty and utopic tags, because the bug still exists on unity 7, both 32- and 64-bit versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1104632 Title: Application spread view (Compiz scale) doesn't work properly after using Show Desktop Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: What steps will reproduce the problem? 1. Open two or more windows of an application like Nautilus so that all are visible on the screen 2. Use the Show Desktop button to hide the windows 3. Activate the window spread by clicking at the icon of the application you launched two times What is the expected output? - all windows of the application (from current workspace) are shown in the spread, represented by a thumbnail What do you see instead? - all windows are technically shown but only the window activated by the first click at the icon has a working thumbnail - the area where the other window-thumbnails should be located is functional but the thumbnails are missing ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc-Version 4.7.2 (Ubuntu/Linaro 4.7.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 02:19:52 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-310, 310.19, 3.8.0-1-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8390] InstallationDate: Installed on 2013-01-22 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130122) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=db108b5c-1f1d-4fe4-99bd-234f619ae6cf ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: P67 Extreme4 Gen3 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.:bvrP2.20:bd05/11/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP67Extreme4Gen3: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. version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Thu Jan 24 15:13:16 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Touch-packages] [Bug 1313446] Re: window disappears on toggle shade
** Tags added: trusty utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A ghost outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would roll up and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+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 1301771] Re: Text of highlighted item in combobox has no color distinction from that of non highlighted items
You can fix it manually. Open the file gtk-widgets.css under, for
example, for Radiance: /usr/share/themes/Radiance/gtk-3.0/
Then, find the line (#1040): /* Workaround for lp:949368 */
and comment two following blocks with /* at the beginning and */ at the
end, like this:
/*GtkComboBox .menuitem * {
color: @fg_color;
}
GtkComboBox .menuitem *:hover {
color: @selected_fg_color;
}*/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1301771
Title:
Text of highlighted item in combobox has no color distinction from
that of non highlighted items
Status in Themes for Ubuntu:
New
Status in “ubuntu-themes” package in Ubuntu:
Triaged
Bug description:
Looks like the text color of highlighted item in combobox/dropdown
list shows no distinction from that of non highlighted ones. It's
drawn in black, instead of white like usual when item is highlighted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: light-themes 14.04+14.04.20140327-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic i686
ApportVersion: 2.14-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Thu Apr 3 13:59:00 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-04-01 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140331)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1301771/+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
