[Touch-packages] [Bug 1830502] Re: apparmor uses excessive memory leading to oom kill
The biggest problem is that it isn't easily disabled because it is hardcoded in the script instead of being in /etc/apparmor/parser.conf. Instead of hardcoding, it would had been better to just update that conffile and let dpkg update it if the user didn't change it (which is highly likely) or on new installs. In /lib/apparmor/functions we have this: # LP: #1383858 - expr tree simplification is too slow for some # policy on 32bit ARM, so disable it for now cache_extra_args= if [ -d "$PROFILES_CACHE_VAR" ] && [ "$pdir" = "$PROFILES_VAR" ]; then cache_extra_args="-O no-expr-simplify" fi So now for machines with 2Gib of RAM and Snaps, Ubuntu 18.04 has become unusable. I know the minimum requirements are 4Gib but it did actually work fine with 2Gib before so it is a bit sad to loose that capability. My suggestion is to just revert that change and do it in parser.conf instead, so at least we have the option to easily modify it to retain some 2Gib support. Thanks a lot for considering this!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1830502 Title: apparmor uses excessive memory leading to oom kill Status in apparmor package in Ubuntu: Confirmed Bug description: When attempting to load the profile from comment #7, apparmor uses excessive amounts of memory leading to being killed by the OOM killer and thus the apparmor.service failing. Original bug description: On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk, my system was unable to finish booting and I had to go into recovery mode and remove a number of files before the system would boot. After doing so I discovered that now the apparmor.service systemd unit always fails to start. I see this in dmesg: [ 1066.975360] Out of memory: Kill process 6799 (apparmor_parser) score 796 or sacrifice child [ 1066.975364] Killed process 6799 (apparmor_parser) total-vm:15057348kB, anon-rss:15046148kB, file-rss:0kB, shmem-rss:0kB [ 1067.406595] oom_reaper: reaped process 6799 (apparmor_parser), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Whenever apparmor.service is attempted to be started by systemd, i.e. either on boot, or later with `systemctl start apparmor`. The log from journalctl doesn't show any actual issues with any profiles just this: -- Reboot -- May 25 17:00:58 systemd[1]: Starting AppArmor initialization... May 25 17:00:58 apparmor[1521]: * Starting AppArmor profiles May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 25 17:01:40 apparmor[1521]:...fail! May 25 17:01:40 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a May 25 17:01:40 systemd[1]: apparmor.service: Failed with result 'exit-code'. May 25 17:01:40 systemd[1]: Failed to start AppArmor initialization. May 25 17:04:53 systemd[1]: Starting AppArmor initialization... May 25 17:04:53 apparmor[4747]: * Starting AppArmor profiles May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd May 25 17:05:25 apparmor[4747]:...fail! May 25 17:05:25 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a May 25 17:05:25 systemd[1]: apparmor.service: Failed with result 'exit-code'. May 25 17:05:25 systemd[1]: Failed to start AppArmor initialization. I can see that apparmor profiles are active after doing this (using aa-status), but it's still troubling that apparmor runs into an issue without actually saying what the error is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1830502/+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 1383858] Re: expr-simplify optimization slows click/snap policy compilation
Hello. Can you guys take a look at this suggestion please? https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1830502/comments/18 Thanks!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click/snap policy compilation Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in click-apparmor package in Ubuntu: Fix Released Status in apparmor package in Ubuntu RTM: Fix Released Status in click-apparmor package in Ubuntu RTM: Fix Released Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. Note: the fix for bug #1385947 must be included with this fix. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+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 1852023] [NEW] Wayland doesn't work in GMA500
Public bug reported: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA TOSHIBA NB515 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP 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:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jul 1 17:43:10 2019 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze 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/1852023 Title: Wayland doesn't work in GMA500 Status in xorg package in Ubuntu: New Bug description: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ag
[Touch-packages] [Bug 1852025] [NEW] [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem
Public bug reported: Everytime I boot there is no sound. With QasMixer I am able to fix it by selecting hw:0 (HDA Intel) and increasing the second slider from bottom to top, that slider says "auriculares" in spanish which is "headphones". I am not using headphones though and I didn't found any other way of increasing that slider in the standard programs that come installed by default in Ubuntu 19.10 (and many other older releases). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luigi 1637 F pulseaudio luigi 26280 F qasmixer /dev/snd/pcmC0D0p: luigi 1637 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:38:04 2019 InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov 10 17:18:45 luigi-netbook dbus-daemon[887]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=122 pid=1140 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") nov 10 19:17:05 luigi-netbook pulseaudio[1140]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP 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:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852025 Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: Everytime I boot there is no sound. With QasMixer I am able to fix it by selecting hw:0 (HDA Intel) and increasing the second slider from bottom to top, that slider says "auriculares" in spanish which is "headphones". I am not using headphones though and I didn't found any other way of increasing that slider in the standard programs that come installed by default in Ubuntu 19.10 (and many other older releases). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luigi 1637 F pulseaudio luigi 26280 F qasmixer /dev/snd/pcmC0D0p: luigi 1637 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:38:04 2019 InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov 10 17:18:45 luigi-netbook dbus-daemon[887]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=122 pid=1140 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") nov 10 19:17:05 luigi-netbook pulseaudio[1140]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dm
[Touch-packages] [Bug 1619753] Re: systemd-fsck does not show results of rootfs filesystem check in logs or journald
But it should be persisted by default in /var/log, so there should be a unit somewhere that if the log has information then it appends it in a file and gets logrotated. That way, if a server or PC is acting strange, one could look there to see if something strange happened to the filesystem and when it happened. The log shouldn't be lost... -- 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/1619753 Title: systemd-fsck does not show results of rootfs filesystem check in logs or journald Status in initramfs-tools package in Ubuntu: Invalid Bug description: Prior to the systemd paradigm shift, Ubuntu versions provided mechanisms to be able to see the results of a filesystem check performed on the root filesystem either in boot.log in 12.04 or in mountall.log in 14.04. As of 16.04, there is no way to see the output of systemd-fsck when it is run on the root filesystem. root@ubuntu-16-04-1:~# lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 root@ubuntu-16-04-1:~# apt-cache policy systemd systemd: Installed: 229-4ubuntu7 Candidate: 229-4ubuntu7 Version table: *** 229-4ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Steps to reproduce: 1) Force fsck on next reboot by altering linux boot commandline: Edit /etc/default/grub and add "fsck.mode=force" to the GRUB_CMDLINE_LINUX variable. If you also want to force repair behavior, also add "fsck.repair=yes" to the same variable. # example: GRUB_CMDLINE_LINUX="fsck.mode=force fsck.repair=yes" Once the changes have been made, run "sudo update-grub" to update the boot info, then reboot. 2) After boot, journalctl does not report any filesystem repair details for the root fs, only for secondary filesystems such as /boot or others designated in /etc/fstab. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1619753/+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 1340905] [NEW] Acer Aspire E1-570-6889 brightness control not working
Public bug reported: Cannot adjust the brightness in a Acer Aspire E1-570-6889. The brightness key works and the brightness configuracion in the system configuration allows to adjust the brightness but the display does nothing, it is always at full brightness. I may try some things esporadically since it is not my laptop, but I may take a long time to try them :-(. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jul 11 15:48:22 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0835] InstallationDate: Installed on 2014-07-07 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire E1-570 ProcEnviron: LANGUAGE=es_UY:es TERM=xterm PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=951be93c-e59d-461a-b0e6-d7e48153b4ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_CX dmi.board.vendor: Acer dmi.board.version: V2.06 dmi.chassis.asset.tag: Acer Asset Tag String dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnAcer:pnAspireE1-570:pvrV2.06:rvnAcer:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06: dmi.product.name: Aspire E1-570 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jul 11 15:25:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18668 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1340905 Title: Acer Aspire E1-570-6889 brightness control not working Status in “xorg” package in Ubuntu: New Bug description: Cannot adjust the brightness in a Acer Aspire E1-570-6889. The brightness key works and the brightness configuracion in the system configuration allows to adjust the brightness but the display does nothing, it is always at full brightness. I may try some things esporadically since it is not my laptop, but I may take a long time to try them :-(. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jul 11 15:48:22 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0835] InstallationDate: Installed on 2014-07-07 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire E1-570 ProcE
[Touch-packages] [Bug 729831] Re: Output controls are not switched to headset
The same thing happens with USB headsets, so, it seems related to having multiple output devices dynamically connected. -- 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/729831 Title: Output controls are not switched to headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio After my bluetooth headset is connected to the system, the sound output is switched from the speakers to the headset, but the volume control does not set the volume of the headset. I have to go to "Sound Preferences... -> Output", then choose my headset here. Then I can control the volume. Also, after selecting a new output device, the "Output volume" slider changes its position, but the volume remains the same. I have to either click on the slider or use the volume keys on the keyboard to actually set the volume. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xvro 2336 F pulseaudio /dev/snd/pcmC1D0c: xvro 2336 F...m pulseaudio /dev/snd/controlC0: xvro 2336 F pulseaudio /dev/snd/pcmC0D0p: xvro 2336 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Date: Sat Mar 5 21:36:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 04/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4B dmi.board.name: EX38-DQ6 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX38-DQ6 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 1608287] [NEW] No display output on Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+ after upgrading to 16.04 from 14.04
Public bug reported: Everything was fine on this PC with 14.04, but it doesn't display anything on 16.04. It doesn't hang because I am able to press CTRL+ALT+F1 and push the power button and it shutdowns normally. Booting with "nomodeset" works (with slow software rendering of course). Upgraded the BIOS from 2.5 to 2.8 and using all the default settings: nothing. Enabled xenail-proposed-updates and installed everything from there: nothing. Tried some BIOS tweaks but didn't fix it either. Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+. I have access to this PC (my father PC) once a week to try things. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 31 17:32:13 2016 DistUpgraded: 2016-07-29 13:33:38,576 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Richland [Radeon HD 8470D] [1849:9996] InstallationDate: Installed on 2014-11-16 (623 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=es_UY:es TERM=xterm-256color PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=621d22e8-9497-4dd2-b0d7-7303344fcc72 ro quiet splash vt.handoff=7 nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-07-29 (2 days ago) dmi.bios.date: 01/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: FM2A58M-VG3+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd01/11/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A58M-VG3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jul 31 17:19:30 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1608287 Title: No display output on Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+ after upgrading to 16.04 from 14.04 Status in xorg package in Ubuntu: New Bug description: Everything was fine on this PC with 14.04, but it doesn't display anything on 16.04. It doesn't hang because I am able to press CTRL+ALT+F1 and push the power button and it shutdowns normally. Booting with "nomodeset" works (with slow software rendering of course). Upgraded the BIOS from 2.5 to 2.8 and using all the default settings: nothing. Enabled xenail-proposed-updates and installed everything from there: nothing. Tried some BIOS tweaks but didn't fix it either. Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+. I have access to this PC (my father PC) once a
[Touch-packages] [Bug 1608287] Re: No display output on Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+ after upgrading to 16.04 from 14.04
In the attached XorgLogOld.txt you can see the log when trying without "nomodeset", it detects the monitor correctly and the X server doesn't hang... -- 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/1608287 Title: No display output on Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+ after upgrading to 16.04 from 14.04 Status in xorg package in Ubuntu: New Bug description: Everything was fine on this PC with 14.04, but it doesn't display anything on 16.04. It doesn't hang because I am able to press CTRL+ALT+F1 and push the power button and it shutdowns normally. Booting with "nomodeset" works (with slow software rendering of course). Upgraded the BIOS from 2.5 to 2.8 and using all the default settings: nothing. Enabled xenail-proposed-updates and installed everything from there: nothing. Tried some BIOS tweaks but didn't fix it either. Radeon HD 8470D AMD A6-6400K AsRock FM2A58M-VG3+. I have access to this PC (my father PC) once a week to try things. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 31 17:32:13 2016 DistUpgraded: 2016-07-29 13:33:38,576 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Richland [Radeon HD 8470D] [1849:9996] InstallationDate: Installed on 2014-11-16 (623 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=es_UY:es TERM=xterm-256color PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=621d22e8-9497-4dd2-b0d7-7303344fcc72 ro quiet splash vt.handoff=7 nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-07-29 (2 days ago) dmi.bios.date: 01/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: FM2A58M-VG3+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd01/11/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A58M-VG3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jul 31 17:19:30 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1608287/+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
