[Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Same thing is happening here with an Asus Z790. It was working properly on 23.04. Not on 23.10 the sound works like this: HiFi 2.0 - Very low sound. I have to crank the sound to max to barely hear it. HiFi 5.1 - Only the front ones sound (but they sound around 60% when the volume is at 100%, meaning, the actual volume of them is not full). The rear speakers dont even sound. You have to put your ear to the actual speaker to hear it. HiFi 7.1 - The front ones work correctly but any others do not. The headphones still work correctly via bluetooth, but the whole sound experience basically is dead. Everything is either very low or speaker mode or nothing at all. -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: 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: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2018290] [NEW] Clicking on the top right corner fails
Public bug reported: Problem is that when any app gets maximized, or uses the half screen technique (eg: Drag a window to the left or right side of the screen so it half-screen maximizes itself) the top portion of the window can not be clicked (left or right clicked). So any button on that area do not work. Like something is overlapping the buttons. The solution is to drag the window back to a smaller size to use those buttons again. It also has a similar issue where, when clicking on the gnome extensions at the top or even the options of ubuntu at the top, you need to slightly click below them a bit for them to actually register the click. The problem has been mentioned here which is the same one: https://askubuntu.com/questions/1464858/right-corner-at-chrome-not-response-to-mouse-click ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 530.41.03 Thu Mar 16 19:48:20 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 2 03:55:34 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/530.41.03, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation AD102 [GeForce RTX 4090] [10de:2684] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. AD102 [GeForce RTX 4090] [19da:4675] InstallationDate: Installed on 2023-04-20 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=276e1671-8c73-42fc-bf30-ea9c79e82647 ro mitigations=off pci=nommconf nvidia-drm.modeset=1 intel_idle.max_cstate=1 ibt=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2023 dmi.bios.release: 9.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z790 HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd03/29/2023:br9.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ790HERO:rvrRev1.xx: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar 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/2018290 Title: Clicking on the top right corner fails Status in xorg package in Ubuntu: New Bug description: Problem is that when any app gets maximized, or uses the half screen technique (eg: Drag a window to the left or right side of the screen so it half-screen maximizes itself) the top portion of the window can not be clicked (left or right clicked). So any button on that area do not work. Like something is overlapping the buttons. The solution is to drag the window back to a smaller size to use those buttons again. It also has a similar issue where, when clicking on the gnome extensions at the top or even the options of ubuntu at the top, you need to slightly click below
[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default
Hi team, wasn't this already done since on the new 23.04 and maybe before, there is a specific question that asks if you would like to report or not to ubuntu? I think that is related to this directly no? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in Apport: Confirmed Status in One Hundred Papercuts: Confirmed Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1623530/+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 2011837] Re: Nvidia with Wayland or Xorg issue
Sorry, did not know it was filed against launchpad. Did not even know the option to set it was set to launchpad. This issue is also related to this one https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2012983 just in case. Same hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2011837 Title: Nvidia with Wayland or Xorg issue Status in wayland package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I will summarize here what I put at https://discourse.ubuntu.com/t/ubuntu-23-04-testing-week/34246/6 On Ubuntu 23.04, if I install it, it works fine but there is a considerable lag for everything. This is when using Wayland. If I do not change the custom.conf gdm to not use wayland, I can get in but I can not interact with any windows. Context menus and sub menus open but do not do anything. The only way for me to get to the terminal was to open nautilus/files from the Dock, then right click any empty space and select terminal. The moment I did that I had a couple of seconds before it crashed the terminal. But was able to get a picture of the hardware after my 3rd attempt. If I do put in on xorg, then an image I posted on the 1st link happens and it stays there, does not matter if I change tty, it always shows and needed to reinstall 23.04 to be able to go back to wayland. But if I use wayland I can actually feel the lag and the interaction with windows and all. This started happening all today after applying all the latest updates for 23.04 (I did not update since I think since several days back). The hardware that I was using for testing is: CPU - 13900k MOBO - Asus Z790 Hero RAM: DDR5 128GB VID: Nvidia 4090 (Drivers were automatically installed during setup) SSD - SN850x It is a computer just for Ubuntu 23.04 testing right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2011837/+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 1623530] Re: Apport should be disabled by default
Hi Brian, yes it works but in the installer it should have that option, so that when installing ubuntu for the first time for example, the user can stop reports from the beginning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in Apport: Confirmed Status in One Hundred Papercuts: Confirmed Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1623530/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Confirmed, after adding the nvidia-drm.modeset=1 to the GRUB file it worked. I tested 3 cases: 1. Reboot without Log out afterwards. 2. Reboot with a Log out afterwards and then try to log in again. 3. Reboot with a Log out afterwards, try to log in again and then reboot. It worked for all cases. Of course this is still a workaround, but it works for the time being. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) 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.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This is exactly what is happening to me. I installed Ubuntu 20.04 today (The official released version, not beta), and if I set the auto login on, it will give me the same issue the original poster said. You can't login afterwards and if your logout, it enter a loop where you will never come out from unless you purge gdm3 and install it back or other workarounds that I can't guarantee work alone. I have an Nvidia GTX 1080 running on the Proprietary 440 Driver. My user is "luis" and the password is "x" in case anyone would want to literally try it out with the same user/pass/hardware combination. If I disable the auto login then everything related to logout/login works correctly. The hardware is down below of an Asus Hero Alpha VII, Intel 6700k and 64 GB of RAM. The SSD is a Samsung 850 Pro 1TB. 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1c.7 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) 03:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:02.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 07:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] 09:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0b:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) I will try the removing of splash and then adding nvidia-drm.modeset=1 to see how it goes. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working
[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default
Guys, this has created more issues to newcomers than anything else I teach them. It should not be alerting the user EVERY TIME an app crashes (which simply comes back up after a second). It apport needs to be enabled to send or gather information it should ask ONCE during the installation process if the user wants to sent the information without being prompted every time an app crashes (and an option if they do want to be prompted). This basically promotes a new comer to leave ubuntu because they think the whole thing is broken. From a usability stand point, it is still the worse idea ever when trying to promote the system, The suggestions mentioned 12+ months ago have not being applied nor a feedback (which would be welcomed) received. It is very frustrating to explain to every new ubuntu user I teach or bring to use ubuntu (which already tops 5000+ users) that they need to disable apport to avoid the bug report popups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in Apport: Confirmed Status in One Hundred Papercuts: Confirmed Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1623530/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Hi Daniel, thank you. How can I mark this ticket as fixed. It has been about 10 days. No problems whatsoever. I actually lost connection yesterday but then noticed it was because I did not charge the headset for the last 2 days. Even with very low power, I was still able to finish a conversation. Thank you for the help and if you would like as a gift, I could buy one of this in Amazon and send it to you buddy. They are pretty awesome. Big hugs friend and think positive. -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1725865] Re: Network shows Cable Unplugged
** Changed in: network-manager (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/1725865 Title: Network shows Cable Unplugged Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Invalid Bug description: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1725865/+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 1725410] Re: Intel Integrated Card not working Asus Hero Alpha VIII
It was a hardware issue with the motherboard. ** Changed in: network-manager (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/1725410 Title: Intel Integrated Card not working Asus Hero Alpha VIII Status in network-manager package in Ubuntu: Invalid Bug description: After upgrading to the latest Kernel, the issue appeared. Basically it always says there is no cable detected and the LAN (Wired) connection never works. Only wireless. If I go back to a previous Ubuntu version it works, but after either 4.12 or 4.13 the issue appeared. I also checked the BIOS version and it works only if I stay with a previous Ubuntu version. The device that is having an issue is: description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 31 serial: 34:97:f6:36:cb:d6 capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.7-4 latency=0 link=no multicast=yes port=twisted pair resources: irq:132 memory:df70-df71 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 11:59:57 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.13 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Linux 74b235bc-acdd-4fc3-a028-d960c890fbe0 802-11-wireless 1508522270 Fri 20 Oct 2017 11:57:50 AM CST yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp9s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Intel ce6b4984-a66e-306e-9a98-9487e5b3c553 802-3-ethernet 1508435911 Thu 19 Oct 2017 11:58:31 AM CST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux 74b235bc-acdd-4fc3-a028-d960c890fbe0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725410/+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 1725865] Re: Network shows Cable Unplugged
Hi Sebastien, I have added the corresponding bug here https://bugzilla.gnome.org/show_bug.cgi?id=792506 Is this what it was needed buddy? ** Bug watch added: GNOME Bug Tracker #792506 https://bugzilla.gnome.org/show_bug.cgi?id=792506 -- 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/1725865 Title: Network shows Cable Unplugged Status in network-manager package in Ubuntu: New Bug description: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725865/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Hi Daniel, today I was able to start testing because there was an issue with the Nvidia driver once going to the 4.15 kernel version. So today I received the Intel microcode updates + Nvidia 390 which is compatible with 4.15 so after seeing that, I installed the 4.17 RC7 as you proposed. I have to say, it is working correctly "for now". I would like to do a longer test if that is possible with you. For example a 100 hour test, which means that since I use this about 5 hours a day for client meetings, and about 2 hours for gaming, it would be around 2 weeks of test so I can let you know with a final result what the outcome is. For now, I have not had the following errors: 1. Audio cutting in and out 2. No kernel or dmesg errors of any type. It actually showed like this when connnecting the dongle. [ 18.167592] logitech-hidpp-device 0003:046D:4069.000A: HID++ 4.5 device connected. [ 117.024265] usb 1-3: new full-speed USB device number 8 using xhci_hcd [ 117.740563] usb 1-3: New USB device found, idVendor=046d, idProduct=0a1f [ 117.740569] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 117.740572] usb 1-3: Product: Logitech G930 Headset [ 117.740574] usb 1-3: Manufacturer: Logitech [ 117.759570] input: Logitech Logitech G930 Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:046D:0A1F.000C/input/input24 [ 117.816837] hid-generic 0003:046D:0A1F.000C: input,hiddev2,hidraw7: USB HID v1.01 Device [Logitech Logitech G930 Headset] on usb-:00:14.0-3/input3 So everything looking smooth so far for the past hour. Give me if possible till the end of a 2 week test to confirm everything. -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Happy new year Daniel. No worries buddy, I fully understand. I will follow your guidelines and report back. In regards to the questions: 1. It worked for some time (I think 1 to 2 weeks which was about 30 minutes to maybe an hour if I can recall). It was on 17.10 that I did heavy test on it. Then I moved to 16.04 and it was still there. Then I noticed it was in all of the ones tested (Except for 18.04 which I will test right now). 2. Will test right away per your advice. 3. Will let you know once tested. Big hugs friend. -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Hi Daniel, wanted to share my findings for the last weeks. So I tested 16.04,16.10,17.04 and 17.10. The issue is now showing on all versions. In 17.04 I remember not seeing the issue although I might not have enough testing as am doing right now. Previously I used it for about 5 to 20 minutes in 17.04 compared to 4 to 6 hours in 17.10 and 16.04 when I tested. So it's giving the same error on all 4. What do you recommend I do now to follow up with you. Merry Christmas buddy. -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1623530] Re: Apport should be disabled by default
Just updating that in 17.04 and 17.10 it still shows, some times multiple times for the same issue. The opt-in option is better suited for end users and if a developer wants it enabled they can simply edit the apport file. But again, a year later and 2 versions later, a simple opt-in approach (that would actually help so many users I have talk to) would be the way to go. Anything else like telling the user to install something or thinking for the developer first (and forgetting the whole idea is to make a user friendly desktop system) is so wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in Apport: Confirmed Status in One Hundred Papercuts: Confirmed Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1623530/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Hi Daniel, thank you for helping out. I can report that the issues are back today (After 2 days of working). This time is crazy, it breaks more often. I had to reinstall the whole 17.10 and of course it happens but less often (Like the original bug report). -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: New Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
OK so instead of using a new or old kernel and to avoid issues with
other drivers (like Nvidia breaking with the 4.14 RC version) and based
on your feedback, I only then focused on PulseAudio. I noted that Ubuntu
17.10 is using the PulseAudio from January which is 10.0 instead of the
11.1 from September. So I grabbed the 11.1 one, downloaded the needed
dependencies and compiled the whole thing like this:
1. Make sure the Source repository is enabled since it comes disabled by
default from the Software & Updates App.
2. Install all dependencies needed
sudo apt-get build-dep pulseaudio && sudo apt-get install checkinstall
git libpulse-dev
3. Set all the flags and settings
CFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall"
CXXFLAGS="-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat -Wformat-security -Werror=format-security -Wall"
CPPFLAGS="-D_FORTIFY_SOURCE=2"
LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--no-as-needed -lxcb"
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir="\${prefix}/include" --mandir="\${prefix}/share/man"
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var
--libexecdir="\${prefix}/lib/pulseaudio" --srcdir=. --disable-
maintainer-mode --disable-dependency-tracking --disable-silent-rules
--enable-x11 --disable-hal --libdir=\${prefix}/lib/x86_64-linux-gnu
--with-module-dir=\${prefix}/lib/pulse-11.1/modules --disable-oss-
wrapper
NOTE: The above is based on PulseAudio 11.1 so if you look at the final
line it says pulse-11.1 just to help with knowing which version is
handled.
After this a simple
make -j8 (In my case)
Then
sudo make install
then reboot or kill pulseaudio. After that I have tested during the past
3 hours and have had no issues whatsoever. This solved a crackling
issues that happened every 3-5 minutes. The disconnecting and
reconnecting issues that in 3 hours would have happened about 30 times
or more. A sound issue in calls, even other members hearing me can hear
me better and no crackling sound in the back. And while testing with
steam and youtube, there was no drop in sound.
For now this is a better solution but if other bugs appear in regards to
sound issues, most probably updating to 11.1 (The whole 11.x versions
fixed several issues I was having on both, a wireless headset and the
USB connected headset). Hope this information helps along.
--
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/1725863
Title:
Logitech G930 drops connection and reconnects in 17.10 (But not in
17.04)
Status in linux package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
Every so many seconds / minutes the Wireless headset Logitech G930
simply drops connection. It always reconnects but when doing a
recording, a meeting, listening to music or a movie it simply drops
the connection for 1 to 3 second. This happens several times an hour.
If it helps, it was not happening in 17.04 (Never happened in more
than 200+ hours of using the headset).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cyrex 1288 F pulseaudio
/dev/snd/controlC2: cyrex 1288 F pulseaudio
/dev/snd/controlC0: cyrex 1288 F pulseaudio
Date: Sat Oct 21 17:55:42 2017
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
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: 06/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3504
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Yes correct, it uses it's own wireless dongle. But since this is the issue, shouldn't I update pulseaudio instead of the kernel? I already have the latest stable one, 4.13, and the 4.14 is not out yet (To avoid issues like Nvidia Module compatibility). I will try installing 4.12 to see what happens. I also checked to see if PulseAudio had a new version and the 11.1 (and 11.0) sure look like they fixed the issue by checking out their changes (Not tried it yet). -- 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/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1725863] [NEW] Logitech G930 Fails in 17.10 (But not in 17.04)
Public bug reported: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1725863 Title: Logitech G930 Fails in 17.10 (But not in 17.04) Status in pulseaudio package in Ubuntu: New Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1725863/+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 1725865] [NEW] Network shows Cable Unplugged
Public bug reported: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1725865 Title: Network shows Cable Unplugged Status in network-manager package in Ubuntu: New Bug description: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW
[Touch-packages] [Bug 1725410] [NEW] Intel Integrated Card not working Asus Hero Alpha VIII
Public bug reported: After upgrading to the latest Kernel, the issue appeared. Basically it always says there is no cable detected and the LAN (Wired) connection never works. Only wireless. If I go back to a previous Ubuntu version it works, but after either 4.12 or 4.13 the issue appeared. I also checked the BIOS version and it works only if I stay with a previous Ubuntu version. The device that is having an issue is: description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 31 serial: 34:97:f6:36:cb:d6 capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.7-4 latency=0 link=no multicast=yes port=twisted pair resources: irq:132 memory:df70-df71 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 11:59:57 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.13 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Linux 74b235bc-acdd-4fc3-a028-d960c890fbe0 802-11-wireless 1508522270 Fri 20 Oct 2017 11:57:50 AM CST yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp9s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Intel ce6b4984-a66e-306e-9a98-9487e5b3c553 802-3-ethernet 1508435911 Thu 19 Oct 2017 11:58:31 AM CST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux 74b235bc-acdd-4fc3-a028-d960c890fbe0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1725410 Title: Intel Integrated Card not working Asus Hero Alpha VIII Status in network-manager package in Ubuntu: New Bug description: After upgrading to the latest Kernel, the issue appeared. Basically it always says there is no cable detected and the LAN (Wired) connection never works. Only wireless. If I go back to a previous Ubuntu version it works, but after either 4.12 or 4.13 the issue appeared. I also checked the BIOS version and it works only if I stay with a previous Ubuntu version. The device that is having an issue is: description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 31
[Touch-packages] [Bug 1705573] [NEW] [QY7, recording] No sound at all
Public bug reported: Using 17.10 and as requested, using the Bluetooth QY7, the microphone is not working at all. The sound works but the microphone does not, so for meeting calls, it would not work at all. Similar to this case https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1705572 where I reported another device I have. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cyrex 1728 F pulseaudio /dev/snd/controlC3: cyrex 1728 F pulseaudio /dev/snd/controlC0: cyrex 1728 F pulseaudio /dev/snd/controlC1: cyrex 1728 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Jul 20 14:47:16 2017 InstallationDate: Installed on 2017-05-18 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio Symptom: audio Symptom_Card: QY7 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cyrex 1728 F pulseaudio /dev/snd/controlC3: cyrex 1728 F pulseaudio /dev/snd/controlC0: cyrex 1728 F pulseaudio /dev/snd/controlC1: cyrex 1728 F pulseaudio Symptom_Type: No sound at all Title: [QY7, recording] No sound at all UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- 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/1705573 Title: [QY7, recording] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: Using 17.10 and as requested, using the Bluetooth QY7, the microphone is not working at all. The sound works but the microphone does not, so for meeting calls, it would not work at all. Similar to this case https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1705572 where I reported another device I have. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cyrex 1728 F pulseaudio /dev/snd/controlC3: cyrex 1728 F pulseaudio /dev/snd/controlC0: cyrex 1728 F pulseaudio /dev/snd/controlC1: cyrex 1728 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Jul 20 14:47:16 2017 InstallationDate: Installed on 2017-05-18 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio Symptom: audio Symptom_Card: QY7 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cyrex 1728 F pulseaudio /dev/snd/controlC3: cyrex 1728 F pulseaudio /dev/snd/controlC0: cyrex 1728 F pulseaudio /dev/snd/controlC1: cyrex 1728 F pulseaudio Symptom_Type: No sound at all Title: [QY7, recording] No sound at all UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System
[Touch-packages] [Bug 1705572] [NEW] [CHORD MS 530, recording] Microphone problem
Public bug reported: For 17.10, as requested, here is a Bluetooth test using Audio headphones. In this case I am using the CHORD MS 530. The sound works but the microphone does not. So I can't use it for meeting calls to talk and hear at the same time. I follow the normal steps of pairing and indeed it auto selected the device in the output tab of the sound option in the system settings, but on the input tab, it simply does not show as working. It shows on the input list but there is no recording working in there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Jul 20 14:40:23 2017 InstallationDate: Installed on 2017-05-18 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CHORD MS 530 Symptom_Type: Only some of inputs are working Title: [CHORD MS 530, recording] Recording problem UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- 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/1705572 Title: [CHORD MS 530, recording] Microphone problem Status in alsa-driver package in Ubuntu: New Bug description: For 17.10, as requested, here is a Bluetooth test using Audio headphones. In this case I am using the CHORD MS 530. The sound works but the microphone does not. So I can't use it for meeting calls to talk and hear at the same time. I follow the normal steps of pairing and indeed it auto selected the device in the output tab of the sound option in the system settings, but on the input tab, it simply does not show as working. It shows on the input list but there is no recording working in there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu Jul 20 14:40:23 2017 InstallationDate: Installed on 2017-05-18 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: CHORD MS 530 Symptom_Type: Only some of inputs are working Title: [CHORD MS 530, recording] Recording problem UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1705572/+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 1623530] Re: Apport should be disabled by default
Just if anybody is wondering, apport came enabled by default on Ubuntu 16.10 and in I would say 15 minutes of installing it from scratch I had already 5 error reports, again, of things that were fixed automatically when the app reloaded itself. It just pushes the entry point of Ubuntu for new users away from being easy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in Apport: Confirmed Status in One Hundred Papercuts: Confirmed Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1623530/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
Same applies for Phiaton Chord MS 530. If I do not use A2DP, the mic works. If I set it to A2DP, the mic dies. I had to use the Bluetooth Manager (blueman) because the Bluetooth manager that comes with 16.04 could not handle the bluetooth set correctly. So basically, up to 16.04, A2DP + Mic is yet not possible (Not sure if it's Linux or the actual Bluetooth architecture). -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1623530] Re: Apport should be disabled by default
Brian, well that would not be a solution, a viable one at least. There needs to be an option that does not tell all Ubuntu users they need to install something to avoid something that should not be happening in the first place because of how it is perceived. One proposed solution is, during the installation process, ask with a simple yes/no answer if they would like to send error to Ubuntu (Or a similar idea). By default marked as no. Why marked as no, because from UX, we know users will click away at installing Ubuntu because of how easy it is. Leaving it on no will simply set the user (Who most probably is not interested or unable to send bug reports. - So disabling would create issues for Developer, but resolve the whole point for end users. - Leaving it enabled by default will make Developers happy, but make end users angry. - Setting an option for End users (On by default) will make developers happy, but there would still be a lot of users asking why Ubuntu "has" so many bugs, because they would still get so many bug reports coming up. - Setting an option for End users (Off by default) will make developers happy because only Ubuntu users that are actually interested in helping the development of it will set it to Yes, this, added to the fact that most users will stop asking about why Ubuntu "has" so many bugs. Note that, even if the wiki states that Apport is disabled by default, that is not true in reality. It still shows on 16.04 and throws bugs like crazy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1623530/+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 1623530] Re: Apport should be disabled by default
Yes, any option that helps it not involving the user would help the new users introduced to Ubuntu (Avoid getting the idea that Ubuntu is constantly having issues because of the popups) and still send the information. This can be something opt-in for the user when installing the system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1623530/+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 1623530] [NEW] Apport should be disabled by default
Public bug reported: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu- bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: New Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to
[Touch-packages] [Bug 1382845] Re: Mouse buttons are ignored
I am also experiencing this since 2 days ago on my tests. I also face the same problem with the background window receiving the clicks and the front windows caring less about them. At first I thought it was the mouse (logitech anywhere) so I changed batteries. I could move the cursor but no clicks. I even disassembled the mouse. Nothing. I then used another logitech. Same problem. It was not until I went back to 14.04 or tested on my neighbor's computer that I saw the problem. -- 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/1382845 Title: Mouse buttons are ignored Status in “xorg” package in Ubuntu: Confirmed Bug description: I have just performed a completely clean installation of Utopic from the daily ISO. After installation, however, I was unable to use the mouse buttons. Neither the left nor right mouse buttons have any effect when pressed. I tried connecting another mouse but it exhibits the same behavior - the cursor moves but the clicks don't do anything. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 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 Oct 18 12:17:13 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: Diamond Multimedia Systems Device [1092:2336] InstallationDate: Installed on 2014-10-18 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-22-generic root=UUID=7176b0ad-1080-410c-8964-7c5c6f8a38c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6401:bd07/18/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Oct 18 12:07:46 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382845/+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
