[Touch-packages] [Bug 2051573] [NEW] [HDA-Intel - HD-Audio Generic, playback] No sound at all
Public bug reported: Internal speakers - no sound Headphones (jack) no sound HDMI sound works while connected to external monitor, there are some minor quality issues Ubuntu 22.04 kernel 6.5.0-15-generic on Huawei Matebook 14D ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:39:17 2024 InstallationDate: Installed on 2023-07-13 (200 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: acp - acp Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 1.8 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.08 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXXW-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHUAWEI:bvr1.08:bd01/11/2023:br1.8:efr1.8:svnHUAWEI:pnKLVL-WXXW:pvrM1010:rvnHUAWEI:rnKLVL-WXXW-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXXW dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2051573 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers - no sound Headphones (jack) no sound HDMI sound works while connected to external monitor, there are some minor quality issues Ubuntu 22.04 kernel 6.5.0-15-generic on Huawei Matebook 14D ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 29 17:39:17 2024 InstallationDate: Installed on 2023-07-13 (200 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: acp - acp Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.release: 1.8 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.08 dmi.board.asset.tag: N/A dmi.board.name: KLVL-WXXW-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnHUAWEI:bvr1.08:bd01/11/2023:br1.8:efr1.8:svnHUAWEI:pnKLVL-WXXW:pvrM1010:rvnHUAWEI:rnKLVL-WXXW-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook 14 dmi.product.name: KLVL-WXXW dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051573/+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 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"
And here we go again... - also with qdbusviewer, and also on 18.04 Previous workaround stopped working. After some digging it looks that qtchooser is looking into wrong Qt dir (qt4 instead of qt5) Some other people reported that apt install qt5-default may help - but I did not check this What worked was editing /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf and adding first line so it looks like this: /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf /usr/lib/qt5/bin /usr/lib/x86_64-linux-gnu/qt4/bin /usr/lib/x86_64-linux-gnu EOF -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1251178 Title: qdbus and qdbusviewer crash with "No such file or directory" Status in qt4-x11 package in Ubuntu: Confirmed Status in qtchooser package in Ubuntu: Confirmed Bug description: Release: Ubuntu 13.10 (32-bit) Package versions: qtdbus 4:4.8.4+dfsg-0ubuntu18 qtchooser 26-3ubuntu2 Expected behavior: The `qdbus` program runs, as does the related program `qdbusviewer`. Actual behavior: If I run the `qdbus` program, it always crashes: user@host:~$ qdbus --help qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file or directory The `qdbus` executable is actually: user@host:~$ ls --full-time $(which qdbus) lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus -> qtchooser Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to work if I invoke it directly. There's a `qdbus-qt5` package in the universe repository. It was not pulled in as a dependency, but manually installing it fixes the issue. Therefore it's either a packaging error or a bug in qtchooser. A similar thing happens if I run `qdbusviewer`: user@host:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No such file or directory except that installing `qdbus-qt5` doesn't fix the issue. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: qdbus 4:4.8.4+dfsg-0ubuntu18 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 14 09:34:24 2013 MarkForUpload: True SourcePackage: qt4-x11 UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+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 621430] Re: [VIA VT1708S] Playback problem "Sound Skipping"
I encounter this bug on Ubuntu 19.10, both using internal sound card and
external Behringer UM2
Fixable by changing
load-module module-udev-detect
to
load-module module-udev-detect tshed=0
in file
/etc/pulse/default.pa
** Changed in: alsa-driver (Ubuntu)
Status: Expired => Confirmed
--
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/621430
Title:
[VIA VT1708S] Playback problem "Sound Skipping"
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
I am using the kernel backport from Maverick to Lucid. The summary of
this problem is that at seemingly random times the sound skips almost
like it does not have sufficient hardware to play it, which also
results in totem and flash video skipping. It corrects itself, however
does happen again at random times. I took debug information for this
report after such an occurrence.
Symptoms:
1.) The sound card pops and crackles during log in, and the log-in noise is
delayed.
2.) After login the sound functions normally and seems to have good latency.
3.) At random times the sound skips, and takes video playback with it,
however it does sort itself out.
Steps to recreate:
None, I am assuming anyone with this sound card would have this issue. My
hardware is a stock Asus k50ij laptop.
Notes:
Fedora 13 has a lot of problems with volume and playback with this chipset,
it seems Ubuntu does not. I also plan to do upstream testing on a mainline
kernel, though I have not done so yet.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-17.23~lucid1-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 1/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: virgil 1404 F pulseaudio
/dev/snd/pcmC0D0p: virgil 1404 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 45'
Mixer name : 'VIA VT1708S'
Components : 'HDA:11060397,1043,0010'
Controls : 20
Simple ctrls : 13
Date: Fri Aug 20 17:49:06 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [VIA VT1708S] Playback problem
dmi.bios.date: 12/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IJ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr217:bd12/04/2009:svnASUSTeKComputerInc.:pnK50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnK50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K50IJ
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/621430/+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 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"
Because this is top post being shown in Google search for problems with qdbusviewer and they persist also on 18.04 here is the solution: 1. Find an error message. In my case (even after installing default): qdbusviewer: could not exec '/usr/lib/qt5/bin/qdbusviewer': No such file or directory 2. Find in which package is file being reported as missing: $ apt-file search /usr/lib/qt5/bin/qdbusviewer qttools5-dev-tools: /usr/lib/qt5/bin/qdbusviewer 3. Install found package: $ sudo apt install qttools5-dev-tools Voila! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1251178 Title: qdbus and qdbusviewer crash with "No such file or directory" Status in qt4-x11 package in Ubuntu: Confirmed Status in qtchooser package in Ubuntu: Confirmed Bug description: Release: Ubuntu 13.10 (32-bit) Package versions: qtdbus 4:4.8.4+dfsg-0ubuntu18 qtchooser 26-3ubuntu2 Expected behavior: The `qdbus` program runs, as does the related program `qdbusviewer`. Actual behavior: If I run the `qdbus` program, it always crashes: user@host:~$ qdbus --help qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file or directory The `qdbus` executable is actually: user@host:~$ ls --full-time $(which qdbus) lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus -> qtchooser Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to work if I invoke it directly. There's a `qdbus-qt5` package in the universe repository. It was not pulled in as a dependency, but manually installing it fixes the issue. Therefore it's either a packaging error or a bug in qtchooser. A similar thing happens if I run `qdbusviewer`: user@host:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No such file or directory except that installing `qdbus-qt5` doesn't fix the issue. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: qdbus 4:4.8.4+dfsg-0ubuntu18 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 14 09:34:24 2013 MarkForUpload: True SourcePackage: qt4-x11 UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1251178/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
Following instructions provided by @cjjefcoat, I managed to get kernel -116 running. It turns out that just removing the "ppa:ubuntu-toolchain-r/test" ppa and reinstalling the gcc-4.8 wasn't sufficient to get it downgraded to "gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4". Anyway, *purging* the ppa did the trick. Thanks! -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
I can use my Ubuntu 14.04.05 with kernel 4.4.0-112-generic normally, but when it comes to booting with 4.4.0-116-generic Nvidia drivers don't work. My gcc-4.8 version is "gcc (Ubuntu 4.8.5-2ubuntu1~14.04.1) 4.8.5" and gcc-5 version is "gcc-5 (Ubuntu 5.4.1-2ubuntu1~14.04) 5.4.1 20160904". I tried reinstalling -116 kernel, but it didn't work and so didn't work rebuilding the drivers with "dkms remove"/"dkms install". I can't get "retpoline" to appear in modinfo output for nvidia-390 for "kernel 4.4.0-116-generic", no matter on which kernel version and with which version of gcc I try to recompile them. -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
Re: [Touch-packages] [Bug 1718927] Re: No hdmi sound after suspend/resume on 16.04
Hi Daniel, I have Ubuntu Gnome 16.04.3. After resuming I can change device in settings but it gives no result - still silence. The sound is only on the speakers. The only way to restore sound in HDMI is to reboot. But I am not pretty sure if the problem relates to pulse audio. I reinstalled the system and did not install pulseaudio at all. Still the same. After resuming there is no sound in HDMI. Regards Jacek Wróbel SAC, Kielecka 33, Święta Katarzyna, 26-010 Bodzentyn 2017-09-25 21:56 GMT+02:00 Daniel van Vugt <daniel.van.v...@canonical.com>: > At a guess, your system is probably reverting back to the default audio > device on resume. > > What does it look like in Settings after resuming? Can you change the > audio playback device back to HDMI by hand? > > ** Changed in: pulseaudio (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1718927 > > Title: > No hdmi sound after suspend/resume on 16.04 > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works > perfectly, but when I suspend computer and resume it there is no sound > via HDMI in TV. However sound via built in speakers works fine. The > only thing I can do to restore sound is to reboot the machine. Similar > problem was discussed in following thread > https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I > tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no > solution. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+ > bug/1718927/+subscriptions > -- 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/1718927 Title: No hdmi sound after suspend/resume on 16.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1718927] [NEW] No hdmi sound after suspend/resume on 16.04
Public bug reported: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. ** 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1718927 Title: No hdmi sound after suspend/resume on 16.04 Status in pulseaudio package in Ubuntu: New Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr
** Tags added: canonical-bootstack -- 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/1667016 Title: tcpdump in lxd container: apparmor blocks writing to stdout/stderr Status in apparmor package in Ubuntu: Confirmed Bug description: [ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0] If you ssh into an lxd container as a normal user, and inside that container run "sudo tcpdump", the tcpdump process is blocked from writing to stdout/stderr. This appears to be due to apparmor: disabling apparmor for tcpdump makes the problem go away. ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/ Note: this is a different bug from #1641236. In that bug, the user did "lxc exec bash" to get a shell in the container; the stdout fd was being passed from the outer host to the container. But in this case, the pty is being created entirely inside the container by sshd. Details copied from https://github.com/lxc/lxd/issues/2930 # Steps to reproduce 1. Create two Ubuntu 16.04 lxd containers, one privileged, one not. 2. ssh into each one, and then use `sudo -s` to get root. (Do not use `lxc exec` because of issue #1641236) 3. Inside one run `tcpdump -i eth0 -nn not tcp port 22`, and ping from the other. tcpdump in the privileged container works just fine. tcpdump in the unprivileged container does not show any output. But if I run strace on it I see errors attempting to access stdout and stderr: ~~~ ioctl(1, TCGETS, 0x7fff97c8d680)= -1 ENOTTY (Inappropriate ioctl for device) ... write(2, "tcpdump: verbose output suppress"..., 75) = -1 EACCES (Permission denied) write(2, "listening on eth0, link-type EN1"..., 74) = -1 EACCES (Permission denied) ~~~ This is very weird. Even more weird: the following command *does* capture packets: ~~~ tcpdump -i eth0 -nn -w foo.pcap ~~~ The file foo.pcap grows. This proves it's nothing to do with network capture perms. But the following command shows no output: ~~~ tcpdump -r foo.pcap -nn ~~~ And again it's because it can't write to stdout: ~~~ fstat(1, 0x7ffe2fb5eb10)= -1 EACCES (Permission denied) read(3, "", 4096) = 0 write(1, "14:34:30.618180 IP6 fe80::c609:6"..., 1740) = -1 EACCES (Permission denied) ~~~ I had originally thought this was to do with capabilities. But if I run `capsh --print` inside both containers, they both have `cap_net_raw` and `cap_net_admin`. In fact, the unprivileged container has two additional capabilities! (`cap_mac_override` and `cap_mac_admin`) So now I suspect that apparmor is at fault. dmesg dmesg output generated by the following steps: * start tcpdump * wait 5 seconds * send 1 ping from other side * wait 5 seconds * stop tcpdump ~~~ [429020.685987] audit: type=1400 audit(1487774339.708:3597): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686000] audit: type=1400 audit(1487774339.708:3598): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686013] audit: type=1400 audit(1487774339.708:3599): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686022] audit: type=1400 audit(1487774339.708:3600): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.716725] device eth0 entered promiscuous mode [429020.741308] audit: type=1400 audit(1487774339.764:3601): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429020.741330] audit: type=1400 audit(1487774339.764:3602): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429021.716785] audit: type=1400 audit(1487774340.740:3603): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_"
[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
Is there any workaround available other than switching to privileged containers? -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in Snap Layer: New Status in snapd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Artful: Fix Released Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/layer-snap/+bug/1709536/+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 1611078] Re: Support snaps inside of lxd containers
I am still unable to run snaps inside lxd containers. I've just tested on an Ubuntu 16.04.3 LTS host: $ uname -a Linux hp 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lxc version 2.0.10 $ lxc launch ubuntu:16.04 test Creating test Starting test $ lxc exec test -- apt update $ lxc exec test -- apt dist-upgrade -y $ lxc exec test -- apt install squashfuse -y $ lxc exec test -- snap install hello error: cannot communicate with server: Post http://localhost/v2/snaps/hello: dial unix /run/snapd.socket: connect: connection refused $ lxc exec test -- systemctl status snapd ● snapd.service - Snappy daemon Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Wed 2017-08-30 22:39:39 UTC; 35s ago Main PID: 2017 (code=exited, status=201/NICE) Aug 30 22:39:39 test systemd[1]: snapd.service: Unit entered failed state. Aug 30 22:39:39 test systemd[1]: snapd.service: Failed with result 'exit-code'. Aug 30 22:39:39 test systemd[1]: snapd.service: Service hold-off time over, scheduling restart. Aug 30 22:39:39 test systemd[1]: Stopped Snappy daemon. Aug 30 22:39:39 test systemd[1]: snapd.service: Start request repeated too quickly. Aug 30 22:39:39 test systemd[1]: Failed to start Snappy daemon. $ lxc exec test -- snap version snap2.26.10 snapd unavailable series - $ -- 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/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in lxd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1682499] Re: disable dnssec
This helped me only partially - I still have issues with DNS lookup. It seems that the systemd-resolved is broken from the very idea. After solving DNSSEC problem, I see now a switching problem - if one DNS does not respond, resolved switches to another one, which may be a local DNS not serving all the information, however it responds RELIABLY with "REFUSED" for majority of queries! Thus, resolved is stuck with this "reliable" DNS, refusing almost all queries until reboot (or networking reload). There are so many bugs filled about resolved that somebody should gather them in one place and do something. Moreover, tracing problems is not easy - they are intermittent, depending on current server load. For some people in fixed setup bug may be nonexistent; when travelling across well-configured, simple and non- overloaded networks everything is OK. Then, at some hour, some connection - I start having to reload network every time I start reading mail. For now many people are switching to alternative resolver - e.g. "unbound"; what is going on with resolved looks like sabotage. -- 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/1682499 Title: disable dnssec Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * dnssec functionality in systemd-resolved prevents network access in certain intra and extra net cases, due to failure to correctly validate dnssec entries. As a work-around we should disable dnssec by default. [Test Case] * Validate systemd-resolved is compiled with --with-default-dnssec=no * Validate that systemd-resolve --status says that DNSSEC setting is no $ systemd-resolve --status good output: ... DNSSEC setting: no DNSSEC supported: no ... bad output: ... DNSSEC setting: allow-downgrade DNSSEC supported: yes ... [Regression Potential] * People who expect DNSSEC to be available by default will need to re-enable it by modifying systemd-resolve configuration file [Other Info] * See duplicate bugs and other bug reports in systemd for scenarios of DNS resolution failures when DNSSEC is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+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 1654918] Re: No Internet access with default of Automatic (DHCP)
Regarding my previous post (#24)... Seems that everything is back to abnormal. After logging out and re- logging again bug was back. This time soft disconnecting and reconnecting network (from NManager) helped to regain access to network, but this was not always the remedy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) Status in Linux: New Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh 17.04 install, wireless router connects without any issue but there is no internet connection/access. This continues thru disconnecting, reconnecting, rebooting ect, Nothing.. If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & manually add Google DNS nameservers: then internet is enabled. screen attached Note this also affects ethernet, not just wireless Hardware is: description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:08:00.0 logical name: wlp8s0 version: 73 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 link=ye s multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:c240-c2401fff To note: this hardware works perfectly in 14.04 > 16.04 Add. note; issue doesn't arise with 4.11.x kernel ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 8 22:08:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108) IpRoute: default via 192.168.1.1 dev wlp8s0 proto static metric 600 169.254.0.0/16 dev wlp8s0 scope link metric 1000 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp8s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 06F21A fb815a75-4091-455e-b73d-2c1f2d97220f /org/freedesktop/NetworkManager/ActiveConnection/0 enp7s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1654918/+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 1654918] Re: No Internet access with default of Automatic (DHCP)
Ubuntu 17.04 on a Dell E6530, fresh install with copying of some networkmanager setup in /etc/ from good old Ubuntu 16.04.01 LTS and using the same home partition. My version of this bug is really miraculous. It was here for a week, today disappeared. For a week I had problems with ONE of the four locations where I connect to the net: - home-wifi (OK) - home-cable (OK) - work-cable (BAD) - work-wifi (OK). Problems only with 17.04, 16.04 working flawlessly. Problem was repeatable - nslookup working until I started firefox. Firefox showing Google home page ONCE, then all requests showing "unavailable", even reloading the home page. Also any later nslookup failing with "REFUSED". Two days ago I upgraded following to "zesty-proposed", but it did NOT help for yesterday. Maybe it needed time Upgraded the following packages: libnss-resolve (232-21ubuntu2) to 232-21ubuntu3 libpam-systemd (232-21ubuntu2) to 232-21ubuntu3 libsystemd0 (232-21ubuntu2) to 232-21ubuntu3 libsystemd0:i386 (232-21ubuntu2) to 232-21ubuntu3 libudev1 (232-21ubuntu2) to 232-21ubuntu3 systemd (232-21ubuntu2) to 232-21ubuntu3 systemd-sysv (232-21ubuntu2) to 232-21ubuntu3 udev (232-21ubuntu2) to 232-21ubuntu3 Maybe today (Sat) my work net services are less/more overloaded, so DNS query timing is different? I will see again on Mon. Anyway, strange - it seems that some timing or some combination of circumstances break the local DNS system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1654918 Title: No Internet access with default of Automatic (DHCP) Status in Linux: New Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh 17.04 install, wireless router connects without any issue but there is no internet connection/access. This continues thru disconnecting, reconnecting, rebooting ect, Nothing.. If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & manually add Google DNS nameservers: then internet is enabled. screen attached Note this also affects ethernet, not just wireless Hardware is: description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@:08:00.0 logical name: wlp8s0 version: 73 serial: width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 link=ye s multicast=yes wireless=IEEE 802.11 resources: irq:32 memory:c240-c2401fff To note: this hardware works perfectly in 14.04 > 16.04 Add. note; issue doesn't arise with 4.11.x kernel ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.2-2ubuntu4 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 8 22:08:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108) IpRoute: default via 192.168.1.1 dev wlp8s0 proto static metric 600 169.254.0.0/16 dev wlp8s0 scope link metric 1000 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp8s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 06F21A fb815a75-4091-455e-b73d-2c1f2d97220f /org/freedesktop/NetworkManager/ActiveConnection/0 enp7s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1654918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1027392] Re: Apport refuses to acknowledge 'Ignore future problems of this type' when ticked
I am on 16.04.1 LTS, x86_64, apport version 2.20.1-0ubuntu2.5, and the bug is still here. I have an unresolvable problem with hp printer, appearing only when I forget to switch printer on, and I want to ignore this forever. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1027392 Title: Apport refuses to acknowledge 'Ignore future problems of this type' when ticked Status in apport package in Ubuntu: Confirmed Bug description: Hello, I have a very annoying bug with apport. Every time at a random occasion when using Ubuntu, apport comes up with an annoying error that a system problem has been detected (something to do with colord). Now although there is nothing wrong with detecting an error with a system service - this is getting annoying. Apport refuses to acknowledge the option of 'Ignore future problems of this type'. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Sat Jul 21 12:13:14 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1027392/+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 1646168] [NEW] hadoop crash on ubuntu 16.04
Public bug reported: I'm trying to run custom installed hadoop 2.7.3 on ubuntu 16.04. When I run a map reduce job I'm being logged out (this does not happen always). I've looked at https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499 and https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026. I confirmed that I have procps - 2:3.3.10-4ubuntu2.2 installed, yet the bug still persists. ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1646168 Title: hadoop crash on ubuntu 16.04 Status in procps package in Ubuntu: New Bug description: I'm trying to run custom installed hadoop 2.7.3 on ubuntu 16.04. When I run a map reduce job I'm being logged out (this does not happen always). I've looked at https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499 and https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026. I confirmed that I have procps - 2:3.3.10-4ubuntu2.2 installed, yet the bug still persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1646168/+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 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group
*** This bug is a duplicate of bug 1637026 ***
https://bugs.launchpad.net/bugs/1637026
I still get this bug on 16.04 LTS after updating my system. I've looked
at https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026 and
confirmed that I have procps - 2:3.3.10-4ubuntu2.2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1610499
Title:
hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process
group
Status in procps package in Ubuntu:
Confirmed
Bug description:
when i run hadoop in ubuntu 16.04, ssh will exit, all process which
belong to hadoop user will be killed ,through debug ,i found the
/bin/kill in ubuntu16.04 has a bug , it has bug in killing process
group .
Ubuntu version is:
Description:Ubuntu 16.04.1 LTS
Release:16.04
(1)The way to repeat this bug
It is easy to repeat this bug , run “/bin/kill -15 -12345” or any like
“/bin/kill -15 -1” in ubuntu16.04 , it will kill all the process .
(2)Cause analysis
The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 , when I run
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,
-1 mean it will kill all the process .
(3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
(long)('0' - optopt) " is not right .
static void __attribute__ ((__noreturn__)) kill_main(int argc, char
**argv)
{
case '?':
if (!isdigit(optopt)) {
xwarnx(_("invalid argument %c"), optopt);
kill_usage(stderr);
} else {
/* Special case for signal digit negative
* PIDs */
pid = (long)('0' - optopt);
if (kill((pid_t)pid, signo) != 0)
exitvalue = EXIT_FAILURE;
exit(exitvalue);
}
loop=0;
}
(4) the cause
sometimes when the resource is tight or a hadoop container lost connection
in sometime, the nodemanager will kill this container , it send a signal to
kill this jvm process ,it is a normal behavior for hadoop to kill a task and
then reexecute this task. but with this kill bug ,it kill all the process
belong to a hadoop user .
(5) The way to workaround
I copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to
solve their bug,but i don't know how to contact them .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499/+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 1207831] Re: jackd 2 64 bit does not correclty handle 32 bit clients
Thanks QkiZ! Version from KXStudio repositories works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1207831 Title: jackd 2 64 bit does not correclty handle 32 bit clients Status in jackd2 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 12.04.2 LTS Release:12.04 Launch 64 bit jackd2 binary on a 64bit install. launch a 32bit jack client. The jackd2 server reports an invalid / incorrect value to the jack_get_sample_rate call, and also the client name reported by jack_lsp is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1207831/+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 1458169] [NEW] package apport 2.17.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: instalowałem arduino ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportLog: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashReports: 600:0:118:277815:2015-05-23 14:40:30.697401285 +0200:2015-05-23 14:40:31.697401285 +0200:/var/crash/apport.0.crash Date: Sat May 23 14:40:31 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-20 (3 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1458169 Title: package apport 2.17.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: instalowałem arduino ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportLog: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashReports: 600:0:118:277815:2015-05-23 14:40:30.697401285 +0200:2015-05-23 14:40:31.697401285 +0200:/var/crash/apport.0.crash Date: Sat May 23 14:40:31 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-20 (3 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1458169/+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 1449282] Re: lightdm tcp listen requires additional configuration
** Description changed: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver-command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the xserver-allow-tcp=true is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) - ### i haven't /etc/lightdm/lightdm.conf when i tried to create it withe the lines above it was worse my system didin't start. + after a few experiment i have found something what works: + i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf + + before it was: + [SeatDefaults] + # Dump core + xserver-command=X -core + + now: + [SeatDefaults] + # Dump core + xserver-command=X -core + xserver-allow-tcp=true + + and it works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: lightdm tcp listen requires additional configuration Status in lightdm package in Ubuntu: New Bug description: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver- command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the xserver-allow-tcp=true is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) ### i haven't /etc/lightdm/lightdm.conf when i tried to create it withe the lines above it was worse my system didin't start. after a few experiment i have found something what works: i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf before it was: [SeatDefaults] # Dump core xserver-command=X -core now: [SeatDefaults] # Dump core xserver-command=X -core xserver-allow-tcp=true and it works! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1449282/+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 1449282] Re: lightdm tcp listen requires additional configuration
** Description changed: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver-command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the xserver-allow-tcp=true is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) ### i haven't /etc/lightdm/lightdm.conf - when i tried to create it withe the lines above it was worse my system didin't start. - after a few experiment i have found something what works: + when i tried to create it and write the lines above it was worse, my system didin't start. + after a few experiment i have found something that works: i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf before it was: [SeatDefaults] # Dump core xserver-command=X -core now: [SeatDefaults] # Dump core - xserver-command=X -core + xserver-command=X -core xserver-allow-tcp=true and it works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: lightdm tcp listen requires additional configuration Status in lightdm package in Ubuntu: New Bug description: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver- command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the xserver-allow-tcp=true is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) ### i haven't /etc/lightdm/lightdm.conf when i tried to create it and write the lines above it was worse, my system didin't start. after a few experiment i have found something that works: i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf before it was: [SeatDefaults] # Dump core xserver-command=X -core now: [SeatDefaults] # Dump core xserver-command=X -core xserver-allow-tcp=true and it works! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1449282/+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 1449282] Re: lightdm tcp listen requires additional configuration
** Description changed: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver-command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the xserver-allow-tcp=true is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmConfig: - [SeatDefaults] - xserver-command=X -core -listen tcp - xserver-allow-tcp=true + [SeatDefaults] + xserver-command=X -core -listen tcp + xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) + + + ### + i haven't /etc/lightdm/lightdm.conf + when i tried to create it withe the lines above it was worse my system didin't start. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: lightdm tcp listen requires additional configuration Status in lightdm package in Ubuntu: New Bug description: In order to enable X11 forwarding from an external host you must explicitly set the Xserver to listen by overriding the xserver- command. Previously you could set the xserver-allow-tcp=true and it would do this automatically. I would have expected this change in behaviour to show up in README.Debian.gz but since it did not, perhaps the functionality of the xserver-allow-tcp=true is not working as expected. Below shows my before (no TCP listener on 6000) and after (TCP listener on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade. Before (14.10): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-allow-tcp=true After (15.04): ~$ cat /etc/lightdm/lightdm.conf [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 27 17:33:26 2015 InstallationDate: Installed on 2014-12-18 (130 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmConfig: [SeatDefaults] xserver-command=X -core -listen tcp xserver-allow-tcp=true SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago) ### i haven't /etc/lightdm/lightdm.conf when i tried to create it withe the lines above it was worse my system didin't start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1449282/+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 1274613] Re: module-bluetooth-discover does not load on login
update: well... the fix with loading module-bluetooth-discover, as last module - works... just sometimes... I added to startup: pactl list modules | grep -q bluetooth-discover || pactl load-module module-bluetooth-discover -- 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/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+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 1274613] Re: module-bluetooth-discover does not load on login
I fixed the issue simply by moving part: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif ...to the end of file (/etc/pulse/default.pa). Hope it's working for you too. :) -- 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/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+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 1401434] Re: Desktop is distorted after update to 331.113
I have the same bug with driver 331.113 on Lenovo T530 - when I switch into 2 monitors (one monitor is built-in and second is external) - icons and dialogs are distorted-Not OK. When I switch the same picture on both monitors picture is OK. When I use only built-in laptop monitor picture is also OK. -- 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/1401434 Title: Desktop is distorted after update to 331.113 Status in xorg package in Ubuntu: Confirmed Bug description: After upgrading to 331.113 I have experienced distorted desktop. I have also experienced the same problem after trying to upgrade to 14.10 and that's why I've reverted to backup of 14.04. I is quite strange. Unity controls are ok. I.e. Dash and panel on top look ok. But desktop itself and application windows are stretched to multi-monitor setup. If I arrange monitors side by side, desktop and applications are distorted horizontally. If I arrange them top to bottom, desktop is distorted vertically. It is interesting, that even screenshot is taken as is, i.e. showing distortion. On my current setup I have Dash on both (or three) screens and top panel repeating. In the screenshot with distortion, however, there's only one Dash and top panel is not visible (only line seen) on laptop screen. Mouse cursor is ok, but it is impossible to point to correct location on desktop or application window: some hit and miss involved. I am using Nvidia Optimus with nvidia-prime and lightdm for dual or three monitor setup (with docking station), laptop screen running on Intel card. I suppose this might be simply old configuration files or some package version, that is not compatible with 331.113. I've reverted to 331.38 and everything's ok. Note, that upgrading to 14.10 had exactly the same effect. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.14.1-031401-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: [core,compiztoolbox,mousepoll,vpswitch,imgpng] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 11 10:34:04 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d1] NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d1] InstallationDate: Installed on 2014-04-18 (236 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 4282A72 ProcKernelCmdLine: root=UUID=a7ac0cbe-9ae3-433b-8b76-d00c20786809 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET58WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4282A72 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET58WW(1.38):bd07/06/2012:svnLENOVO:pn4282A72:pvrThinkPadW520:rvnLENOVO:rn4282A72:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4282A72 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Dec 11 10:14:18
[Touch-packages] [Bug 1401084] [NEW] Missing rules in php5 abstraction
Public bug reported: I am using apache mod_apparmor with a wordpress blog. In my rules I have: #include abstractions/php5 But this did not allow all access that was needed: apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=k denied_mask=k fsuid=33 ouid=0 apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=wk denied_mask=wk fsuid=33 ouid=0 This access seems to be needed by opcache module, I found some info about it here: https://lists.ubuntu.com/archives/apparmor/2014-June/005879.html Ubuntu 14.04.1 apparmor 2.8.95~2430-0ubuntu5.1 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/1401084 Title: Missing rules in php5 abstraction Status in apparmor package in Ubuntu: New Bug description: I am using apache mod_apparmor with a wordpress blog. In my rules I have: #include abstractions/php5 But this did not allow all access that was needed: apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=k denied_mask=k fsuid=33 ouid=0 apparmor=DENIED operation=file_lock profile=/usr/sbin/apache2//myvhost.example.com name=/tmp/.ZendSem.Y5Ghmr pid=21874 comm=apache2 requested_mask=wk denied_mask=wk fsuid=33 ouid=0 This access seems to be needed by opcache module, I found some info about it here: https://lists.ubuntu.com/archives/apparmor/2014-June/005879.html Ubuntu 14.04.1 apparmor 2.8.95~2430-0ubuntu5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1401084/+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 1162408] Re: little horizontal black lines sporadically appear
I have this on Trusty, on HP Folio 9670m (intel graphics). -- 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/1162408 Title: little horizontal black lines sporadically appear Status in “xorg” package in Ubuntu: Incomplete Bug description: Some little horizontal black lines sometimes appear on the Ubuntu desktop. They disappear quickly, and there seems no obvious way to force the event to occur predictably. The problem occurs with libgl1-mesa-dri-experimental but, unless I'm mistaken, occurred also with the nonexperimental branch. Furthermore, I'm running Ubuntu Classic and was not using 3d effects when the problem occurred (was simply typing text in LibreOffice). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.25-lowlatency 3.5.7.4 Uname: Linux 3.5.0-25-lowlatency i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Mar 31 06:55:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-25-lowlatency, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-26-generic, i686: installed virtualbox, 4.1.18, 3.5.0-25-lowlatency, i686: installed virtualbox, 4.1.18, 3.5.0-26-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (9 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0JF77M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0JF77M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.43+git1303291653.ca678b~gd~q version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git1303291656.5f41e0~gd~q version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+git1303291654.6e74aa~gd~q version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5+git1303291654.431816~gd~q version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7+git1303271126.677142~gd~q --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-11-19 15:54:14,165 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (302 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-15-lowlatency i686 UpgradeStatus: Upgraded to saucy on 2013-11-19 (59 days ago) UserGroups: adm audio debian-tor kismet
[Touch-packages] [Bug 1162408] Re: little horizontal black lines sporadically appear
Mistake in above, I have HP Folio 9470m (not 9670) -- 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/1162408 Title: little horizontal black lines sporadically appear Status in “xorg” package in Ubuntu: Incomplete Bug description: Some little horizontal black lines sometimes appear on the Ubuntu desktop. They disappear quickly, and there seems no obvious way to force the event to occur predictably. The problem occurs with libgl1-mesa-dri-experimental but, unless I'm mistaken, occurred also with the nonexperimental branch. Furthermore, I'm running Ubuntu Classic and was not using 3d effects when the problem occurred (was simply typing text in LibreOffice). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.25-lowlatency 3.5.7.4 Uname: Linux 3.5.0-25-lowlatency i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sun Mar 31 06:55:41 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-25-lowlatency, i686: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-26-generic, i686: installed virtualbox, 4.1.18, 3.5.0-25-lowlatency, i686: installed virtualbox, 4.1.18, 3.5.0-26-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (9 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0JF77M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd12/10/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0JF77M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.libdrm2: libdrm2 2.4.43+git1303291653.ca678b~gd~q version.libgl1-mesa-dri: libgl1-mesa-dri 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2~git1303291656.5f41e0~gd~q version.libgl1-mesa-glx: libgl1-mesa-glx 9.2~git1303291656.5f41e0~gd~q version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0+git1303291654.6e74aa~gd~q version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5+git1303291654.431816~gd~q version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7+git1303271126.677142~gd~q --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-11-19 15:54:14,165 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0532] InstallationDate: Installed on 2013-03-21 (302 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E6230 MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-lowlatency root=UUID=f66679c3-3498-4cbc-930b-c7bf9116f37c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-15-lowlatency i686 UpgradeStatus: Upgraded to saucy on 2013-11-19 (59 days ago) UserGroups: adm audio debian-tor kismet lpadmin
