[Touch-packages] [Bug 1857036] Re: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container.
This also affects other non-debian/non-ubuntu distros. https://bugzilla.redhat.com/show_bug.cgi?id=1773148 ** Bug watch added: Red Hat Bugzilla #1773148 https://bugzilla.redhat.com/show_bug.cgi?id=1773148 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1857036 Title: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container. Status in sudo package in Ubuntu: Confirmed Bug description: When using `sudo --login --user USERNAME` with Ubuntu Focal currently, it will correctly operate but it will also throw the following error before continuing with the logon process: sudo: setrlimit(RLIMIT_CORE): Operation not permitted A full run of this was tested in a Focal LXD container after dropping to a root shell to reproduce (arstotzka is the host system, focal-test is the test container): teward@arstotzka:~$ lxc shell focal-test root@focal-test:~# sudo --login --user ubuntu sudo: setrlimit(RLIMIT_CORE): Operation not permitted To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. ubuntu@focal-test:~$ This appears to be similar to this issue identified on RedHat's tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1773148 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sudo 1.8.29-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 Date: Thu Dec 19 17:16:31 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/90-cloud-init-users: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1857036/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I have the same problem. My laptop is Acer Aspire VN7-592G. Internal microphone isn't detected. For external microphone the same problem is reproduced. At this moment I use usb headset and it works fine. -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
** Also affects: alsa-driver via mailto:r.mia...@gmail.com Importance: Undecided Status: New ** No longer affects: alsa-driver -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 999859] Re: [USB-Audio - MAYA44 USB, playback] volume slider problem
Okay, i'm a total linux noob but for some reason I managed to fix this. 1) edit file > gksu gedit /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common 2) search for [Element PCM] switch = mute volume = merge override-map.1 = all override-map.2 = all-left,all-right and change it into [Element PCM] switch = mute volume = merge volume-limit = 99.9 override-map.1 = all override-map.2 = all-left,all-right 3) reboot audio: > pulseaudio -k 4) put volume of maya44 at max through the terminal > alsamixer click F6, select the maya44 soundcard, put the master volume at max (using the page-up arrow), exit alsa (ctrl-c in the terminal) 5) Play Justin Bieber, and slowly fade it to mute 6) ... 7) profit! (about tree fiddy) note A: by doing this, my internal sound disappeared from the sound settings, after unplugging the sound card, internal sound still worked by running > pulseaudio -k note B: if you don't like it, just reverse the steps, everthing goes back to the way it was. note C: by executing note B, you are also reverse profit. Which means LOSS note D: note C is not desirable -- 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/999859 Title: [USB-Audio - MAYA44 USB, playback] volume slider problem Status in ALSA driver: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: The volume slider does not allow me to slightly adjust the volume. The volume is too low/barely noticable over nearly the whole slider range. When moved into the end position (max) the volume goes up dramatically in the last step. So volume adjustment is not smooth but jumping from too low to max in one step of the slider. I can adjust the volume in the software/player I use but it does not really work with the system volume adjustment. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: romy 2263 F pulseaudio /dev/snd/controlC0: romy 2263 F pulseaudio /dev/snd/controlC1: romy 2263 F pulseaudio /dev/snd/pcmC1D0p: romy 2263 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf irq 48' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,18490890,00100101' Controls : 46 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'USB'/'AUDIOTRAK MAYA44 USB at usb-:00:1a.0-1, full speed' Mixer name : 'USB Mixer' Components : 'USB0a92:0091' Controls : 6 Simple ctrls : 3 Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbefc000 irq 49' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 15 20:08:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redwood HDMI Audio [Radeon HD 5000 Series] - HD-Audio Generic Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - MAYA44 USB, playback] volume slider problem UpgradeStatus: Upgraded to precise on 2012-05-15 (0 days ago) dmi.bios.date: 04/09/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: X58 Extreme 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.30:bd04/09/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme: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. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/999859/+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 999859] Re: [USB-Audio - MAYA44 USB, playback] volume slider problem
** Also affects: alsa-driver 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/999859 Title: [USB-Audio - MAYA44 USB, playback] volume slider problem Status in ALSA driver: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: The volume slider does not allow me to slightly adjust the volume. The volume is too low/barely noticable over nearly the whole slider range. When moved into the end position (max) the volume goes up dramatically in the last step. So volume adjustment is not smooth but jumping from too low to max in one step of the slider. I can adjust the volume in the software/player I use but it does not really work with the system volume adjustment. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: romy 2263 F pulseaudio /dev/snd/controlC0: romy 2263 F pulseaudio /dev/snd/controlC1: romy 2263 F pulseaudio /dev/snd/pcmC1D0p: romy 2263 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf irq 48' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,18490890,00100101' Controls : 46 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'USB'/'AUDIOTRAK MAYA44 USB at usb-:00:1a.0-1, full speed' Mixer name : 'USB Mixer' Components : 'USB0a92:0091' Controls : 6 Simple ctrls : 3 Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbefc000 irq 49' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 15 20:08:05 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redwood HDMI Audio [Radeon HD 5000 Series] - HD-Audio Generic Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - MAYA44 USB, playback] volume slider problem UpgradeStatus: Upgraded to precise on 2012-05-15 (0 days ago) dmi.bios.date: 04/09/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: X58 Extreme 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.30:bd04/09/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme: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. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/999859/+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 1499305] [NEW] package passwd 1:4.1.5.1-1ubuntu9.1 failed to install/upgrade: cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error)
Public bug reported: no software installed from terminal or software centre ProblemType: Package DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu Sep 24 07:29:05 2015 DpkgTerminalLog: Setting up passwd (1:4.1.5.1-1ubuntu9.1) ... DuplicateSignature: package:passwd:1:4.1.5.1-1ubuntu9.1:cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) ErrorMessage: cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: shadow Title: package passwd 1:4.1.5.1-1ubuntu9.1 failed to install/upgrade: cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.passwd.conf: [inaccessible: [Errno 5] Input/output error] ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1499305 Title: package passwd 1:4.1.5.1-1ubuntu9.1 failed to install/upgrade: cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) Status in shadow package in Ubuntu: New Bug description: no software installed from terminal or software centre ProblemType: Package DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu Sep 24 07:29:05 2015 DpkgTerminalLog: Setting up passwd (1:4.1.5.1-1ubuntu9.1) ... DuplicateSignature: package:passwd:1:4.1.5.1-1ubuntu9.1:cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) ErrorMessage: cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) InstallationDate: Installed on 2015-09-23 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: shadow Title: package passwd 1:4.1.5.1-1ubuntu9.1 failed to install/upgrade: cannot compute MD5 hash for file '/etc/init/passwd.conf': failed to read (Input/output error) UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.passwd.conf: [inaccessible: [Errno 5] Input/output error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1499305/+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 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
With Chrome 40, the problem isn't properly fixed for me. HW acceleration does work, but the display/graphic session still crashes in full screen (tested with youtube html5 player), especially when you use a compiz animation (I often use the scale plugin). -- 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/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU Status in Chromium Browser: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering. In chrome://gpu/ I get: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all [...] In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting sensors limits [240G [234G[ OK ] * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri Oct 3 17:48:09 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 13:54:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1377220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : h
[Touch-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
When starting chrome(ium) with --disable-gpu-sandbox option, GPU acceleration works properly. -- 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/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU Status in “mesa” package in Ubuntu: Confirmed Bug description: When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering. In chrome://gpu/ I get: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all [...] In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting sensors limits [240G [234G[ OK ] * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri Oct 3 17:48:09 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 13:54:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1377220/+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 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
I confirm this bug also affects Ivy Bridge. But though the "LIBGL_DRI3_DISABLE" work around does enable gpu, it introduces other graphical freezes when going in full screen mode, tested in YouTube html5 player. It makes the whole graphical session unresponsive. -- 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/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU Status in “mesa” package in Ubuntu: Confirmed Bug description: When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering. In chrome://gpu/ I get: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all [...] In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting sensors limits [240G [234G[ OK ] * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri Oct 3 17:48:09 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 13:54:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1377220/+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/L
