[Touch-packages] [Bug 1179194] Re: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all
[Expired for gstreamer1.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer1.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1179194 Title: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all Status in gstreamer1.0 package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: Totem player crashed after trying to unmute it. Details are; Description: Ubuntu 13.04 Release: 13.04 # apt-cache policy totem totem: Installed: 3.6.3-0ubuntu6 Candidate: 3.6.3-0ubuntu6 Version table: *** 3.6.3-0ubuntu6 0 500 http://ke.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I expected it to unmute and continue playing ;) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbadi 2863 F pulseaudio Date: Sun May 12 14:56:52 2013 InstallationDate: Installed on 2013-04-25 (16 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbadi 2863 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to raring on 2013-04-26 (15 days ago) dmi.bios.date: 06/06/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN33WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Product Name dmi.board.vendor: LENOVO dmi.board.version: Mainboard version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN33WW(V2.03):bd06/06/2012:svnLENOVO:pnLenovoG580:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580: dmi.product.name: Lenovo G580 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1179194/+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 1179194] Re: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1179194 Title: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all Status in gstreamer1.0 package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: Totem player crashed after trying to unmute it. Details are; Description: Ubuntu 13.04 Release: 13.04 # apt-cache policy totem totem: Installed: 3.6.3-0ubuntu6 Candidate: 3.6.3-0ubuntu6 Version table: *** 3.6.3-0ubuntu6 0 500 http://ke.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I expected it to unmute and continue playing ;) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbadi 2863 F pulseaudio Date: Sun May 12 14:56:52 2013 InstallationDate: Installed on 2013-04-25 (16 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbadi 2863 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Lenovo G580, Conexant CX20590, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to raring on 2013-04-26 (15 days ago) dmi.bios.date: 06/06/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN33WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Product Name dmi.board.vendor: LENOVO dmi.board.version: Mainboard version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN33WW(V2.03):bd06/06/2012:svnLENOVO:pnLenovoG580:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580: dmi.product.name: Lenovo G580 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1179194/+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 1450290] Re: network-manager-openvpn ignores dhcp-option SEARCH
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1450290 Title: network-manager-openvpn ignores dhcp-option SEARCH Status in network-manager package in Ubuntu: Expired Bug description: network-manager-openvpn (or some upstream component) is ignoring the dhcp-option SEARCH parameter, which means that not only won't additional domains get appended to search, but if 'Use only for resources on this connection' is enabled, those domains will not get resolved via the VPN DNS servers, breaking split-horizon DNS for sites with more than one domain. When 'Use only for resources on this connection' is enabled, the domains enabled in dnsmasq should be a union of dhcp-option SEARCH, dhcp-option DOMAIN, and reverse domains for networks routed via the connection. Currently only the latter two are enabled. Without 'Use only for resources on this connection' enabled, all DNS resolution does appear to go via the VPN servers, but this is not necessarily desirable, and creates a situation where users may be wedged between having their DNS work as expected, and having their routing work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager-openvpn 0.9.10.0-1ubuntu1 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: KDE Date: Thu Apr 30 13:23:35 2015 InstallationDate: Installed on 2015-04-24 (5 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1450290/+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 1833829] Re: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390
** Summary changed: - High memory usage by Xorg. + High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390 -- 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/1833829 Title: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390 Status in xorg package in Ubuntu: New Bug description: After some continued use of the system (Kubuntu (18.04)) Xorg accumulates a lot of RAM space. From that the space only increments and doesn't decrease. Hardware Specs : 1. Intel core-i5 6300 HQ 2. Nvidia GTX 960M Software Specs : 1. Kubuntu 18.04 2. KDE Plasma shell version 5.12.7 Something interesting to note is that I have not experienced the same behavior from Xorg when I switch the GPU to Intel's Integrated graphics. It is entirely possible that I might not have been able to trigger those situation with Intel, because after seeing logs I couldn't make out why this was happening. Also for the timeline I have used the system for over an year without any such issue arising. It was the second week of June 2019 to present day I have seen this problem. Xorg log : http://paste.ubuntu.com/p/nc3pMF4xsb/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Jun 23 05:06:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:0706] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706] InstallationDate: Installed on 2019-06-21 (1 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=f046965f-7377-42b2-86ba-febdbcabfc9b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd12/13/2017:svnDellInc.:pnInspiron7559:pvr1.2.7:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833829/+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 706039]
I also have this problem on a Macbook 1,1. Substituting ffmpegcolorspace by videoscale gives the same results. According to the Ubuntu Bugtracker this is a kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=36152 Does anyone have a kernel where this setup actually works? Mine is 2.6.39. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/706039 Title: Can't produce data in UYVY Status in gst-plugins-good: Fix Released Status in iSight Firmware Tools: Confirmed Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Status in isight-firmware-tools package in Ubuntu: Confirmed Status in Gentoo Linux: Expired Bug description: v4l-info shows that my isight supports UYVY format, but when trying to configure it on this format it doesn't produce any data. The problem gets worse because this seems to be its preferred format, so gstreamer tries to use it and it fails. gst-launch autovideosrc ! ffmpegcolorspace ! autovideosink Using other formats work. $ v4l-info ### v4l2 device info [/dev/video0] ### general info VIDIOC_QUERYCAP driver : "uvcvideo" card: "Built-in iSight" bus_info: "usb-:00:1d.7-4" version : 0.1.0 capabilities: 0x401 [VIDEO_CAPTURE,STREAMING] standards inputs VIDIOC_ENUMINPUT(0) index : 0 name: "Camera 1" type: CAMERA audioset: 0 tuner : 0 std : 0x0 [] status : 0x0 [] video capture VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE) index : 0 type: VIDEO_CAPTURE flags : 0 description : "YUV 4:2:2 (UYVY)" pixelformat : 0x59565955 [UYVY] VIDIOC_G_FMT(VIDEO_CAPTURE) type: VIDEO_CAPTURE fmt.pix.width : 640 fmt.pix.height : 480 fmt.pix.pixelformat : 0x59565955 [UYVY] fmt.pix.field : NONE fmt.pix.bytesperline: 1280 fmt.pix.sizeimage : 614400 fmt.pix.colorspace : unknown fmt.pix.priv: 0 controls VIDIOC_QUERYCTRL(BASE+0) id : 9963776 type: INTEGER name: "Brightness" minimum : 0 maximum : 255 step: 1 default_value : 63 flags : 0 ### video4linux device info [/dev/video0] ### general info VIDIOCGCAP name: "Built-in iSight" type: 0x1 [CAPTURE] channels: 1 audios : 0 maxwidth: 640 maxheight : 480 minwidth: 48 minheight : 32 channels VIDIOCGCHAN(0) channel : 0 name: "Camera 1" tuners : 0 flags : 0x0 [] type: CAMERA norm: 0 tuner ioctl VIDIOCGTUNER: Invalid argument audio ioctl VIDIOCGAUDIO: Invalid argument picture VIDIOCGPICT brightness : 16191 hue : 0 colour : 54613 contrast: 0 whiteness : 0 depth : 16 palette : UYVY buffer ioctl VIDIOCGFBUF: Invalid argument window VIDIOCGWIN x : 0 y : 0 width : 640 height : 480 chromakey : 0 flags : 0 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-good/+bug/706039/+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 706039]
gstreamer 0.10 has been finally removed from the tree. If this is an issue with the 1.0 series too, please file a new bug against that version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/706039 Title: Can't produce data in UYVY Status in gst-plugins-good: Fix Released Status in iSight Firmware Tools: Confirmed Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Status in isight-firmware-tools package in Ubuntu: Confirmed Status in Gentoo Linux: Expired Bug description: v4l-info shows that my isight supports UYVY format, but when trying to configure it on this format it doesn't produce any data. The problem gets worse because this seems to be its preferred format, so gstreamer tries to use it and it fails. gst-launch autovideosrc ! ffmpegcolorspace ! autovideosink Using other formats work. $ v4l-info ### v4l2 device info [/dev/video0] ### general info VIDIOC_QUERYCAP driver : "uvcvideo" card: "Built-in iSight" bus_info: "usb-:00:1d.7-4" version : 0.1.0 capabilities: 0x401 [VIDEO_CAPTURE,STREAMING] standards inputs VIDIOC_ENUMINPUT(0) index : 0 name: "Camera 1" type: CAMERA audioset: 0 tuner : 0 std : 0x0 [] status : 0x0 [] video capture VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE) index : 0 type: VIDEO_CAPTURE flags : 0 description : "YUV 4:2:2 (UYVY)" pixelformat : 0x59565955 [UYVY] VIDIOC_G_FMT(VIDEO_CAPTURE) type: VIDEO_CAPTURE fmt.pix.width : 640 fmt.pix.height : 480 fmt.pix.pixelformat : 0x59565955 [UYVY] fmt.pix.field : NONE fmt.pix.bytesperline: 1280 fmt.pix.sizeimage : 614400 fmt.pix.colorspace : unknown fmt.pix.priv: 0 controls VIDIOC_QUERYCTRL(BASE+0) id : 9963776 type: INTEGER name: "Brightness" minimum : 0 maximum : 255 step: 1 default_value : 63 flags : 0 ### video4linux device info [/dev/video0] ### general info VIDIOCGCAP name: "Built-in iSight" type: 0x1 [CAPTURE] channels: 1 audios : 0 maxwidth: 640 maxheight : 480 minwidth: 48 minheight : 32 channels VIDIOCGCHAN(0) channel : 0 name: "Camera 1" tuners : 0 flags : 0x0 [] type: CAMERA norm: 0 tuner ioctl VIDIOCGTUNER: Invalid argument audio ioctl VIDIOCGAUDIO: Invalid argument picture VIDIOCGPICT brightness : 16191 hue : 0 colour : 54613 contrast: 0 whiteness : 0 depth : 16 palette : UYVY buffer ioctl VIDIOCGFBUF: Invalid argument window VIDIOCGWIN x : 0 y : 0 width : 640 height : 480 chromakey : 0 flags : 0 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-good/+bug/706039/+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 706039] Re: Can't produce data in UYVY
** Changed in: gentoo Status: New => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/706039 Title: Can't produce data in UYVY Status in gst-plugins-good: Fix Released Status in iSight Firmware Tools: Confirmed Status in gst-plugins-good0.10 package in Ubuntu: Confirmed Status in isight-firmware-tools package in Ubuntu: Confirmed Status in Gentoo Linux: Expired Bug description: v4l-info shows that my isight supports UYVY format, but when trying to configure it on this format it doesn't produce any data. The problem gets worse because this seems to be its preferred format, so gstreamer tries to use it and it fails. gst-launch autovideosrc ! ffmpegcolorspace ! autovideosink Using other formats work. $ v4l-info ### v4l2 device info [/dev/video0] ### general info VIDIOC_QUERYCAP driver : "uvcvideo" card: "Built-in iSight" bus_info: "usb-:00:1d.7-4" version : 0.1.0 capabilities: 0x401 [VIDEO_CAPTURE,STREAMING] standards inputs VIDIOC_ENUMINPUT(0) index : 0 name: "Camera 1" type: CAMERA audioset: 0 tuner : 0 std : 0x0 [] status : 0x0 [] video capture VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE) index : 0 type: VIDEO_CAPTURE flags : 0 description : "YUV 4:2:2 (UYVY)" pixelformat : 0x59565955 [UYVY] VIDIOC_G_FMT(VIDEO_CAPTURE) type: VIDEO_CAPTURE fmt.pix.width : 640 fmt.pix.height : 480 fmt.pix.pixelformat : 0x59565955 [UYVY] fmt.pix.field : NONE fmt.pix.bytesperline: 1280 fmt.pix.sizeimage : 614400 fmt.pix.colorspace : unknown fmt.pix.priv: 0 controls VIDIOC_QUERYCTRL(BASE+0) id : 9963776 type: INTEGER name: "Brightness" minimum : 0 maximum : 255 step: 1 default_value : 63 flags : 0 ### video4linux device info [/dev/video0] ### general info VIDIOCGCAP name: "Built-in iSight" type: 0x1 [CAPTURE] channels: 1 audios : 0 maxwidth: 640 maxheight : 480 minwidth: 48 minheight : 32 channels VIDIOCGCHAN(0) channel : 0 name: "Camera 1" tuners : 0 flags : 0x0 [] type: CAMERA norm: 0 tuner ioctl VIDIOCGTUNER: Invalid argument audio ioctl VIDIOCGAUDIO: Invalid argument picture VIDIOCGPICT brightness : 16191 hue : 0 colour : 54613 contrast: 0 whiteness : 0 depth : 16 palette : UYVY buffer ioctl VIDIOCGFBUF: Invalid argument window VIDIOCGWIN x : 0 y : 0 width : 640 height : 480 chromakey : 0 flags : 0 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-good/+bug/706039/+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 1833833] [NEW] avro does not work
Public bug reported: I am using Avro to pin Bangla after I started using Ubuntu 18.04 LTS but some days later it won,t work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 23 07:23:19 2019 InstallationDate: Installed on 2019-04-27 (56 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1833833 Title: avro does not work Status in ibus package in Ubuntu: New Bug description: I am using Avro to pin Bangla after I started using Ubuntu 18.04 LTS but some days later it won,t work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 23 07:23:19 2019 InstallationDate: Installed on 2019-04-27 (56 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1833833/+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 1833829] [NEW] High memory usage by Xorg.
Public bug reported: After some continued use of the system (Kubuntu (18.04)) Xorg accumulates a lot of RAM space. From that the space only increments and doesn't decrease. Hardware Specs : 1. Intel core-i5 6300 HQ 2. Nvidia GTX 960M Software Specs : 1. Kubuntu 18.04 2. KDE Plasma shell version 5.12.7 Something interesting to note is that I have not experienced the same behavior from Xorg when I switch the GPU to Intel's Integrated graphics. It is entirely possible that I might not have been able to trigger those situation with Intel, because after seeing logs I couldn't make out why this was happening. Also for the timeline I have used the system for over an year without any such issue arising. It was the second week of June 2019 to present day I have seen this problem. Xorg log : http://paste.ubuntu.com/p/nc3pMF4xsb/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Jun 23 05:06:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:0706] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706] InstallationDate: Installed on 2019-06-21 (1 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=f046965f-7377-42b2-86ba-febdbcabfc9b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd12/13/2017:svnDellInc.:pnInspiron7559:pvr1.2.7:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "Screenshot_20190623_052528.jpeg" https://bugs.launchpad.net/bugs/1833829/+attachment/5272398/+files/Screenshot_20190623_052528.jpeg -- 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/1833829 Title: High memory usage by Xorg. Status in xorg package in Ubuntu: New Bug description: After some continued use of the system (Kubuntu (18.04)) Xorg accumulates a lot of RAM space. From that the space only increments and doesn't decrease. Hardware Specs : 1. Intel core-i5 6300 HQ 2. Nvidia GTX 960M Software Specs : 1. Kubuntu 18.04 2. KDE Plasma shell version 5.12.7 Something interesting to note is that I have not experienced the same behavior from Xorg when I switch the GPU to Intel's Integrated graphics. It is entirely possible that I might not have been able to trigger those situation with Intel, because after seeing logs I
[Touch-packages] [Bug 1639408] Re: udev misidentifies usb headset as xbox gamepad from same manufacturer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1639408 Title: udev misidentifies usb headset as xbox gamepad from same manufacturer Status in systemd package in Ubuntu: Confirmed Bug description: I have a USB wireless Afterglow AG9+ Wireless headset that is being misidentifed as a generic xbox pad. This is actually a generic usb sound card [ 931.178869] usb 5-5: new full-speed USB device number 3 using ohci-pci [ 931.373967] usb 5-5: New USB device found, idVendor=0e6f, idProduct=0157 [ 931.373971] usb 5-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 931.373975] usb 5-5: Product: Afterglow AG9+ Wireless HS for XboxOne (Dongle) [ 931.373977] usb 5-5: Manufacturer: Performance Designed Products [ 931.373979] usb 5-5: SerialNumber: 2D53FFD0FBE9 [ 931.376306] input: Generic X-Box pad as /devices/pci:00/:00:13.0/usb5/5-5/5-5:1.0/input/input18 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 5 02:00:10 2016 InstallationDate: Installed on 2016-11-05 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=e0481110-c70f-4b94-a8e8-a32cf885ffd1 ro quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: 970 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd07/31/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1639408/+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 1833826] [NEW] grub menu entry FSCK does not work
Public bug reported: after a fresh install of Xubuntu 18.04.02 I tried "Ubuntu, mit Linux 4.15.0-51-generic (recovery mode)" and as a result got: /lib/recocery-mode/recovery-menu: line 80: /etc/default/rcS: No such file or directory fsck from util-linux 2.31.1 /dev/sda4 is mounted e2fsck: Cannot continue, aborting. I check both the live DVD and the installed filesystem and found /etc/default/rcS to be missing. I copied it over from an old Xubuntu live DVD (it contains commented out lines only) and now the error message is still: fsck from util-linux 2.31.1 /dev/sda4 is mounted e2fsck: Cannot continue, aborting. This shouldn't happen on a newly installed system. I am a newbie to Ubuntu and when my laptop has trouble when I'm on he road basics like that should IMHO work as I won't have the ability to look for workarounds and wouldn't want to boot into a possibly corrupted filesystem. Description:Ubuntu 18.04.2 LTS Release:18.04 util-linux: Installiert: 2.31.1-0.4ubuntu3.3 Installationskandidat: 2.31.1-0.4ubuntu3.3 Versionstabelle: *** 2.31.1-0.4ubuntu3.3 100 100 /var/lib/dpkg/status ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1833826 Title: grub menu entry FSCK does not work Status in util-linux package in Ubuntu: New Bug description: after a fresh install of Xubuntu 18.04.02 I tried "Ubuntu, mit Linux 4.15.0-51-generic (recovery mode)" and as a result got: /lib/recocery-mode/recovery-menu: line 80: /etc/default/rcS: No such file or directory fsck from util-linux 2.31.1 /dev/sda4 is mounted e2fsck: Cannot continue, aborting. I check both the live DVD and the installed filesystem and found /etc/default/rcS to be missing. I copied it over from an old Xubuntu live DVD (it contains commented out lines only) and now the error message is still: fsck from util-linux 2.31.1 /dev/sda4 is mounted e2fsck: Cannot continue, aborting. This shouldn't happen on a newly installed system. I am a newbie to Ubuntu and when my laptop has trouble when I'm on he road basics like that should IMHO work as I won't have the ability to look for workarounds and wouldn't want to boot into a possibly corrupted filesystem. Description: Ubuntu 18.04.2 LTS Release: 18.04 util-linux: Installiert: 2.31.1-0.4ubuntu3.3 Installationskandidat: 2.31.1-0.4ubuntu3.3 Versionstabelle: *** 2.31.1-0.4ubuntu3.3 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1833826/+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 1833823] Re: Text box appeared on the main screen of desktop and no way to get rid of it.
solved it. It was a mistakenly placed sticky note widget. I'll be removing this bug report if that's something I can do. -- 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/1833823 Title: Text box appeared on the main screen of desktop and no way to get rid of it. Status in xorg package in Ubuntu: New Bug description: I'm not sure what happened here. I just downloaded phpbb to work on my own forum and now this text box appeared on my main screen of my laptop and I can't make it go away, even after a restart and complete shutdown and startup. Not sure if it's a problem with xorg/wayland or whatever. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sat Jun 22 11:47:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30] InstallationDate: Installed on 2019-06-19 (3 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5a07 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X510UAR ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-23-generic root=UUID=fee9ef1f-d467-48de-8ddd-824920256181 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UAR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UAR.309:bd07/24/2018:svnASUSTeKCOMPUTERINC.:pnX510UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X510UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833823/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Changed in: lvm2 (Debian) Status: Unknown => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in lvm2 source package in Bionic: New Status in linux source package in Cosmic: New Status in lvm2 source package in Cosmic: New Status in linux source package in Disco: New Status in lvm2 source package in Disco: New Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: In Progress Status in lvm2 package in Debian: Incomplete Bug description: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1833823] [NEW] Text box appeared on the main screen of desktop and no way to get rid of it.
Public bug reported: I'm not sure what happened here. I just downloaded phpbb to work on my own forum and now this text box appeared on my main screen of my laptop and I can't make it go away, even after a restart and complete shutdown and startup. Not sure if it's a problem with xorg/wayland or whatever. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sat Jun 22 11:47:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30] InstallationDate: Installed on 2019-06-19 (3 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5a07 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X510UAR ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-23-generic root=UUID=fee9ef1f-d467-48de-8ddd-824920256181 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UAR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX510UAR.309:bd07/24/2018:svnASUSTeKCOMPUTERINC.:pnX510UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X510UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "The attached pic is a screen print of my main screen." https://bugs.launchpad.net/bugs/1833823/+attachment/5272381/+files/Screenshot_20190622_114919.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1833823 Title: Text box appeared on the main screen of desktop and no way to get rid of it. Status in xorg package in Ubuntu: New Bug description: I'm not sure what happened here. I just downloaded phpbb to work on my own forum and now this text box appeared on my main screen of my laptop and I can't make it go away, even after a restart and complete shutdown and startup. Not sure if it's a problem with xorg/wayland or whatever. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sat Jun 22 11:47:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30] InstallationDate: Installed on 2019-06-19 (3 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5a07 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X510UAR ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1826939] Re: Network restart after suspend is unreliable
This problem has not occurred on my machine for some time now. So I think this bug can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netbase in Ubuntu. https://bugs.launchpad.net/bugs/1826939 Title: Network restart after suspend is unreliable Status in netbase package in Ubuntu: New Bug description: After suspending my computer to standby and then waking it up again, networking restarts unreliably: Sometimes it restarts fine, sometimes it takes a few seconds to restart, and sometimes it takes more than a minute (I didn't wait longer). When the network wakeup is not finished, pings to my local router get a timeout, and "sudo service networking restart" creates this output: klee@gonzales:~$ ping router PING router (192.168.100.254) 56(84) bytes of data. From gonzales (192.168.100.2) icmp_seq=1 Destination Host Unreachable ^C --- router ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 11:16:05 CEST; 12h ago Docs: man:interfaces(5) Main PID: 1239 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/networking.service Apr 29 11:15:58 gonzales systemd[1]: Starting Raise network interfaces... Apr 29 11:15:59 gonzales ifup[1239]: ifup: waiting for lock on /run/network/ifstate.eno1 Apr 29 11:16:05 gonzales systemd[1]: Started Raise network interfaces. After I have done a "sudo service networking restart", the output is this: klee@gonzales:~$ sudo service networking status ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2019-04-29 23:17:00 CEST; 5s ago Docs: man:interfaces(5) Process: 3701 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS) Main PID: 3701 (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 4915) Memory: 7.4M CGroup: /system.slice/networking.service └─3728 /sbin/dhclient -1 -4 -v -pf /run/dhclient.eno1.pid -lf /var/lib/dhcp/dhclient.eno1.leases -I -df /var/lib/dhcp/dhclient6.eno1.leases eno1 Apr 29 23:16:59 gonzales ifup[3701]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 5 (xid=0x53439c24) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales dhclient[3728]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales ifup[3701]: DHCPOFFER of 192.168.100.2 from 192.168.100.254 Apr 29 23:16:59 gonzales ifup[3701]: DHCPREQUEST for 192.168.100.2 on eno1 to 255.255.255.255 port 67 (xid=0x249c4353) Apr 29 23:16:59 gonzales dhclient[3728]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:16:59 gonzales ifup[3701]: DHCPACK of 192.168.100.2 from 192.168.100.254 (xid=0x53439c24) Apr 29 23:17:00 gonzales dhclient[3728]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales ifup[3701]: bound to 192.168.100.2 -- renewal in 42225 seconds. Apr 29 23:17:00 gonzales systemd[1]: Started Raise network interfaces. (And the pings work fine again, too.) This is a regression after the upgrade from 18.10 (where networking wakeup worked fine) to 19.04. Version info: klee@gonzales:~$ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 netbase 5.6 ifupdown 0.8.34ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: netbase 5.6 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 29 23:19:00 2019 Dependencies: InstallationDate: Installed on 2016-08-06 (996 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: netbase UpgradeStatus: Upgraded to disco on 2019-04-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbase/+bug/1826939/+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 1832859] Re: during shutdown libvirt-guests gets stopped after file system unmount
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1701234. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-04-18T12:56:02+00:00 rmetrich wrote: Description of problem: The blk-availability.service unit is activated automatically when multipathd is enabled, even if multipathd is finally not used. This leads to the blk-availability service to unmount file systems too early, breaking unit ordering and leading to shutdown issues of custom services requiring some mount points. Version-Release number of selected component (if applicable): device-mapper-1.02.149-10.el7_6.3.x86_64 How reproducible: Always Steps to Reproduce: 1. Enable multipathd even though there is no multipath device # yum -y install device-mapper-multipath # systemctl enable multipathd --now 2. Create a custom mount point "/data" # lvcreate -n data -L 1G rhel # mkfs.xfs /dev/rhel/data # mkdir /data # echo "/dev/mapper/rhel-data /data xfs defaults 0 0" >> /etc/fstab # mount /data 3. Create a custom service requiring mount point "/data" # cat > /etc/systemd/system/my.service << EOF [Unit] RequiresMountsFor=/data [Service] ExecStart=/bin/bash -c 'echo "STARTING"; mountpoint /data; true' ExecStop=/bin/bash -c 'echo "STOPPING IN 5 SECONDS"; sleep 5; mountpoint /data; true' Type=oneshot RemainAfterExit=true [Install] WantedBy=default.target EOF # systemctl daemon-reload # systemctl enable my.service --now 4. Set up persistent journal and reboot # mkdir -p /var/log/journal # systemctl restart systemd-journald # reboot 5. Check the previous boot's shutdown # journalctl -b -1 -o short-precise -u my.service -u data.mount -u blk-availability.service Actual results: -- Logs begin at Thu 2019-04-18 12:48:12 CEST, end at Thu 2019-04-18 13:35:50 CEST. -- Apr 18 13:31:46.933571 vm-blkavail7 systemd[1]: Started Availability of block devices. Apr 18 13:31:48.452326 vm-blkavail7 systemd[1]: Mounting /data... Apr 18 13:31:48.509633 vm-blkavail7 systemd[1]: Mounted /data. Apr 18 13:31:48.856228 vm-blkavail7 systemd[1]: Starting my.service... Apr 18 13:31:48.894419 vm-blkavail7 bash[2856]: STARTING Apr 18 13:31:48.930270 vm-blkavail7 bash[2856]: /data is a mountpoint Apr 18 13:31:48.979457 vm-blkavail7 systemd[1]: Started my.service. Apr 18 13:35:02.544999 vm-blkavail7 systemd[1]: Stopping my.service... Apr 18 13:35:02.547811 vm-blkavail7 systemd[1]: Stopping Availability of block devices... Apr 18 13:35:02.639325 vm-blkavail7 bash[3393]: STOPPING IN 5 SECONDS Apr 18 13:35:02.760043 vm-blkavail7 blkdeactivate[3395]: Deactivating block devices: Apr 18 13:35:02.827170 vm-blkavail7 blkdeactivate[3395]: [SKIP]: unmount of rhel-swap (dm-1) mounted on [SWAP] Apr 18 13:35:02.903924 vm-blkavail7 systemd[1]: Unmounted /data. Apr 18 13:35:02.988073 vm-blkavail7 blkdeactivate[3395]: [UMOUNT]: unmounting rhel-data (dm-2) mounted on /data... done Apr 18 13:35:02.988253 vm-blkavail7 blkdeactivate[3395]: [SKIP]: unmount of rhel-root (dm-0) mounted on / Apr 18 13:35:03.083448 vm-blkavail7 systemd[1]: Stopped Availability of block devices. Apr 18 13:35:07.693154 vm-blkavail7 bash[3393]: /data is not a mountpoint Apr 18 13:35:07.696330 vm-blkavail7 systemd[1]: Stopped my.service. --> We can see the following: - blkdeactivate runs, unmounting /data, even though my.service is still running (hence the unexpected message "/data is not a mountpoint") Expected results: - my.service gets stopped - then "data.mount" gets stopped - finally blkdeactivate runs Additional info: I understand there is some chicken-and-egg problem here, but it's just not possible to blindly unmount file systems and ignore expected unit ordering. Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859/comments/0 On 2019-04-23T13:09:14+00:00 prajnoha wrote: Normally, I'd add Before=local-fs-pre.target into blk- availability.service so on shutdown its ExecStop would execute after all local mount points are unmounted. The problem might be with all the dependencies like iscsi, fcoe and rbdmap services where we need to make sure that these are executed *after* blk-availability. So I need to find a proper target that we can hook on so that it also fits all the dependencies. It's possible we need to create a completely new target so we can properly synchronize all the services on shutdown. I'll see what I can do... Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859/comments/1 On 2019-04-23T13:17:39+00:00 rmetrich wrote: Indeed, wasn't able to find a proper
[Touch-packages] [Bug 1833821] [NEW] Printer not printing
Public bug reported: The OS has recognized and installed the driver for the printer but has failed to print any and all documents when the print button is pressed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 23:02:31 2019 InstallationDate: Installed on 2019-06-20 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for LBP2900: usb://Canon/LBP2900?serial=A2C54KO9 MachineType: Sony Corporation VPCEG25EN Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/LBP2900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/LBP2900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=f8d3de2c-0473-40a3-8b12-d95100633f39 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R0240Z8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0240Z8:bd01/06/2012:svnSonyCorporation:pnVPCEG25EN:pvrC901CBN4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEG25EN dmi.product.sku: N/A dmi.product.version: C901CBN4 dmi.sys.vendor: Sony Corporation ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1833821 Title: Printer not printing Status in cups package in Ubuntu: New Bug description: The OS has recognized and installed the driver for the printer but has failed to print any and all documents when the print button is pressed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 23:02:31 2019 InstallationDate: Installed on 2019-06-20 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for LBP2900: usb://Canon/LBP2900?serial=A2C54KO9 MachineType: Sony Corporation VPCEG25EN Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/LBP2900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/LBP2900.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=f8d3de2c-0473-40a3-8b12-d95100633f39 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R0240Z8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0240Z8:bd01/06/2012:svnSonyCorporation:pnVPCEG25EN:pvrC901CBN4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEG25EN dmi.product.sku: N/A dmi.product.version: C901CBN4 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833821/+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 1833817] [NEW] Substring expansion "${string%%' '*}" doesn't work
Public bug reported:
The following substring expansion to get the first word of a string
separated by spaces doesn't work using dash 0.5.8-2.10 on Ubuntu 18.04
LTS:
string="one two three four"
first="${string%%' '*}"
printf "%s\n" "$first"
It prints "one two three four", instead of "one". This works on bash and
Solaris sh, but not in dash.
Oddly, not putting the white space between single quotes works:
string="one two three four"
first="${string%% *}"
printf "%s\n" "$first" # Prints "one"
** Affects: dash (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic
** Tags added: bionic
** Summary changed:
- Parameter expansion "${string%%' '*}" doesn't work
+ Substring expansion "${string%%' '*}" doesn't work
** Description changed:
- The following parameter expansion to get the first word of a string
+ The following substring expansion to get the first word of a string
separated by spaces doesn't work using dash 0.5.8-2.10 on Ubuntu 18.04
LTS:
string="one two three four"
first="${string%%' '*}"
printf "%s\n" "$first"
It prints "one two three four", instead of "one". This works on bash and
Solaris sh, but not in dash.
** Description changed:
The following substring expansion to get the first word of a string
separated by spaces doesn't work using dash 0.5.8-2.10 on Ubuntu 18.04
LTS:
string="one two three four"
first="${string%%' '*}"
printf "%s\n" "$first"
It prints "one two three four", instead of "one". This works on bash and
Solaris sh, but not in dash.
+
+ Oddly, not putting the white space between single quotes works:
+ string="one two three four"
+ first="${string%% *}"
+ printf "%s\n" "$first" # Prints "one"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1833817
Title:
Substring expansion "${string%%' '*}" doesn't work
Status in dash package in Ubuntu:
New
Bug description:
The following substring expansion to get the first word of a string
separated by spaces doesn't work using dash 0.5.8-2.10 on Ubuntu 18.04
LTS:
string="one two three four"
first="${string%%' '*}"
printf "%s\n" "$first"
It prints "one two three four", instead of "one". This works on bash
and Solaris sh, but not in dash.
Oddly, not putting the white space between single quotes works:
string="one two three four"
first="${string%% *}"
printf "%s\n" "$first" # Prints "one"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1833817/+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 1821462] Re: Ubuntu 19.04 Desktop:slow boot
mine also take too much to boot https://paste.ubuntu.com/p/nZQf5ySCT5/ And the time system booted up is https://paste.ubuntu.com/p/BtwVSDCMTH/ and takes more than this time when trying to open firefox or files . -- 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/1821462 Title: Ubuntu 19.04 Desktop:slow boot Status in systemd package in Ubuntu: Confirmed Bug description: Hello, I have my ubuntu desktop set to boot text only mode. it seems a removable hard drive was pplugged into my machine some time ago. On every boot the boot takes a minute and a half to search to see if that drive is plugged in. I ran systemd-analyze blame Below is my output: 37.816s apt-daily.service 2.383s dev-sda4.device 2.381s NetworkManager-wait-online.service 1.198s man-db.service 1.112s dev-loop9.device 1.108s dev-loop8.device 1.098s dev-loop4.device 1.083s dev-loop6.device 1.071s dev-loop10.device 1.057s dev-loop13.device 1.057s dev-loop11.device 1.051s dev-loop7.device 1.051s dev-loop12.device 1.046s dev-loop2.device 1.032s dev-loop14.device 1.024s apt-daily-upgrade.service 1.017s snap-core18-782.mount 988ms snap-vice\x2djz-22.mount 983ms snap-gnome\x2dcalculator-260.mount 949ms dev-loop15.device 930ms dev-loop3.device 905ms dev-loop5.device 901ms dev-loop1.device 899ms dev-loop0.device 891ms dev-loop16.device 878ms snap-gnome\x2d3\x2d26\x2d1604-78.mount 868ms snap-remmina-2831.mount 855ms snap-gnome\x2dcharacters-139.mount 845ms snap-youtube\x2ddl\x2dsnap-1.mount 844ms dev-loop17.device 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount 814ms snap-remmina-2823.mount 803ms snap-gnome\x2dclocks-85.mount 798ms snap-gnome\x2dcharacters-206.mount 793ms snap-core-6350.mount 783ms snap-core-6531.mount 776ms udisks2.service 773ms snap-gnome\x2dlogs-45.mount 763ms snap-vice\x2djz-20.mount 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount 744ms snap-core-6405.mount 734ms snap-vice\x2djz-19.mount 733ms snap-gnome\x2dcharacters-124.mount 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount 719ms dev-loop18.device 715ms snap-core18-731.mount 706ms snap-core18-719.mount 695ms snap-gnome\x2dcalculator-238.mount 680ms upower.service 662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount 646ms dev-loop19.device 643ms snap-gtk\x2dcommon\x2dthemes-818.mount 638ms dev-loop23.device 626ms snap-gnome\x2dlogs-57.mount 626ms dev-loop26.device 610ms snap-gnome\x2dsystem\x2dmonitor-70.mount 596ms dev-loop21.device 589ms dev-loop25.device 587ms dev-loop20.device 583ms dev-loop24.device 528ms logrotate.service 523ms systemd-journal-flush.service 496ms dev-loop22.device 491ms dev-loop30.device 490ms dev-loop27.device 487ms dev-loop28.device 433ms networkd-dispatcher.service 427ms snapd.service 397ms ModemManager.service 382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount 379ms snap-gnome\x2dcalculator-352.mount 369ms snap-remmina-2819.mount 362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount 359ms snap-gnome\x2dsystem\x2dmonitor-57.mount 340ms accounts-daemon.service 307ms systemd-logind.service 281ms keyboard-setup.service 280ms kmod-static-nodes.service 261ms dev-hugepages.mount 260ms avahi-daemon.service 259ms sys-kernel-debug.mount 259ms ufw.service 255ms apport-autoreport.service 251ms systemd-udev-trigger.service 242ms systemd-modules-load.service 232ms systemd-journald.service 230ms fwupd.service 206ms apport.service 196ms dev-mqueue.mount 194ms apparmor.service 186ms rsyslog.service 184ms dev-loop29.device 182ms NetworkManager.service 181ms systemd-remount-fs.service 180ms gdm.service 174ms nmbd.service 164ms smbd.service 164ms wpa_supplicant.service
[Touch-packages] [Bug 1833811] [NEW] fail boot after installation with lvm due to missing thin-provisioning-tools
Public bug reported: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773731 when installating and creating a raid 1 with lvm cache etc, system fails to boot due to missing /usr/sbin/cache_check reports lvm2-pvscan@, fixes itself after installing the package thin-provisioning-tools ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 22 06:42:09 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1833811 Title: fail boot after installation with lvm due to missing thin- provisioning-tools Status in lvm2 package in Ubuntu: New Bug description: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773731 when installating and creating a raid 1 with lvm cache etc, system fails to boot due to missing /usr/sbin/cache_check reports lvm2-pvscan@, fixes itself after installing the package thin- provisioning-tools ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 22 06:42:09 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1833811/+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 1464321] Re: No sound output through docking station headphones jack for Dell Latitude E5450
Larry's solution works, but the downside is the laptop's internal headphone/mic jacks and speaker is still muted when you undock it, unless you switch back to Analog Stereo duplex manually. This was tested with xubuntu 16.04 (x86) on a Dell D620 (Sigmatel Audio). Has anyone found a solution to let the laptop switch between outputs automatically? It even works with Win XP... Thanks in advance. -- 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/1464321 Title: No sound output through docking station headphones jack for Dell Latitude E5450 Status in alsa-driver package in Ubuntu: New Bug description: 1) Release: 15.04 2) I do not know the package or version. 3) Expected: I expect sound to be output from the speaker that is connected to the headphones jack of my docking station. 4) Actual: No sound output at all. I have this problem with my new computer: Dell Latitude E5450/5450 (Late 2014) Service Tag: 4W7RQ32. I can confirm that the docking station and speaker both work, as I did not have this problem on my older Dell Latitude E5420 (Early 2011) Service Tag: 1WW25S1 running Ubuntu version 14.04LTS ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1574 F pulseaudio /dev/snd/controlC2: thomas 1574 F pulseaudio /dev/snd/controlC1: thomas 1574 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 11 11:10:28 2015 InstallationDate: Installed on 2015-06-11 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1574 F pulseaudio /dev/snd/controlC2: thomas 1574 F pulseaudio /dev/snd/controlC1: thomas 1574 F pulseaudio Symptom_Jack: Green Line Out, Rear, Docking station Symptom_Type: No sound at all Title: [Latitude E5450, Realtek ALC3235, Green Line Out, Rear, Docking station] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 09X6YN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/10/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn09X6YN:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1464321/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
** Tags added: disco -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: New Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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
