[Touch-packages] [Bug 1837317] [NEW] package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: Unknown error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Jul 14 20:33:28 2019 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2017-07-19 (731 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: apt Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to xenial on 2019-07-13 (7 days ago) mtime.conffile..etc.apt.apt.conf.d.01autoremove: 2016-04-14T09:45:21 mtime.conffile..etc.cron.daily.apt-compat: 2017-01-17T17:36:38 mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2017-01-18T14:24:43 mtime.conffile..etc.logrotate.d.apt: 2016-04-05T20:24:43 ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1837317 Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on stdin at conffile prompt Status in apt package in Ubuntu: New Bug description: Unknown error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Jul 14 20:33:28 2019 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2017-07-19 (731 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: apt Title: package apt 1.2.29ubuntu0.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to xenial on 2019-07-13 (7 days ago) mtime.conffile..etc.apt.apt.conf.d.01autoremove: 2016-04-14T09:45:21 mtime.conffile..etc.cron.daily.apt-compat: 2017-01-17T17:36:38 mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2017-01-18T14:24:43 mtime.conffile..etc.logrotate.d.apt: 2016-04-05T20:24:43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1837317/+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 1837318] [NEW] Cannot store password. Password prompt never ends
Public bug reported: Cannot store password using secret-tool. I do the following: $ secret-tool store --label='MyService' service myservice Password: sf ^C The thing is when I hit ENTER and inserting the password, the password prompt never end. So I have to hit Ctrl+C to quit the program, and hence the password is not saved. Here are my system details: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic $ apt-cache policy libsecret-tools libsecret-tools: Installed: 0.18.6-1 Candidate: 0.18.6-1 Version table: *** 0.18.6-1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: libsecret (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1837318 Title: Cannot store password. Password prompt never ends Status in libsecret package in Ubuntu: New Bug description: Cannot store password using secret-tool. I do the following: $ secret-tool store --label='MyService' service myservice Password: sf ^C The thing is when I hit ENTER and inserting the password, the password prompt never end. So I have to hit Ctrl+C to quit the program, and hence the password is not saved. Here are my system details: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic $ apt-cache policy libsecret-tools libsecret-tools: Installed: 0.18.6-1 Candidate: 0.18.6-1 Version table: *** 0.18.6-1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1837318/+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 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: Incomplete ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** No longer affects: systemd (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Cosmic) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: Incomplete Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: New Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Incomplete Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837330] [NEW] Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations
Public bug reported: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily repeatable if you have two monitors with two refresh rates, I suppose. After you set up your monitors, make sure to enable 144 Hz, then "test" it by moving your mouse around. It should feel smooth, just like it should on 144 Hz. Now move a window (such as a browser, or your file manager) around. You should notice that it still feels like it runs at 60 Hz. To sum up: What should happen: - The windows that are currently on the 144 Hz Monitor should be rendered at the specified refresh rate What actually happens - The refresh rate of rendered windows (excluding games) appears to be capped to the lowest refresh rate monitor I did test this further and it seemed to confirm my hypothesis. When I set my second, 60 Hz monitor, to run at 30 Hz, everything excluding my cursor was now being rendered at 30 Hz on both screens. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 19:47:07 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed nvidia, 418.56, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2019-07-16 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco refresh-rate ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837330 Title: Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations Status in xorg package in Ubuntu: New Bug description: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily re
[Touch-packages] [Bug 1800968] Re: nm-applet only show current wifi connection
I don't have that computer handy, but I have another one I use currently which is affected by the same issue. This computer is running Ubuntu MATE 19.04, network-manager-gnome version 1.8.20-1ubuntu1. Changing the log level to debug I see the following entries from NetworkManager: Jul 21 14:41:37 Comcast NetworkManager[976]: [1563734497.6525] device[0x561d1f3660f0] (wlp2s0): wifi-scan: scanning requested but not allowed at this time Jul 21 14:41:37 Comcast NetworkManager[976]: [1563734497.6527] device[0x561d1f3660f0] (wlp2s0): wifi-scan: scheduled in 43 seconds (interval now 43 seconds) -- 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/1800968 Title: nm-applet only show current wifi connection Status in network-manager package in Ubuntu: Incomplete Bug description: This doesn't happen all the time, but it happens quite frequently, that I'm connected to one wifi connection and there are others in the area, but when I click on nm-applet, it only displays the wifi that I'm connected to, but not the other available networks. I'm currently running Ubuntu 18.04.1 LTS, network-manager-gnome version 1.8.10-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1800968/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
I have to concur that it must this change is really a detriment to people that still use Ubuntu on physical servers - i.e. running OpenStack hosts. Fixing one problem by creating another problem is really poor problem management. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
On Sun, Jul 21, 2019 at 09:59:40PM -, atterdag wrote: > I have to concur that it must this change is really a detriment to > people that still use Ubuntu on physical servers - i.e. running > OpenStack hosts. Fixing one problem by creating another problem is > really poor problem management. I don't see how we created another problem. We changed the default, that's all. We thought the new default would be more suitable for more users. Clearly not everyone will agree with the default - that's the nature of defaults, and why the behaviour is configurable. If you think that a different default would be better for Ubuntu, by all means let's discuss that, as I described by suggesting a venue for that discussion in the previous comment. But it doesn't follow that a default not suitable in your particular situation is a problem in general. If on the other hand the problem you're describing is not a matter of the default configuration, then please file your own bug with specific details. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 1837284] Re: Initial installation does not allow high graphics resolution. Requires disabling Wayland and using Nvidia proprietary driver.
It sounds like you're reporting two problems: * Low resolution graphics by default (using the nouveau driver I guess) * Installing the Nvidia driver results in no login screen, unless you disable Wayland. Since the second problem is already covered by bug 1798790, we should make this bug about the first issue only. But since you've reported this bug with a different driver installed, after the first problem is gone, this bug report is no longer valid. To continue discussing the first issue, if you want to, please uninstall the Nvidia driver to reintroduce the resolution problem, and then open a new bug. To continue discussing the second issue, please use bug 1798790 instead. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1837284 Title: Initial installation does not allow high graphics resolution. Requires disabling Wayland and using Nvidia proprietary driver. Status in Ubuntu: Invalid Bug description: 1. Booting the system from USB 3.0 stick does not show any indication of graphics problems. 2. Upon the installation to a hard drive, the graphics resolution is below standard and cannot be changed in the system settings. 3. By installing the Nvidia driver and rebooting the system, I find that there is no graphics desktop available; apparently, level 5 was not fully reached. There is a workaround for this. I can try to press CTRL+F2 and then CTRL+F1 and the high-resolution graphical desktop becomes apparent. Switching terminals allows me to go to the graphical session. 4. Disabling Wayland in the appropriate configuration file allows the system to become fully functional. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 20 16:34:26 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-19-generic, x86_64: installed nvidia, 418.56, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM204 [GeForce GTX 970] [1462:3160] MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0dfd5d83-cd3e-4f06-bae7-d9db4e171814 verbose nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2903:bd02/22/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1837284/+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/ListHel
[Touch-packages] [Bug 1837330] Re: Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations
*** This bug is a duplicate of bug 1820832 *** https://bugs.launchpad.net/bugs/1820832 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820832, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1820832 [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837330 Title: Multiple different display refresh rates lead to the lowest one being chosen for rendering the window animations Status in xorg package in Ubuntu: New Bug description: I have two different monitors hooked up. One has a 60 Hz refresh rate, the other one has a 144 Hz one. I did make sure to select the correct resolution and refresh rate for booth. The issue is that any objects on the desktop environment such as windows (browsers, file managers, terminals), basically, every graphical part of the screen, get rendered in 60 frames per second, in stead of the correct 144 frames per second. This is very easily repeatable if you have two monitors with two refresh rates, I suppose. After you set up your monitors, make sure to enable 144 Hz, then "test" it by moving your mouse around. It should feel smooth, just like it should on 144 Hz. Now move a window (such as a browser, or your file manager) around. You should notice that it still feels like it runs at 60 Hz. To sum up: What should happen: - The windows that are currently on the 144 Hz Monitor should be rendered at the specified refresh rate What actually happens - The refresh rate of rendered windows (excluding games) appears to be capped to the lowest refresh rate monitor I did test this further and it seemed to confirm my hypothesis. When I set my second, 60 Hz monitor, to run at 30 Hz, everything excluding my cursor was now being rendered at 30 Hz on both screens. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 19:47:07 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed nvidia, 418.56, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2019-07-16 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7885 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-inp
[Touch-packages] [Bug 1837345] [NEW] PCI/internal sound card not detected
Public bug reported: Intel Corp Broadwell-U audio controller Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jul 22 08:37:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2018-07-11 (375 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0N7TKY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0N7TKY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1837345 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Intel Corp Broadwell-U audio controller Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jul 22 08:37:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2018-07-11 (375 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0N7TKY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0N7TKY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1837345/+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 1803192] Re: Internal MIC stopped to work on 18.10
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803192 Title: Internal MIC stopped to work on 18.10 Status in pulseaudio package in Ubuntu: Won't Fix Bug description: After upgrading my mon's laptop from Kubuntu 18.04 to 18.10, the internal Mic stop to work. Everything works well (speakers, etc) however no more sound comes as entry from Internal Mic. I checked and she has chipset ALC269VB i update to alsa-driver 1.1.7 without success. i checked alsamixer and everything seems ok as with pavucontrol. I upgraded my laptop too to 18.10 and i have no issue with internal mic but i do not have the same chipset. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paulette 4997 F pulseaudio /dev/snd/pcmC0D0c: paulette 4997 F...m pulseaudio /dev/snd/pcmC0D0p: paulette 4997 F...m pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-28 (259 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) Package: pulseaudio 1:12.2-0ubuntu4 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf] PackageArchitecture: amd64 Tags: cosmic Uname: Linux 4.19.0-041900-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-11-04 (10 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11: dmi.product.name: Aspire 5750G dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803192/+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 1803016] Re: Ubuntu 18.10 and ASUS ZenBook Flip Q536FD integrated Speakers not sounds
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803016 Title: Ubuntu 18.10 and ASUS ZenBook Flip Q536FD integrated Speakers not sounds Status in alsa-driver package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Bluetooth and HDMI sound it is ok, but the integrated speakers not sounds. Distro: Description: Ubuntu 18.10 Release: 18.10 Info: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 hwinfo --sound 18: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.sos2QFV32t3 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9dc8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1481 Revision: 0x30 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xb4218000-0xb421bfff (rw,non-prefetchable) Memory Range: 0xb410-0xb41f (rw,non-prefetchable) IRQ: 140 (1419 events) Module Alias: "pci:v8086d9DC8sv1043sd1481bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: natanael 2115 F pulseaudio /dev/snd/pcmC0D0p: natanael 2115 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-11-08 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Tags: cosmic Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q536FD.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q536FD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ536FD.203:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnZenBookQ536FD_Q536FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ536FD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook Q536FD_Q536FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1803016/+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 1769914] Re: PulseAudio configures Fiio E10K DAC/headphone amp as input, but it only is a sink
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1769914 Title: PulseAudio configures Fiio E10K DAC/headphone amp as input, but it only is a sink Status in pulseaudio package in Ubuntu: Won't Fix Bug description: PulseAudio thinks that a Fiio E10K can capture audio and tries to configure that, leading to a ton of: retire_capture_urb: 2492 callbacks suppressed messages in dmesg. The device has no capture ability, alsamixer also only shows one master playback control; no capture one. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak2367 F...m pulseaudio /dev/snd/controlC2: jak2367 F pulseaudio /dev/snd/controlC1: jak2367 F pulseaudio /dev/snd/controlC0: jak2367 F pulseaudio CurrentDesktop: GNOME Date: Tue May 8 16:43:47 2018 InstallationDate: Installed on 2018-03-14 (54 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET31W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1769914/+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 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Won't Fix -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Won't Fix Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1690052] Re: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state()
** Tags removed: artful cosmic yakkety zesty -- 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/1690052 Title: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/49a8e58cea0b15b22d3a3cdbb1d736e619467e34 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690052/+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 1690026] Re: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_inf
** Tags removed: cosmic -- 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/1690026 Title: pulseaudio crashed with SIGABRT in pa_sconv_s16le_from_f32ne_sse2() from convert_to_work_format() from pa_resampler_run() from pa_sink_input_peek() from fill_mix_info() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/09eaa7a762edd70e8a3d904cb32f366b3c3211a1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690026/+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 1591535] Re: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds.
** Tags removed: cosmic -- 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/1591535 Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all. My built-in internal mic won't record sounds. Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/618 --- My built-in internal mic on my Toshiba Satellite-A215 will not pick up sounds. The external speakers work just fine, but once again the mic can't record any sounds. I have an Ubuntu 14.04.4 LTS. Below is a link of my ALSA "info" that may be useful: http://www.alsa- project.org/db/?f=10a2337ec9b863d7414121dff10f30ad0cdf430d I've tried the ALSA DKMS update recommended to me by an ubuntuforums.org user from this link: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS However after following the instructions from the above link, the mic still has not worked. The same Ubuntu forum user suggested I file a bug. He/she provided me with a link from "an old report from an A215 with the same ALC268 codec": https://bugs.launchpad.net/ubuntu/+s...r/+bug/1081353 I provided this because it may be helpful in the debug process. The version of ALSA I have is shown below: Advanced Linux Sound Architecture Driver Version k3.19.0-61-generic. Any help would be appreciated, please let me know if you need any additional info. PS I've also provided a link below of the ongoing forum discussion I've been having at ubuntuforums.org below: http://ubuntuforums.org/showthread.php?t=2323851 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21 Uname: Linux 3.19.0-61-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1533 F pulseaudio CurrentDesktop: Unity Date: Sat Jun 11 10:49:01 2016 InstallationDate: Installed on 2016-01-06 (156 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1533 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [Satellite A215, Realtek ALC268, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.10 dmi.board.name: IALAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.10:bd05/23/2007:svnTOSHIBA:pnSatelliteA215:pvrPSAEGU-01700U:rvnTOSHIBA:rnIALAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A215 dmi.product.version: PSAEGU-01700U dmi.sys.vendor: TOSHIBA mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-06T05:53:22.078529 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1591535/+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 1571724] Re: mate-settings-daemon crashed with SIGSEGV in glib_io_free() from delete_events() from pa_iochannel_free() from pa_pstream_unlink() from context_unlink()
** Tags removed: artful cosmic wily yakkety zesty -- 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/1571724 Title: mate-settings-daemon crashed with SIGSEGV in glib_io_free() from delete_events() from pa_iochannel_free() from pa_pstream_unlink() from context_unlink() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/48bd2dca48ca53fe7f2bc00c913addbbe0daf3b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1571724/+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 1836809] Re: segfault when CCD are present in two different HOG services
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: Won't Fix Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+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 1826516] Re: bluetooh mouse lag when use bluetooth hedphones
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1826516 Title: bluetooh mouse lag when use bluetooth hedphones Status in bluez package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: I have Microsoft Sculpt Comfort Mouse (bluettoh) and it works. When i connect my bluetooth heaset (plantronics PLT 50) mouse cursor lags terribly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 09:19:08 2019 InstallationDate: Installed on 2018-12-22 (124 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20LW000YPB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.9-050009-generic root=UUID=74c51606-28cc-4d8f-91ac-c1d0dfd082c3 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET54W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW000YPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000YPB:pvrThinkPadL580:rvnLENOVO:rn20LW000YPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW000YPB dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:21:6B:EA:3C:5F ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:21050738 acl:78587 sco:377825 events:21982 errors:0 TX bytes:19896288 acl:159 sco:377811 commands:5333 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2019-04-15T07:00:56.250208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1826516/+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 1692448] Re: Bluetooth speaker fails to reconnect when turned on (but it tries)
** Tags removed: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1692448 Title: Bluetooth speaker fails to reconnect when turned on (but it tries) Status in bluez package in Ubuntu: New Bug description: Bluetooth speaker fails to reconnect when turned on. Watching the Bluetooth icon in the Unity panel I can see it is trying (B icon briefly gets the expected padlock and then loses it). The speaker doesn't reconnect then unless initiated by the laptop (set Connection = ON in the panel). Note this bug is only about the Bluetooth connection, and not about audio problems (of which there are a few). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 16:28:37 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20CM0010AU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM0010AU dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM0010AU dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 34:02:86:EE:0F:47 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0 TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1692448/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions)
** Tags removed: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions) Status in GTK+: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix ** Changed in: mesa (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+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 1738676] Re: With natural scrolling, horizontal sliders behave backwards
** Tags removed: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1738676 Title: With natural scrolling, horizontal sliders behave backwards Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: When natural-scrolling is enabled, controlling horizontal sliders is backwards and counter intuitive. The volume control in the top-bar "speaker" icon is backwards. You have to... - scroll DOWN, to INCREASE the volume - scroll UP, to DECREASE the volume Expected behavior: Enable natural-scrolling and - scroll UP, to INCREASE the volume - scroll DOWN, to DECREASE the volume - scroll UP, to INCREASE the screen brightness - scroll DOWN, to DECREASE the screen brightness Enable natural-scrolling, hover over a horizontal slider, and... - scroll UP, to move the slider to the RIGHT - scroll DOWN, to move the slider to the LEFT This happens for the OSD volume icon, and for the volume slider in the topbar menu. This also happens for screen brightness controls. This problem occurs for both mouse natural-scrolling and touchpad natural scrolling. Expected fix: When the pointer hovers over the speaker icon in the scroll actions on the speaker icon in the top bar should be reversed. When the user interacts with a horizontal slider, scrolling to the top should always move the slider to the right, and scrolling down should always move the slider to the left, even if natural-scrolling is enabled. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 17 19:23:30 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-12-10 (7 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+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 1693724] Re: Context menus have no animation/fade-in under Gnome Shell
** Tags removed: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693724 Title: Context menus have no animation/fade-in under Gnome Shell Status in gnome-shell package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: Confirmed Status in gnome-shell package in Arch Linux: New Bug description: Context menus have no animation/fade-in under Gnome Shell. The transitions under Unity7 for context menus look nicer, less abrupt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+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 1836290] Re: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed
** Tags removed: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836290/+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 1808193] Re: Battery percentage changes suddenly depending on whether AC is plugged in
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix ** Changed in: upower (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery percentage changes suddenly depending on whether AC is plugged in Status in gnome-shell package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in upower package in Ubuntu: Won't Fix Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: upower PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+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 1837345] Re: PCI/internal sound card not detected
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011. Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010. Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010. Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011. Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009. Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1837345 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: Intel Corp Broadwell-U audio controller Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jul 22 08:37:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2018-07-11 (375 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0N7TKY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/01/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0N7TKY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1837345/+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 1829973] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1829973 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() Status in evolution-data-server package in Ubuntu: Expired Bug description: It was running in the background. I didn't do anything actively. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 17 20:00:10 2019 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory InstallationDate: Installed on 2017-10-13 (585 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory Signal: 5 SourcePackage: evolution-data-server StacktraceTop: g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 e_data_factory_spawn_subprocess_backend () at /usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10 () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() UpgradeStatus: Upgraded to bionic on 2018-06-25 (330 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1829973/+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 1807842] Re: [nouveau] Damage screen on boot
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix ** Changed in: mesa (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1807842 Title: [nouveau] Damage screen on boot Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: I install Ubuntu 18.10 and when I booting system (installed or from usb) I see "broken" screen before system show desktop (attached photo). On this damage screen I see mouse cursor, but is OK and when I try move cursor arround screen in every place cursor is OK, but background of screen is broken. In Ubuntu 18.04.1 LTS is everything OK. I try nvidia drivers, but I have another problem: screen is not damaged, but when I open Activities or when I typing password on every keypress or cursor move screen blinking on bottom side. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Prístup odmietnutý: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 08:57:41 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.18.0-10-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0647] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. G96M [GeForce 9600M GT] [106b:00bc] NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. C79 [GeForce 9400M] [106b:00bb] InstallationDate: Installed on 2018-12-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Apple Inc. MacBookPro5,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=46b8171c-35ba-4d62-9203-2edd74237d37 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,3:pvr1.0:rvnAppleInc.:rnMac-F22587C8:rvr:cvnAppleInc.:ct10:cvrMac-F22587C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro5,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807842/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
[Expired for openvpn (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openvpn (Ubuntu) Status: Incomplete => Expired -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Expired Status in openvpn package in Ubuntu: Expired Bug description: [Triage Notes] This report can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Expired Status in openvpn package in Ubuntu: Expired Bug description: [Triage Notes] This report can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1813314] Re: [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume. Low volume quality than on windows 10.
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1813314 Title: [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume. Low volume quality than on windows 10. Status in alsa-driver package in Ubuntu: Won't Fix Bug description: When I increase the volume indicator to 1.0 (probably in the gnome desktop it is 100%) the sound is lower quality than in windows 10. Please. Repair it. Lenovo thinkpad t410, conexant cx 20585 soundcard, processor intel core i5 520M, (2.40GHZ, 2 cores 4 threats.) Ram 4GB. If it does matter, I use orca screenreader. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogus 1794 F pulseaudio /dev/snd/pcmC0D0p: bogus 1794 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 25 15:55:07 2019 InstallationDate: Installed on 2019-01-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Wbudowany dźwięk - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_Type: High background noise, or volume is too low Title: [2537G98, Conexant CX20585, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2537G98 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2537G98:pvrThinkPadT410:rvnLENOVO:rn2537G98:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2537G98 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-01-25T15:02:33.273945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813314/+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 1827854] Re: [Vostro 14-3468, Realtek ALC3246, Black Headphone Out, Front] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1827854 Title: [Vostro 14-3468, Realtek ALC3246, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: There is no sound coming when i use earphones and the speakers are working okay , I have checked my earphones are also okay and working fine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kaushal2918 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 15:05:43 2019 InstallationDate: Installed on 2018-11-16 (170 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kaushal2918 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Vostro 14-3468, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to cosmic on 2019-04-20 (15 days ago) dmi.bios.date: 02/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.0 dmi.board.name: 0T1X3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.0:bd02/06/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827854/+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 1833010] Re: PCI/internal sound card not detected
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1833010 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Linx 1010b Tablet converted from Windows 10 to Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1931 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 22:29:12 2019 InstallationDate: Installed on 2019-06-14 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: LINX1010B.R22.03.010 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrLINX1010B.R22.03.010:bd07/24/2015:svnLINX:pnLINX1010B:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: LINX1010B dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: LINX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802631] Re: [AX370-Gaming 5, Realtek ALC1220, Green Headphone Out, Front] No sound at all, sound is played through speakers plugged in the back instead of the headphones plugged
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1802631 Title: [AX370-Gaming 5, Realtek ALC1220, Green Headphone Out, Front] No sound at all, sound is played through speakers plugged in the back instead of the headphones plugged in the front Status in alsa-driver package in Ubuntu: Won't Fix Bug description: What happens: plugging in headphones in the front jack is detected (icon in the sound settings is changed to headphones correctly), but no sound is played through the headphones. Sound is still reproduced through speakers plugged in the back and the volume settings are being ignored. Expected results: sound plays through the headphones when headphones are plugged in and when they are plugged in, speakers are not playing any audio. Ubuntu version: Description: Ubuntu 18.10 Release: 18.10 Package versions: alsa-base/cosmic,cosmic,now 1.0.25+dfsg-0ubuntu5 all [installed,automatic] alsa-utils/cosmic,now 1.1.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/cosmic,now 1.14.4-1ubuntu1 amd64 [installed,automatic] libao-common/cosmic,cosmic,now 1.2.2+20180113-1ubuntu1 all [installed,automatic] libao4/cosmic,now 1.2.2+20180113-1ubuntu1 amd64 [installed,automatic] libasound2/cosmic,now 1.1.6-1ubuntu1 amd64 [installed,automatic] libasound2-data/cosmic,cosmic,now 1.1.6-1ubuntu1 all [installed,automatic] libasound2-plugins/cosmic,now 1.1.6-1ubuntu1 amd64 [installed,automatic] libavdevice58/cosmic,now 7:4.0.2-2 amd64 [installed,automatic] libgcrypt20/cosmic,now 1.8.3-1ubuntu1 amd64 [installed,automatic] libopenal1/cosmic,now 1:1.18.2-3build1 amd64 [installed,automatic] libpcaudio0/cosmic,now 1.1-2 amd64 [installed,automatic] libsdl1.2debian/cosmic,now 1.2.15+dfsg2-2 amd64 [installed,automatic] libsdl2-2.0-0/cosmic,now 2.0.8+dfsg1-4ubuntu1 amd64 [installed,automatic] linux-sound-base/cosmic,cosmic,now 1.0.25+dfsg-0ubuntu5 all [installed,automatic] nautilus-sendto/cosmic,now 3.8.6-2 amd64 [installed,automatic] pulseaudio/cosmic,now 1:12.2-0ubuntu4 amd64 [installed,automatic] sound-theme-freedesktop/cosmic,cosmic,now 0.8-2ubuntu1 all [installed,automatic] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mspehar2531 F pulseaudio /dev/snd/controlC1: mspehar2531 F pulseaudio /dev/snd/controlC0: mspehar2531 F pulseaudio CurrentDesktop: GNOME Date: Sat Nov 10 11:11:08 2018 InstallationDate: Installed on 2018-10-20 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mspehar2531 F pulseaudio /dev/snd/controlC1: mspehar2531 F pulseaudio /dev/snd/controlC0: mspehar2531 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [AX370-Gaming 5, Realtek ALC1220, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default
[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
** Tags removed: cosmic -- 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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor
[Touch-packages] [Bug 1810287] Re: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810287 Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I don,t know about packages. I am new to ubuntu. There is an irritating crackling and buzzy sound along with the audio from speakers ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giri 1966 F pulseaudio /dev/snd/controlC0: giri 1966 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 15:54:22 2019 InstallationDate: Installed on 2019-01-01 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jan 02 15:44:58 giri-HP-Pavilion-15-Notebook-PC dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.45' (uid=1000 pid=1966 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.56:bd06/29/2018:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: J6M42PA#ACJ dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-02T15:54:03.591051 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1810287/+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 1802653] Re: [HDA-Intel - HDA ATI HDMI, playback] No sound at all
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1802653 Title: [HDA-Intel - HDA ATI HDMI, playback] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: v ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: betab 2401 F pulseaudio /dev/snd/pcmC1D1p: betab 2401 F...m pulseaudio /dev/snd/controlC0: betab 2401 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 10 14:46:54 2018 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: betab 2401 F pulseaudio /dev/snd/pcmC1D1p: betab 2401 F...m pulseaudio /dev/snd/controlC0: betab 2401 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA ATI HDMI, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: A320M-DS2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: 7438518-007 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/05/2017:svnNOVATECHLTD:pnBB-95004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-DS2-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: BB-95004 dmi.product.sku: BB-95004 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802653/+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 1802631] Re: [AX370-Gaming 5, Realtek ALC1220, Green Headphone Out, Front] No sound at all, sound is played through speakers plugged in the back instead of the headphones plugged
This behaviour is the same in 19.04 as well... Front jack is just not working -- 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/1802631 Title: [AX370-Gaming 5, Realtek ALC1220, Green Headphone Out, Front] No sound at all, sound is played through speakers plugged in the back instead of the headphones plugged in the front Status in alsa-driver package in Ubuntu: Won't Fix Bug description: What happens: plugging in headphones in the front jack is detected (icon in the sound settings is changed to headphones correctly), but no sound is played through the headphones. Sound is still reproduced through speakers plugged in the back and the volume settings are being ignored. Expected results: sound plays through the headphones when headphones are plugged in and when they are plugged in, speakers are not playing any audio. Ubuntu version: Description: Ubuntu 18.10 Release: 18.10 Package versions: alsa-base/cosmic,cosmic,now 1.0.25+dfsg-0ubuntu5 all [installed,automatic] alsa-utils/cosmic,now 1.1.6-1ubuntu1 amd64 [installed,automatic] gstreamer1.0-alsa/cosmic,now 1.14.4-1ubuntu1 amd64 [installed,automatic] libao-common/cosmic,cosmic,now 1.2.2+20180113-1ubuntu1 all [installed,automatic] libao4/cosmic,now 1.2.2+20180113-1ubuntu1 amd64 [installed,automatic] libasound2/cosmic,now 1.1.6-1ubuntu1 amd64 [installed,automatic] libasound2-data/cosmic,cosmic,now 1.1.6-1ubuntu1 all [installed,automatic] libasound2-plugins/cosmic,now 1.1.6-1ubuntu1 amd64 [installed,automatic] libavdevice58/cosmic,now 7:4.0.2-2 amd64 [installed,automatic] libgcrypt20/cosmic,now 1.8.3-1ubuntu1 amd64 [installed,automatic] libopenal1/cosmic,now 1:1.18.2-3build1 amd64 [installed,automatic] libpcaudio0/cosmic,now 1.1-2 amd64 [installed,automatic] libsdl1.2debian/cosmic,now 1.2.15+dfsg2-2 amd64 [installed,automatic] libsdl2-2.0-0/cosmic,now 2.0.8+dfsg1-4ubuntu1 amd64 [installed,automatic] linux-sound-base/cosmic,cosmic,now 1.0.25+dfsg-0ubuntu5 all [installed,automatic] nautilus-sendto/cosmic,now 3.8.6-2 amd64 [installed,automatic] pulseaudio/cosmic,now 1:12.2-0ubuntu4 amd64 [installed,automatic] sound-theme-freedesktop/cosmic,cosmic,now 0.8-2ubuntu1 all [installed,automatic] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mspehar2531 F pulseaudio /dev/snd/controlC1: mspehar2531 F pulseaudio /dev/snd/controlC0: mspehar2531 F pulseaudio CurrentDesktop: GNOME Date: Sat Nov 10 11:11:08 2018 InstallationDate: Installed on 2018-10-20 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mspehar2531 F pulseaudio /dev/snd/controlC1: mspehar2531 F pulseaudio /dev/snd/controlC0: mspehar2531 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [AX370-Gaming 5, Realtek ALC1220, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802631/+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
