[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The UX391UA fix is not in 4.20 as it was already a release candidate. To get sound working on this model you'll need to download the 4.20 source, apply the patch to sound/pci/hda/patch_realtek.c then compile and install the kernel. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+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 1802135] Re: broken touchpad after i2c-i801 blacklist change
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1802135 Title: broken touchpad after i2c-i801 blacklist change Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in kmod source package in Xenial: Fix Committed Status in linux source package in Xenial: Confirmed Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in kmod source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU: [Impact] ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801. PNP LEN0049 will use smbus by default in kernel, but i2c bus is in runtime suspend mode in old touchpad fw. Then touchpad will not work. LEN2040 on 11e 3rd can reproduce this issue by passing psmouse.synaptics_intertouch=1 These 2 pnp device should be the same one Synaptics s3203_ver5. [Fix] i2c-i801 should auto suspend when not used, no need runtime pm. [Test Case] Tested on Thinkpad 11e 3rd. Touchpad works fine. [Regression Potential] Low, upstream fix cherry-picked. 4.18 kernel patch, no need for cosmic. Original bug report: = After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 11e 2nd gen machines. We have a fleet of approximetly 1000 of them in production running ubuntu 18.04. Prior to this update the trackpads worked out of box in 18.04. We are currently working around the issue by deploying our own blacklist files. Here is a link to the SRU justification: https://bugs.launchpad.net /hwe-next/+bug/1786574 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+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 1759836] Re: systemd-udevd consumes 100% of CPU
I can confirm that the solution Florian posted (modifying /lib/udev/rules.d/97-hid2hci.rules) works for me as well. Dell Latitude E6500, Kubuntu 18.04 with hwe kernel (4.18.0-13-generic), udev/systemd version 237-3ubuntu10.9, bluez version 5.48-0ubuntu3.1 -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1644643] Re: apt failed to run due to link time reference error
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- 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/1644643 Title: apt failed to run due to link time reference error Status in apt package in Ubuntu: Expired Bug description: After update apt and its related library to 1.2.15 from 1.2.10ubuntu1, I get following message when I try to invoke apt: apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt- private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference 1.2.10 do not have this problem. Now I manually downgrade from 1.2.15 to 1.2.10 to solve this problem. Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 what I expect to happen: apt would show the helper message what happened instead: apt shows me the line on above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 901622] Re: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) )
Same issue as everyone else. I have my system(/home and the likes) on the SD Card and /boot on the internal SSD. I have my OS installed this way is because my Laptop BIOS doesn't allow booting directly from SD Card(perhaps because internally the SD Reader is connected via the PCI bus) This way the laptop boots to the regular destination(Internal SSD) then GRUB loads and then I can select my desired OS, then GRUB will find the Kernel(/boot) and then handoff to the SD Card. This all works as expected with the only problem being that my system will not suspend no matter how I try. I see a flashing cursor on screen while trying to resume from suspend and then I will get read-only errors. The only way to get past this is to do a full reboot. Most of the time requiring a full fsck to fix the orphaned inodes, etc. So what is the advisable solution? Is the problem the fact that my SD Card reader is on the PCI bus and therefore is having trouble with the hotplug driver? Could a plausible solution be to disallow the system from unmounting my SD Card? I mean after all this SD Card while *removable* isn't actually going to be removed during operation of the system, much less while in hibernate. As far as I can tell the system unmounts all sd cards so as to prevent data loss, assuming that it can be removed during suspend, and that is all fine as the majority of people benefit from this decision however how do I disable this feature? Any help would be greatly appreciated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/901622 Title: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) ) Status in pm-utils package in Ubuntu: Confirmed Bug description: After the upgrade to Oneiric resume from pm-suspend no longer works, might be connected to change of kernel from 2.6.38 to 3.0.0... Issue also reported for Arch Linux and kernel 2.6.39 here: https://bbs.archlinux.org/viewtopic.php?pid=1008743 See attached dmesg output for details This is for kernel 3.0.0-14-server x86_64 (but also occured on 3.0.0-13) and a NAS booting from a USB stick. --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 Package: pm-utils 1.4.1-8ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: Upgraded to oneiric on 2011-10-17 (51 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/901622/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** Description changed: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html - https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port- - from-aptdaemon-to-packagekit + https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in mythbuntu-control-centre package in Ubuntu: Fix Released Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I have the same issue here: xrandr output: Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 353mm x 198mm 1366x768 60.00*+ 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) SVIDEO-1 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400
[Touch-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
FYI, HDMI output works when I switch to a terminal using CTRL_ALT_F3. It seems to not work only in graphics mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.75KHz v: height 1080 start 1084 end 1094 total
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files
** Changed in: initramfs-tools (Ubuntu) Assignee: Colin Underhill (daisybank) => Julio Decima (j10a) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files Status in initramfs-tools: New Status in Ubuntu Software Center: Invalid Status in Ubuntu: Fix Released Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1809989] Re: deluser does not clean up systemd files
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1809989 Title: deluser does not clean up systemd files Status in adduser package in Ubuntu: New Bug description: In Description: Ubuntu 16.04.4 LTS Release: 16.04 using adduser package Version: 3.113+nmu3ubuntu4 systemd package Version: 229-4ubuntu21.10 deluser will not clean up data in /run/user/ directory. If a user is created then under many circumstances, such as systemd enable-linger being called for the user, data for that user will exist in /run/user/. Running deluser for such as user will remove the user, home directory, etc. but not the /run/user data. ** Most importantly **, the next user creation will be given the open uid formerly held by the deleted user. The new user can then have broken systemd sessions so that the systemctl --user command will always fail with the error Failed to connect to bus: No such file or directory A system reboot seems to be the only thing that will reliably clean up the cruft in /run/user/ Expected behavior would be that if a user is successfully removed then there should be no directory remaining for that user's uid under /run/user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1809989/+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 1726075] Re: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all
Same issue, HP Pavilion 15-cc178cl. Tried: - checking that speakers aren't muted in alsamixer & pavucontrol - renaming /etc/modprobe.d/alsa-base.conf - model={generic,auto,hp} in /etc/modprobe.d/alsa-base.conf - adding these lines to ~/.config/pulse/default.pa: https://askubuntu.com/a/1068198 (this caused pulse to fail to start) - remapping each output pin to "Internal Speakers" in hdajackretask Have not tried: - uninstalling and reinstalling alsa and pulse (this appears to want to uninstall ubuntu-desktop--is that expected?) alsa-info: http://www.alsa- project.org/db/?f=50bc75eae4b64a7d838f66b581e79cf696920eeb -- 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/1726075 Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I cannot hear anything without headphone, the speaker don't work at all, even though after i set the speaker volume bar in the alsamixer panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remaincool 1862 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 23 00:57:26 2017 InstallationDate: Installed on 2017-07-06 (108 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: 内置音频 - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remaincool 1862 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1726075/+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 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start
** Description changed: I have an ASUS P10S-I server motherboard with integrated ASPEED AST2400 VGA chipset. With earlier Ubuntu version (maybe on Ubuntu 16.04.3 ?) it worked well. Once when I updated (but before the actual version) it went wrong. To be truth it not really the xresver...-ast's problem because this earlier not installed automatically and the poroblem was the same. When - i fond it on synaptic as uninstalled i hoped this will solv the problem - and i had installed it but it not worked at all... + i found it on synaptic as uninstalled i hoped that this will solve the + problem and i had installed it but it not worked at all... The issue: When I boot normally the login window load slowly and keybord and mouse very slow too but work. I can login. But after i login the screen not show the desktop it show diagonal stripes. (see the attachment) This stripes made from original screen but unrecognisable the things. But the items work if you can click the right places. (for example i can click on the main switch button if i have luck and Crl+Alt+Del log out me.) After i log out the login screen corrupted on the same diagonal stripe way. But also work I can re login. How it work: If I start the recovery mode and on the recovery window choose continue start normally (and nothing else needed) it works without problem. Evrithing is fine. I tried to indtal ASPEED driver but on the Softwares and Updates menu Another driver don't found it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Engedély megtagadva: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 28 00:28:01 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] InstallationDate: Installed on 2017-11-20 (402 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a: Creative Labs Optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. P10S-I Series ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1e49958f-dcf2-402d-b5ec-4e379ec72739 ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P10S-I Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4401:bd03/05/2018:svnASUSTeKCOMPUTERINC.:pnP10S-ISeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP10S-ISeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Server dmi.product.name: P10S-I Series dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Dec 28 00:17:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputHID 062a:MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.23 ** Description changed: I have an ASUS P10S-I server
[Touch-packages] [Bug 1810050] [NEW] screen glitch in dock
Public bug reported: i found a glitch in the dock when closing out of the screen switch menu down by the activities button. it changes back to the normal colour when the mouse cursor hovers over it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 15:37:21 2018 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fce0] InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181225) MachineType: TOSHIBA Satellite C650 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=22135462-7795-4371-b6e5-dbb5a4541789 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.00:bd04/01/2011:svnTOSHIBA:pnSatelliteC650:pvrPSC2EC-00M001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C650 dmi.product.sku: PSC2EC-00M001 dmi.product.version: PSC2EC-00M001 dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 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+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption disco reproducible single-occurrence ubuntu ** Attachment added: "Screenshot from 2018-12-29 15-34-17.png" https://bugs.launchpad.net/bugs/1810050/+attachment/5225716/+files/Screenshot%20from%202018-12-29%2015-34-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1810050 Title: screen glitch in dock Status in xorg package in Ubuntu: New Bug description: i found a glitch in the dock when closing out of the screen switch menu down by the activities button. it changes back to the normal colour when the mouse cursor hovers over it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 15:37:21 2018 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fce0] InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181225) MachineType: TOSHIBA Satellite C650 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=22135462-7795-4371-b6e5-dbb5a4541789 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias:
[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot
Hi, I can confirm this bug still exists on Ubuntu 18.04 and in my case none of the above solutions have been successful. The following workaround has solved it for me: Edit /etc/crontab and add the following line: @reboot rootufw enable It has worked every time on 5 reboots I have done to test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot Status in ufw: Invalid Status in ufw package in Ubuntu: Invalid Status in ufw source package in Xenial: Invalid Status in ufw source package in Bionic: Invalid Status in ufw source package in Cosmic: Invalid Status in ufw source package in Disco: Invalid Bug description: Whenever I boot into 17.10 ufw is always inactive, even though /etc/ufw/ufw.conf has this: # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:56:40 2017 InstallationDate: Installed on 2015-04-01 (936 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+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 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start
** Description changed: I have an ASUS P10S-I server motherboard with integrated ASPEED AST2400 VGA chipset. With earlier Ubuntu version (maybe on Ubuntu 16.04.3 ?) it worked well. Once when I updated (but before the actual version) it went wrong. + + To be truth it not really the xresver...-ast's problem because this + earlier not installed automatically and the poroblem was the same. When + i fond it on synaptic as uninstalled i hoped this will solv the problem + and i had installed it but it not worked at all... The issue: When I boot normally the login window load slowly and keybord and mouse very slow too but work. I can login. But after i login the screen not show the desktop it show diagonal stripes. (see the attachment) This stripes made from original screen but unrecognisable the things. But the items work if you can click the right places. (for example i can click on the main switch button if i have luck and Crl+Alt+Del log out me.) After i log out the login screen corrupted on the same diagonal stripe way. But also work I can re login. How it work: If I start the recovery mode and on the recovery window choose continue start normally (and nothing else needed) it works without problem. Evrithing is fine. I tried to indtal ASPEED driver but on the Softwares and Updates menu Another driver don't found it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.1: - + ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Engedély megtagadva: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 28 00:28:01 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] + ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] InstallationDate: Installed on 2017-11-20 (402 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 062a: Creative Labs Optical mouse - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 062a: Creative Labs Optical mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. P10S-I Series ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=hu_HU.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=hu_HU.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1e49958f-dcf2-402d-b5ec-4e379ec72739 ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P10S-I Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4401:bd03/05/2018:svnASUSTeKCOMPUTERINC.:pnP10S-ISeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP10S-ISeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Server dmi.product.name: P10S-I Series dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Dec 28 00:17:45 2018 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower
[Touch-packages] [Bug 1798868] Re: Compiz Crashed with SIGSEGV [Radeon]
** Description changed: + SEE WORKAROUND AT END OF POST + Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the necessary debug packages installed. However, I could not find the debug packages in the repository, so that is why I am submitting this report manually. Many thanks for any help. + + Edit 29/12/2018: + WORKAROUND + This bug is still present. However, I present a workaround. It is aimed at relatively inexperienced users like me. It guides the user through downgrading/rolling back affected packages to the most recent known working versions. + 1. Navigate to /var/log/apt in a file explorer. Open the logs until you find the offending mesa updates. In my case, the updates were installed on 15/07/18. + 2. Copy and paste the log into a text file on your desktop. Close the log. + 3. In the text file, do a ctrl+F search on "mesa" to highlight all instances of mesa-related packages. Keep these lines and delete the others. Each line should have this kind of format: + libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) (exact package name/version numbers may differ). The first number in brackets is the version of the package that you had before, the second number is the version it was upgraded to. You should end up with a list of such lines. + 4. The earlier versions of these packages can be downloaded from Launchpad. I don't know how to find them using links/searches, but the URLs look like this: + https://launchpad.net/ubuntu/xenial/amd64/libgles2-mesa/17.2.8-0ubuntu0~16.04.1. You will have to alter the url according to your architecture, package name and package version required. + 5. You will see a page with a download link on the right-hand side for a .deb file. Make a new folder on your desktop called "mesa-install" and download the .deb file there. + 6. Scroll down, and on the left, you will see any dependencies of this package. If any of them say " (=version number)" then you must make a note of these packages on your list of packages to download and install. If they have a ">=" sign, or no version number given, ignore them. + 7. Repeat steps 4 - 6 for all the packages on your list, placing the .deb files in the "mesa-install" folder. + 8. MAKE SURE ALL IMPORTANT FILES ON YOUR SYSTEM ARE BACKED UP. + 9. Open a terminal (Ctrl + Alt + T). + 10. Type "sudo dpkg -R --install /home//Desktop/mesa-install/ + Replace " with your username. This command installs all .deb files in that folder. + 11. Reboot PC. + 12. Log in to a Unity session. Rejoice in the fact that it now works (hopefully). Assuming it is now working, you need to make sure that the packages you downgraded are not subsequently upgraded automatically by Ubuntu. Ignore any offers of automatic updates until you have completed all the steps. + 13. Open a terminal and type: + sudo apt-mark hold + where "" is the name of the first package you downgraded. Press enter, enter password, etc. You should receive confirmation that the package has been held. + 14. Repeat step 13 for all packages on your list. + + Good luck to all others who have faced this problem, and fingers crossed + for a bug 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/1798868 Title: Compiz Crashed with SIGSEGV [Radeon] Status in mesa package in Ubuntu: New Bug description: SEE WORKAROUND AT END OF POST Symptoms: On login, the desktop takes a long time to load, and when it does, everything blinks. It is possible (but difficult) to open a terminal and execute commands, through the right-click desktop menu. I first noticed the issue in mid-July of 2018. System: Acer 5100 Ubuntu 16.04 (64-bit) Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] Believed to be mesa-related, as symptoms very similar to bug #1741447 and #1735594. I have been informed by a mesa developer that my issue is different because that bug affects Intel GPUs. This system has a Radeon GPU. Log files are as attached to bug #1795709. That bug was declared invalid by Apport because it says I don't have the
[Touch-packages] [Bug 1810039] Re: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]
Do not know if it is a pulseaudio or a alsa-driver bug (cf. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PulseAudioStoleMyVolumes/) but I think it is both: 1/ ALSA driver may not report correct dB information. 2/ PulseAudio may not correctly mix PCM into Master since changing Master volume does nothing at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1810039 Title: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295] Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK 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/1810039/+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 1810039] Re: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1810039 Title: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295] Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK 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/1810039/+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 1810039] [NEW] Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295]
Public bug reported: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: >From the mute state, one press on volume up do graphically well but in reality >the volume is loud and noisy from the first step. And all other up steps do >not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "volume-issue.gif" https://bugs.launchpad.net/bugs/1810039/+attachment/5225699/+files/volume-issue.gif -- 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/1810039 Title: Volume noisy and loud with no level control [HDA Intel PCH / Realtek ALC295] Status in alsa-driver package in Ubuntu: New Bug description: What I expect: When I use slider volume or when I use volume up button of my laptop, I expect that the volume goes up slightly. What happens: From the mute state, one press on volume up do graphically well but in reality the volume is loud and noisy from the first step. And all other up steps do not change the volume. Doing this with `alsamixer` started show me what you can see in volume-issue.gif attached file. Indeed when I press volume up PCM volume is maxed to 100 instantly and then Speaker volume and then Master volume. In my case manually changing the PCM volume in `alsamixer` is the only way to change the actual volume of my laptop. Even changing Master volume has no effect! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jule 1680 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 29 16:04:58 2018 InstallationDate: Installed on 2018-12-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK 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/1810039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Some additional sysinfo with inxi: System:Host: mir Kernel: 4.20.0-042000-generic x86_64 bits: 64 Desktop: Gnome 3.30.1 Distro: Ubuntu 18.10 (Cosmic Cuttlefish) Machine: Type: Laptop System: ASUSTeK product: ZenBook S UX391UA v: 1.0 serial: Mobo: ASUSTeK model: UX391UA v: 1.0 serial: UEFI [Legacy]: American Megatrends v: UX391UA.301 date: 10/15/2018 BTW, ASUS released recently a new BIOS version, but it still doesn't solve our problem: https://www.asus.com/de/Laptops/ASUS- ZenBook-S-UX391UA/HelpDesk_BIOS/ -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@VanVan That's strange! To be on the safe side, I even did a fresh Ubuntu 18.10 installation and updated to the 4.20 kernel with UKUU, but I still don't have sound. Neither from the internal, nor the external speakers. I've played around with alsamixer in the terminal – without success. Can somebody confirm that they got the sound running just by installing the latest kernel (4.20) on the ASUS UX391UA (that's the model this issues is actually about)? -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 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=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+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 1810032] [NEW] package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro
Public bug reported: An error is displayed when ubuntu logs in. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Dec 28 11:29:30 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-12-28 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180817) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1810032 Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 10 Status in console-setup package in Ubuntu: New Bug description: An error is displayed when ubuntu logs in. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Dec 28 11:29:30 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-12-28 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180817) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1810032/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1810023] [NEW] cannot select candidate from the panel
Public bug reported: It happened twice, however, I didn't notice how to reproduce it. The problem happened suddenly (this time) when I am editing a commit message in VSCode. PROBLEM: See the attached ime.gif demo. When I type some pinyin the corresponding Chinese character is shown on the panel, I select any number, say "3", the character "重" should be selected and appear in the text area. However, the number 3 is entered. And after that the IME does not work anymore, until I switch back to English, then To Chinese again, from the system tray. Anyway, when this bug happens, I can only enter the first candidate of any pinyin (by hit space), but cannot select others by using numbers. REASON: I found that by deleting the folder ~/.cache/ibus and login again, this problem is gone. Further investigation show that problematic files are one (or more) of the following: xrfang@office:~/.cache/ibus/libpinyin$ ls user* user_bigram.db user.conf user_pinyin_index.bin user.binuser_phrase_index.bin GUESS: I am definitely sure that this is a bug, because it happened twice. I feel that I might inadvertently triggered some key combination so as to ruined one of the above files. And IBUS crashed when trying to load them. Since it might be hard to identify how these files are corrupted, and as they are cache only, I would suggest the IBUS author(s) investigate how to prevent crash when loading corrupted cache files. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "demo of select a character from the panel" https://bugs.launchpad.net/bugs/1810023/+attachment/5225635/+files/ime.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1810023 Title: cannot select candidate from the panel Status in ibus package in Ubuntu: New Bug description: It happened twice, however, I didn't notice how to reproduce it. The problem happened suddenly (this time) when I am editing a commit message in VSCode. PROBLEM: See the attached ime.gif demo. When I type some pinyin the corresponding Chinese character is shown on the panel, I select any number, say "3", the character "重" should be selected and appear in the text area. However, the number 3 is entered. And after that the IME does not work anymore, until I switch back to English, then To Chinese again, from the system tray. Anyway, when this bug happens, I can only enter the first candidate of any pinyin (by hit space), but cannot select others by using numbers. REASON: I found that by deleting the folder ~/.cache/ibus and login again, this problem is gone. Further investigation show that problematic files are one (or more) of the following: xrfang@office:~/.cache/ibus/libpinyin$ ls user* user_bigram.db user.conf user_pinyin_index.bin user.binuser_phrase_index.bin GUESS: I am definitely sure that this is a bug, because it happened twice. I feel that I might inadvertently triggered some key combination so as to ruined one of the above files. And IBUS crashed when trying to load them. Since it might be hard to identify how these files are corrupted, and as they are cache only, I would suggest the IBUS author(s) investigate how to prevent crash when loading corrupted cache files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1810023/+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