[Touch-packages] [Bug 1750051] Re: cron doesn't support MAILFROM
you're right only adding 6 lines and one bug inside :-( new patch with the corrected line ** Attachment added: "patch_v2.txt" https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+attachment/5135958/+files/patch_v2.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1750051 Title: cron doesn't support MAILFROM Status in cron package in Ubuntu: Triaged Status in cron package in Debian: New Bug description: Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. $ apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 16 15:52:54 2018 InstallationDate: Installed on 2016-12-06 (436 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 1769824] [NEW] Xorg crash
Public bug reported: System was idle at the time. It displayed the background wall paper, but did NOT display the login screen. I had to go to console, and restart lightdm. Wayno ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon May 7 23:16:23 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1312] InstallationDate: Installed on 2018-04-27 (10 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP-Pavilion KJ385AA-ABA a6433w ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5c74d40b-8d0a-4abd-b32e-fca693b36f98 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnKJ385AA-ABAa6433w:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KJ385AA-ABA a6433w dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769824 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: System was idle at the time. It displayed the background wall paper, but did NOT display the login screen. I had to go to console, and restart lightdm. Wayno ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon May 7 23:16:23 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1312] InstallationDate: Installed on 2018-04-27 (10 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP-Pavilion KJ385AA-ABA a6433w ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5c74d40b-8d0a-4abd-b32e-fca693b36f98 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnKJ385AA-ABAa6433w:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KJ385AA-ABA a6433w dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-
[Touch-packages] [Bug 1769822] [NEW] VGA Resolution Detect with KVM
Public bug reported: Detects fine with direct connect, but when through kvm (works fine with windows) will not detect proper resolution. Log files should show: 1. Boot with KVM attached. 2. Plug monitor direct to motherboard (bypass) - old resolution for instant, then change to proper resolution. 3. Swap back to monitor with KVM - Ok for instant, then blank and back to low resolution. KVM model is kvm 41ua - purchased from ebay. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 8 00:13:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-05-06 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=b4d352ff-c19b-4f83-b0e6-94d042477b7f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: H55M-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic resolution ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769822 Title: VGA Resolution Detect with KVM Status in xorg package in Ubuntu: New Bug description: Detects fine with direct connect, but when through kvm (works fine with windows) will not detect proper resolution. Log files should show: 1. Boot with KVM attached. 2. Plug monitor direct to motherboard (bypass) - old resolution for instant, then change to proper resolution. 3. Swap back to monitor with KVM - Ok for instant, then blank and back to low resolution. KVM model is kvm 41ua - purchased from ebay. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 8 00:13:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-05-06 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=b4d352ff-c19b-4f83-b0e6-94d042477b7f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International, Inc.
[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
After that any "apt install" and also "apt upgrade" happens with this error. sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of libguestfs0:amd64: libguestfs0:amd64 depends on lvm2; however: Package lvm2 is not configured yet. dpkg: error processing package libguestfs0:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-reiserfs:amd64: libguestfs-reiserfs:amd64 depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however: Package libguestfs0:amd64 is not configured yet. No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already dpkg: error processing package libguestfs-reiserfs:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-perl: libguestfs-perl depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however: Package libguestfs0:amd64 is not configured yet. dpkg: error processing package libguestfs-perl (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-hfsplus:amd64: libguestfs-hfsplus:amd64 depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however: Package libguestfs0:amd64 is not configured yet. dpkg: error processing package libguestfs-hfsplus:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-tools: libguestfs-tools depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however: Package libguestfs0:amd64 is not configured yet. libguestfs-tools dependNo apport report written because MaxReports is reached already No apport report written because MaxReports is reached already s on libguestfs-perl (= 1:1.36.13-1ubuntu3); however: Package libguestfs-perl is not configured yet. dpkg: error processing package libguestfs-tools (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libguestfs-xfs:amd64: libguestfs-xfs:amd64 depends on libguestfs0 (= 1:1.36.13-1ubuntu3); however: Package libguestfs0:amd64 is not configured yet. dpkg: error processing package libguestfs-xfs:amd64 (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic Errors were encountered while processing: lvm2 libguestfs0:amd64 libguestfs-reiserfs:amd64 libguestfs-perl libguestfs-hfsplus:amd64 libguestfs-tools libguestfs-xfs:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) In
[Touch-packages] [Bug 1769812] [NEW] "installed ca-certificates package post-installation script subprocess returned error exit status 1"
Public bug reported: happened during upgrade to Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: r8168 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 8 06:55:36 2018 InstallationDate: Installed on 2016-01-24 (834 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ca-certificates UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1769812 Title: "installed ca-certificates package post-installation script subprocess returned error exit status 1" Status in ca-certificates package in Ubuntu: New Bug description: happened during upgrade to Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: r8168 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 8 06:55:36 2018 InstallationDate: Installed on 2016-01-24 (834 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ca-certificates UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1769812/+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 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1754296 Title: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver) Status in xorg-server package in Ubuntu: New Bug description: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite extension prevents tearing in (some) games and sometimes is an additional performance boost. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bionic). I tested with the mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and bionic. Xserver will crash with "Option "Composite" "0/False/Disable" When I comment out the specific line in the Extensions section (that means *enabling* Composite) it works again with this xorg.conf. I can also do other stuff like disabling DRI3 or AIGLX. No crashes in these cases. My xorg.conf: Section "Device" Identifier "Intel GMA45" ##just a trivial name as Identifier Driver "intel" EndSection Section "Extensions" Option "Composite" "0" EndSection It has a backtrace and caughts signal 6. My Xorg.0.log: [ 35.779] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 35.781] X Protocol Version 11, Revision 0 [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64 [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash [ 35.787] Build Date: 22 February 2018 08:04:42PM [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 35.789] Current version of pixman: 0.34.0 [ 35.792] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: Wed Mar 7 22:43:35 2018 [ 35.801] (==) Using config file: "/etc/X11/xorg.conf" [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 35.803] (==) No Layout section. Using the first Screen section. [ 35.803] (==) No screen section available. Using defaults. [ 35.803] (**) |-->Screen "Default Screen Section" (0) [ 35.803] (**) | |-->Monitor "" [ 35.804] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset" [ 35.804] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 35.804] (==) Automatically adding devices [ 35.804] (==) Automatically enabling devices [ 35.804] (==) Automatically adding GPU devices [ 35.804] (==) Automatically binding GPU devices [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 35.809] Entry deleted from font path. [ 35.822] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules" [ 35.822] (**) Extension "Composite" is disabled [ 35.822] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 35.822] (II) Loader magic: 0x55cfd2964020 [ 35.822] (II) Module ABI versions: [ 35.822] X.Org ANSI C Emulation: 0.4 [ 35.822] X.Org Video Driver: 23.0 [ 35.822] X.Org XInput driver : 24.1 [ 35.822] X.Org Server Extension : 10.0 [ 35.824] (++) using VT number 1 [ 35.827] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0) [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 0x/131072 [ 35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 0xd340/1048576 [ 35.833] (II) LoadModu
[Touch-packages] [Bug 1769480] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1769480 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- 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/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+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 1751129] Re: I think there is some security issue in my ubuntu .
[Expired for sudo (Ubuntu) because there has been no activity for 60 days.] ** Changed in: sudo (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1751129 Title: I think there is some security issue in my ubuntu . Status in sudo package in Ubuntu: Expired Bug description: If I log into any other user i am able to access my main user through terminal with my current user password. I am using ubuntu 16.04 and I think it might be in all ubuntu 16.04 operating systems. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.5+16.04.20171201.3 Uname: Linux 4.15.1-041501-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 23 01:06:34 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed bbswitch, 0.8, 4.15.1-041501-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.15.1-041501-generic, x86_64: installed virtualbox, 5.0.40, 4.13.0-32-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2018-01-22 (31 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_IN LANGUAGE=en_IN:en XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.1-041501-generic root=UUID=95af4278-a5ad-4183-9691-2a68fd0e627e ro resume=UUID=a7e7e167-65b7-4b78-ad75-4400e9b38bad resume= resume= quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.33 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.57 dmi.chassis.asset.tag: CNU4219GQQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.33:bd09/01/2015:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009FD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009FD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.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 xserver.bootTime: Thu Feb 22 21:34:13 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1751129/+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 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
** Also affects: 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+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 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
This is the debdiff for cosmic. Backported the 2 patches to 1.1.6-1. thanks. ** Patch added: "alsa-lib_1.1.6-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1768830/+attachment/5135786/+files/alsa-lib_1.1.6-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Bionic: New Bug description: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. SRU Document: [Impact] We have several Lenovo machines like Lenovo P520 which have 2 analogue audio codecs on them, the internal speaker and front headset are connected to the 1st codec, the Rear mic, Line in and Line out are connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and front headset) on the 1st codec can work. To make all audio devices work on this machine, upstream provided 3 patches for kernel audio driver and 5 patches for alsa-lib. The kernel patches are already in the linux-4.12, so this is not a problem anymore under 18.04 since we use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport them to v1.1.3-5, the 5 patches are list as below: 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) Some explanation for these 5 patches, to make the audio work, the alsa-lib needs to add an audio configuration file and verb conf file for lenovo machines with dual codecs, these two files are put in a folder named by card_long_name, and the name of configuration file itself is also named by card_long_name, this is implemented by the patches of NO. 3rd and 5th. But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. [Test Case] On the Lenovo machines with dual codecs (p520), I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can find the conf file and can parse the conf file successfully, and I tested the internal speaker, front headset, rear mic, line out and line in, all audio devices work well. On a HP and Dell machines without dual codecs, I insatlled the libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the alsa-lib can't find conf file by card_long_name and card_name, the pulseaudio will drive the sound card as before, so all audio functions worked well as before. [Regression Potential] After adding these 5 patches, there 2 two changes introduced into the alsa-lib v1.1.3-5ubuntu1: 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, 2) before: the ucm parser will search the conf file/folder by card_name only; after: the ucm parser will search the conf file/foler by card_long_name first, if it fails, it will fallback to use card_name to search again. So this change is compatible with old version. There is no regression since there is only one folder named by card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with dual codecs, it will find the conf file by card_long_name, if it runs on other machines, the search by card_long_name will definitely fail and fall back to search by card_name, then it will be same as before. So the objective of these 5 patches is to let lenovo machines with dual codecs find the conf file by card_long_name, let other machines fail to search by card_long_name, then fallback to original searching method - search by card_name. [Other Info] Since I could not find the alsa-lib repository in canonical, I just generated the debdiff with "apt-get source
[Touch-packages] [Bug 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.
See also bug 1767312. ** Summary changed: - Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics + [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes. ** No longer affects: totem (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1720820 Title: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: WORKAROUNDS Just for totem: sudo apt remove gstreamer1.0-vaapi Or to workaround in all players: sudo apt remove mesa-va-drivers ORIGINAL DESCRIPTION Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD Fury graphics card and open source drivers. Video output is just a black frame and crash happens within just a few seconds after video playback starts. Could not reproduce bug on two older Intel laptops with iGPU's where hardware acceleration seemed to work fine under Wayland. Issue is only present on Wayland, not x. I can get hardware accelerated video playback working on Wayland with 'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only way I have found so far. Even in mpv, no other option than vaapi-copy works. gst-play-1.0 outputs the following error: ERROR Internal error: could not render surface for file:///*** ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 totem 3.25.90.1-0ubuntu3 gstreamer1.0-vaapi:amd641.12.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
** Summary changed: - [radeon] totem wrong color on h264 videos + [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos ** Description changed: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove mesa-va-drivers + + See also bug 1720820. ** Description changed: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: + sudo apt remove gstreamer1.0-vaapi + or sudo apt remove mesa-va-drivers See also bug 1720820. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1769800] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"]
** Summary changed: - package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769800 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"] Status in bluez package in Ubuntu: New Bug description: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769800/+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 1769800] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769800 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"] Status in bluez package in Ubuntu: New Bug description: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769800/+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 1769800] [NEW] package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769800 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: error occurred at initial boot-up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Mon May 7 18:10:42 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-05 (91 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision M2400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0U698R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M2400 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:22:5F:B6:8C:FB ACL MTU: 1021:8 SCO MTU: 64:8 DOWN RX bytes:607 acl:0 sco:0 events:39 errors:0 TX bytes:3303 acl:0 sco:0 commands:39 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769800/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
Yes, that is mentioned in https://trello.com/c/i3JvebJ9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
Yes, that is mentioned in https://trello.com/c/i3JvebJ9 Although you then face the problem of upsetting people who prefer doing two-finger taps :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
Would it be possible to make 'area' mode the default if the touchpad doesn't support multi-finger input? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1769778] Re: package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: base-files (Ubuntu) Importance: Undecided => Low ** Changed in: base-files (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1769778 Title: package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured Status in base-files package in Ubuntu: Invalid Bug description: ProblemType: Package DistroRelease: Ubuntu 17.10 Package: base-files 10.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu17 Architecture: amd64 CrashReports: 600:110:119:0:2018-05-08 00:00:33.264052851 +0530:2018-05-08 00:00:33.264052851 +0530:/var/crash/debianutils.0.uploaded 640:0:119:260163:2018-05-08 00:00:15.572422981 +0530:2018-05-08 00:00:30.496090202 +0530:/var/crash/debianutils.0.crash 600:0:119:208763:2018-05-07 23:37:57.606923580 +0530:2018-05-07 23:37:58.606923580 +0530:/var/crash/base-files.0.crash 644:0:119:0:2018-05-08 00:00:30.496090202 +0530:2018-05-08 00:00:30.496090202 +0530:/var/crash/debianutils.0.upload 600:0:119:212512:2018-05-07 23:38:09.622976445 +0530:2018-05-07 23:38:09.214974485 +0530:/var/crash/bash.0.crash Date: Mon May 7 23:37:58 2018 ErrorMessage: package base-files is already installed and configured InstallationDate: Installed on 2017-04-11 (391 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: base-files Title: package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured UpgradeStatus: Upgraded to artful on 2018-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1769778/+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 1769778] [NEW] package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 17.10 Package: base-files 10.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu17 Architecture: amd64 CrashReports: 600:110:119:0:2018-05-08 00:00:33.264052851 +0530:2018-05-08 00:00:33.264052851 +0530:/var/crash/debianutils.0.uploaded 640:0:119:260163:2018-05-08 00:00:15.572422981 +0530:2018-05-08 00:00:30.496090202 +0530:/var/crash/debianutils.0.crash 600:0:119:208763:2018-05-07 23:37:57.606923580 +0530:2018-05-07 23:37:58.606923580 +0530:/var/crash/base-files.0.crash 644:0:119:0:2018-05-08 00:00:30.496090202 +0530:2018-05-08 00:00:30.496090202 +0530:/var/crash/debianutils.0.upload 600:0:119:212512:2018-05-07 23:38:09.622976445 +0530:2018-05-07 23:38:09.214974485 +0530:/var/crash/bash.0.crash Date: Mon May 7 23:37:58 2018 ErrorMessage: package base-files is already installed and configured InstallationDate: Installed on 2017-04-11 (391 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: base-files Title: package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured UpgradeStatus: Upgraded to artful on 2018-05-07 (0 days ago) ** Affects: base-files (Ubuntu) Importance: Low Status: Invalid ** Tags: already-installed amd64 apport-package artful hardware-error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1769778 Title: package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured Status in base-files package in Ubuntu: Invalid Bug description: ProblemType: Package DistroRelease: Ubuntu 17.10 Package: base-files 10.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu17 Architecture: amd64 CrashReports: 600:110:119:0:2018-05-08 00:00:33.264052851 +0530:2018-05-08 00:00:33.264052851 +0530:/var/crash/debianutils.0.uploaded 640:0:119:260163:2018-05-08 00:00:15.572422981 +0530:2018-05-08 00:00:30.496090202 +0530:/var/crash/debianutils.0.crash 600:0:119:208763:2018-05-07 23:37:57.606923580 +0530:2018-05-07 23:37:58.606923580 +0530:/var/crash/base-files.0.crash 644:0:119:0:2018-05-08 00:00:30.496090202 +0530:2018-05-08 00:00:30.496090202 +0530:/var/crash/debianutils.0.upload 600:0:119:212512:2018-05-07 23:38:09.622976445 +0530:2018-05-07 23:38:09.214974485 +0530:/var/crash/bash.0.crash Date: Mon May 7 23:37:58 2018 ErrorMessage: package base-files is already installed and configured InstallationDate: Installed on 2017-04-11 (391 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: base-files Title: package base-files 9.6ubuntu102 failed to install/upgrade: package base-files is already installed and configured UpgradeStatus: Upgraded to artful on 2018-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1769778/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa
If you are using Ubuntu 18.04 please try the version of software- properties from the bionic-proposed pocket. See bug 175 for detailed instructions regarding enabling and using -proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1769338 Title: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa Status in software-properties package in Ubuntu: New Bug description: Switching from nvidia to nouveau makes the gui to get stuck at "Applying changes..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769637] Re: Update evolution-data-server to 3.28.2
This bug was fixed in the package evolution-data-server - 3.28.2-1 --- evolution-data-server (3.28.2-1) unstable; urgency=medium * New upstream release (LP: #1769637) -- Jeremy Bicha Mon, 07 May 2018 08:21:46 -0400 ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1769637 Title: Update evolution-data-server to 3.28.2 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Bionic: Triaged Bug description: Impact == evolution-data-server (e-d-s) has released a new stable bugfix release. (These will happen about once every month until 3.30 is released in Septebmer) Updating e-d-s is required to update evolution to 3.28.2 (LP: #) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-28 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-28 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1769637/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
> I would feel better if a wider call-for-testing could be done on these > packages > in bionic-proposed yes i agree; the mailing lists that comes to mind is ubuntu-server, do you have any other ML suggestion? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: Fix Committed Status in vlan source package in Bionic: Fix Committed Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: [impact] in bug 1573272, the vlan pkg was changed to perform a full ifup inside its if-pre-up.d/vlan script. This allowed correct ordering of ifup for a vlan and its raw-device, as previously there was a race condition between them (see that bug for details). However, this causes hangs during ifup with certain specific configs. The reasons are given starting in comment 13. The result is a regression for those using the specific ifupdown configs; when they try to reboot and/or ifup -a, it will hang trying to bring up their network, preventing boot from finishing (or hanging before the network is fully configured). [test case] upgrade to the latest vlan package and configure the system with an affected ifupdown config, then reboot. The reboot will hang while trying to bring the network up. see the original description below for an example ifupdown config to reproduce this, although there are other possible configs that will/may trigger this regression. [regression potential] The fix for this moves the creation of the vlan(s) corresponding to a physical raw-device 'hotplug' event out of the udev processing path for the raw-device, and into an ifup post script for the raw-device ifup. If this is not done correctly, then any interfaces that are hotplugged, and have vlans configured on them, may fail to correctly create/configure their vlan(s). This change does remove the direct call to ifup from the if-pre-up.d (or if-up.d) scripts, so there should not be any regression potential for more ifup deadlocks. [other info] this required both ifupdown and vlan to be patched. vlan was patched to remove the problematic call to ifup from the vlan pre-up script, and add a call to create the vlan interface(s) from a new post-up script, as well as adding a parameter to vlan-network-interface script to handle the call from udev itself differently than a call from elsewhere (such as the if-up.d/vlan script). this works for bootup and ifup/ifup -a, but fails for device hotplug because of a bug in ifupdown that prevents calling ifquery from an ifup script; that has been patched upstream already, and is the only ifupdown change needed here. [original description] When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
Egmont, by the way, that mutter patch is in Debian also since mutter is currently in sync between Debian and Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
@guido Nope, that one is irrelevant (that icon title is something completely different, it's a legacy concept: the title of the window whenever it's iconified; plus the change is in gnome-terminal's current development series which won't appear in Bionic). Anyway, I managed to locate the bug, see my previous comment. Now it's Ubuntu's turn to apply the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
I'm confused. Are my URL & yours the same? Anyway, it seems that Ubuntu has not fixed it. Terminal seems to work OK, so far; but, it certainly is an eyesore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1752053] Re: nvidia-390 fails to boot graphical display
Is there any way possible to gain early access to the "FIX RELEASED" files??? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
@guido Oh, I guess I found it, I guess you meant this: https://gitlab.gnome.org/GNOME/mutter/merge_requests/62 I made a comment over there. This patch is buggy, this is the one that breaks my previous fix. The patch is shipped by Ubuntu, named theme-use-gtk_render_icon_suface- to-paint-button-icon.patch (intended to fix LP #1764558) inside mutter_3.28.1-1ubuntu1.debian.tar.xz. Ubuntu should drop (or fix) this broken patch to fix this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1164016] Re: restore type-ahead find
Why don't we have both options? Why removing something that we like
(find folder/file with a letter) and insisting on something else
(search)? I am trying to get used to this new behavior for almost a
week, but it is just slowing me down.
This could be implemented as simple as this:
## keypress event
switch (option_search_or_locate ) {
case 1: locate_folder (char_pressed); break;
case 2: search (char_pressed); break;
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1164016
Title:
restore type-ahead find
Status in Nautilus:
Expired
Status in nautilus package in Ubuntu:
Fix Released
Status in ubuntu-settings package in Ubuntu:
Fix Released
Bug description:
GNOME removed type-ahead find in Nautilus 3.6, not without
controversy:
https://mail.gnome.org/archives/nautilus-
list/2012-August/msg2.html
Now when you type in a Nautilus window, Nautilus immediately performs
a search in the current directory and all its subdirectories. I
personally find this annoying. If I want to search, I'll click the
search icon. Often I'm looking at a long directory listing and simply
want to jump to a certain point in it, and type-ahead find works great
for that.
Would Ubuntu consider patching type-ahead find back in?
To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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
Re: [Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
Wait. Try this from Christian Persch. Commit from 5 days ago. https://github.com/GNOME/gnome- terminal/commit/887c8128d7c528660afa53fad9ae46e72ca7297c On Mon, May 7, 2018 at 12:27 PM, Egmont Koblinger wrote: > > There is a patch on gitHub for this about 3 days ago. > > Where exactly? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1748785). > https://bugs.launchpad.net/bugs/1718238 > > Title: > Giant terminal icon is blocking out the Terminal window buttons > > Status in gnome-shell package in Ubuntu: > Confirmed > Status in mutter package in Ubuntu: > Confirmed > Status in ubuntu-themes package in Ubuntu: > Invalid > > Bug description: > Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: light-themes 16.10+17.10.20170918-0ubuntu1 > ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 > Uname: Linux 4.12.0-13-generic x86_64 > ApportVersion: 2.20.7-0ubuntu1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Sep 19 12:47:51 2017 > InstallationDate: Installed on 2017-09-19 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 > (20170917) > PackageArchitecture: all > SourcePackage: ubuntu-themes > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+ > bug/1718238/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1753704]
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1753704 Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package initramfs-tools 0.122ubuntu8.10 failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.10 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 00:22:13 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1753704/+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
Re: [Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
I can not find it; wish I had saved it. On Mon, May 7, 2018 at 12:27 PM, Egmont Koblinger wrote: > > There is a patch on gitHub for this about 3 days ago. > > Where exactly? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1748785). > https://bugs.launchpad.net/bugs/1718238 > > Title: > Giant terminal icon is blocking out the Terminal window buttons > > Status in gnome-shell package in Ubuntu: > Confirmed > Status in mutter package in Ubuntu: > Confirmed > Status in ubuntu-themes package in Ubuntu: > Invalid > > Bug description: > Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: light-themes 16.10+17.10.20170918-0ubuntu1 > ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 > Uname: Linux 4.12.0-13-generic x86_64 > ApportVersion: 2.20.7-0ubuntu1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Sep 19 12:47:51 2017 > InstallationDate: Installed on 2017-09-19 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 > (20170917) > PackageArchitecture: all > SourcePackage: ubuntu-themes > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+ > bug/1718238/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1713813] Re: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1713813 Title: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: I keep gettin an error that I am out of space on /boot This is a default Ubuntu install, so I'd figure y'all would have the default /boot partition be the proper size. I executed: sudo apt-get autoremove linux-image-4.4.0.66-generic And this error popped up. There has got to be a better way to manage new and old linux images. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mamanakisdm 4396 F pulseaudio /dev/snd/pcmC1D0c: mamanakisdm 4396 F...m pulseaudio /dev/snd/pcmC1D0p: mamanakisdm 4396 F...m pulseaudio /dev/snd/controlC1: mamanakisdm 4396 F pulseaudio Date: Tue Aug 29 14:10:50 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=a6ba8e97-6214-4c0c-8267-f063b5e54c12 InstallationDate: Installed on 2016-11-22 (280 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BHS02400 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GNET66WW (2.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET66WW(2.14):bd07/02/2014:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1713813/+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 1731363] Re: package linux-firmware 1.157.13 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1731363 Title: package linux-firmware 1.157.13 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: install failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.13 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Nov 10 08:07:09 2017 Dependencies: ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-04-20 (203 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.13 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1731363/+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 1753704] Re: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1753704 Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package initramfs-tools 0.122ubuntu8.10 failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.10 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 00:22:13 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1753704/+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 1729420] Re: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1729420 Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: auto-report ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: one2578 F pulseaudio /dev/snd/controlC0: one2578 F pulseaudio /dev/snd/controlC1: one2578 F pulseaudio Date: Wed Nov 1 14:23:46 2017 DpkgHistoryLog: Start-Date: 2017-11-01 14:22:47 Commandline: aptdaemon role='role-commit-packages' sender=':1.917' Install: linux-image-4.4.0-98-generic:amd64 (4.4.0-98.121, automatic), linux-image-extra-4.4.0-98-generic:amd64 (4.4.0-98.121, automatic), linux-headers-4.4.0-98-generic:amd64 (4.4.0-98.121, automatic), linux-headers-4.4.0-98:amd64 (4.4.0-98.121, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.4.0.98.103), linux-libc-dev:amd64 (4.4.0-97.120, 4.4.0-98.121), linux-image-generic:amd64 (4.4.0.97.102, 4.4.0.98.103), linux-generic:amd64 (4.4.0.97.102, 4.4.0.98.103) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2014-05-22 (1259 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. B85M-D3H ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-98-generic 4.4.0-98.121 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2016-07-30 (459 days ago) dmi.bios.date: 05/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/02/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B85M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729420/+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 1737790] Re: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1737790 Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Might have been caused by a full /boot Maybe same as https://bugs.launchpad.net/bugs/1737282 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: theo 14705 F pulseaudio david 30317 F pulseaudio gdm 30621 F pulseaudio Date: Mon Dec 11 22:34:49 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=b82815c7-d577-421c-ae03-79a7aa4b080d InstallationDate: Installed on 2014-10-01 (1167 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 42404CG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET51WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 42404CG 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:bvr8AET51WW(1.31):bd08/08/2011:svnLENOVO:pn42404CG:pvrThinkPadT520:rvnLENOVO:rn42404CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 42404CG dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1737790/+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 1745428] Re: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1745428 Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.15 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Jan 25 16:24:40 2018 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-13 (469 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745428/+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 1752401] Re: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1752401 Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Maybe caused by lack of free space in /boot Maybe same as https://bugs.launchpad.net/bugs/1752269 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-36-generic 4.13.0-36.40 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Feb 28 20:20:34 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=b82815c7-d577-421c-ae03-79a7aa4b080d InstallationDate: Installed on 2014-10-01 (1245 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 42404CG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.1 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET51WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 42404CG 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:bvr8AET51WW(1.31):bd08/08/2011:svnLENOVO:pn42404CG:pvrThinkPadT520:rvnLENOVO:rn42404CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 42404CG dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1752401/+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 1761842] Re: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1761842 Title: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: I just ran the Software Updater and I got this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1429 F pulseaudio josef 1877 F pulseaudio /dev/snd/controlC0: gdm1429 F pulseaudio josef 1877 F pulseaudio Date: Fri Apr 6 20:44:14 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=e203c511-a20b-4f19-9b17-96abb1de77dd InstallationDate: Installed on 2015-12-18 (840 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7.3 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-38-generic 4.13.0-38.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to artful on 2018-01-21 (75 days ago) dmi.bios.date: 02/22/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 038C0K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/22/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1761842/+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 1769449] Re: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to update the kernel on your system due to a lack of free space in your boot partition. Please resolve this situation manually and try the update again. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Low ** Tags added: no-boot-space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769449 Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Selecting previously unselected package linux-image-extra-4.4.0-119-generic. (Reading database ... 241161 files and directories currently installed.) Preparing to unpack .../linux-image-extra-4.4.0-119-generic_4.4.0-119.143_amd64.deb ... Unpacking linux-image-extra-4.4.0-119-generic (4.4.0-119.143) ... Setting up linux-image-extra-4.4.0-119-generic (4.4.0-119.143) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-119-generic /boot/vmlinuz-4.4.0-119-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-119-generic /boot/vmlinuz-4.4.0-119-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-119-generic /boot/vmlinuz-4.4.0-119-generic update-initramfs: Generating /boot/initrd.img-4.4.0-119-generic cp: error writing '/var/tmp/mkinitramfs_Ts9JHc//lib/x86_64-linux-gnu/libmount.so.1.1.0': No space left on device cp: error writing '/var/tmp/mkinitramfs_Ts9JHc//sbin/logsave': No space left on device cat: write error: No space left on device cp: error writing '/var/tmp/mkinitramfs_Ts9JHc//sbin/e2fsck': No space left on device E: /usr/share/initramfs-tools/hooks/fsck failed with return 1. update-initramfs: failed for /boot/initrd.img-4.4.0-119-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-extra-4.4.0-119-generic (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-extra-4.4.0-119-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-119-generic 4.4.0-119.143 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.16 AptOrdering: linux-image-extra-4.4.0-119-generic: Install linux-image-extra-4.4.0-119-generic: Configure NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: miniesta4 1742 F pulseaudio /dev/snd/controlC0: miniesta4 1742 F pulseaudio Date: Sun May 6 13:21:49 2018 DpkgHistoryLog: Start-Date: 2018-05-06 13:21:32 Commandline: apt-get install linux-image-extra-4.4.0-119-generic Requested-By: miniesta4 (1000) Install: linux-image-extra-4.4.0-119-generic:amd64 (4.4.0-119.143) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=bbb65603-f5e4-4f77-a3f9-c0aab1a19da9 MachineType: Dell Inc. Inspiron 3847 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=70d4167a-b5c0-439a-b080-c3343552a187 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-119-generic 4.4.0-119.143 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 088DT1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/18/2014:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 3847 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769449/+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.launch
[Touch-packages] [Bug 1769735] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1769735 Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: No se cual es el error, solo salio el msj de erorr y lo reporto ProblemType: Package DistroRelease: Ubuntu 18.04 Package: hicolor-icon-theme 0.17-2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 6 16:55:18 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-05-08 (1460 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1769735/+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 1769735] [NEW] package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned
Public bug reported: No se cual es el error, solo salio el msj de erorr y lo reporto ProblemType: Package DistroRelease: Ubuntu 18.04 Package: hicolor-icon-theme 0.17-2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 6 16:55:18 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-05-08 (1460 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1769735 Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: No se cual es el error, solo salio el msj de erorr y lo reporto ProblemType: Package DistroRelease: Ubuntu 18.04 Package: hicolor-icon-theme 0.17-2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 6 16:55:18 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-05-08 (1460 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1769735/+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 1766542] Re: Installation blocks when the machine is behind a proxy server
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in apt source package in Bionic: New Status in ubiquity source package in Bionic: New Bug description: When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1769727] Re: Black Screen on Wake
see also: https://bugs.launchpad.net/ubuntu-mate/+bug/1769726 older references: https://bugs.launchpad.net/ubuntu-mate/+bug/1688716/+activity -- 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/1769727 Title: Black Screen on Wake Status in xorg package in Ubuntu: New Bug description: Mate 18.04 (64bit) MacbookAir 1,1 Intel i915 Blackscreen after every resume. All other features work. Just no backlight. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Mon May 7 13:05:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller (primary) [106b:00a2] Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller (secondary) [106b:00a2] InstallationDate: Installed on 2018-05-06 (1 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookAir1,1 ProcEnviron: LANGUAGE=en_CA PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA11.88Z.00BB.B03.0803171226 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42C8CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42C8CC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA11.88Z.00BB.B03.0803171226:bd03/17/08:svnAppleInc.:pnMacBookAir1,1:pvr1.0:rvnAppleInc.:rnMac-F42C8CC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C8CC8: dmi.product.family: MacBook dmi.product.name: MacBookAir1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769727/+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 1769727] [NEW] Black Screen on Wake
Public bug reported: Mate 18.04 (64bit) MacbookAir 1,1 Intel i915 Blackscreen after every resume. All other features work. Just no backlight. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Mon May 7 13:05:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller (primary) [106b:00a2] Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller (secondary) [106b:00a2] InstallationDate: Installed on 2018-05-06 (1 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookAir1,1 ProcEnviron: LANGUAGE=en_CA PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA11.88Z.00BB.B03.0803171226 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42C8CC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42C8CC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA11.88Z.00BB.B03.0803171226:bd03/17/08:svnAppleInc.:pnMacBookAir1,1:pvr1.0:rvnAppleInc.:rnMac-F42C8CC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F42C8CC8: dmi.product.family: MacBook dmi.product.name: MacBookAir1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769727 Title: Black Screen on Wake Status in xorg package in Ubuntu: New Bug description: Mate 18.04 (64bit) MacbookAir 1,1 Intel i915 Blackscreen after every resume. All other features work. Just no backlight. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Mon May 7 13:05:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller (primary) [106b:00a2] Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller (secondary) [106b:00a2] InstallationDate: Installed on 2018-05-06 (1 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. MacBookAir1,1 ProcEnviron: LANGUAGE=en_CA PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1cbada0f-d832-4878-b308-9a37b089ff3d ro quiet splash video=SVIDEO-1:d vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA11.88Z.00BB.B03.0803171226 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42C8CC8 dmi.board.vendor
[Touch-packages] [Bug 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
> There is a patch on gitHub for this about 3 days ago. Where exactly? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1164016] Re: restore type-ahead find
In Ubuntu 18.04 this problem is now present again :-( it is really annoying... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons
2018 May 7. Obscuring icon remains. Did fresh install last night with all updates. There is a patch on gitHub for this about 3 days ago. Has it been incorporated by Ubuntu? Does it fix the issue? ** Attachment added: "Screenshot of terminal with obscuring icon." https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1718238/+attachment/5135575/+files/Screenshot_2018-05-07_11-32-04.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718238 Title: Giant terminal icon is blocking out the Terminal window buttons Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 12:47:51 2017 InstallationDate: Installed on 2017-09-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718238/+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 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Same with me. But already lvm2 (2.02.176-4.1ubuntu3) I was trying to install vagrant. -- 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/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
The same problem with Ubuntu 18.04, Teknet BM308, and Lenovo Ideapad 320-15IKB And sometimes when the mouse is conected it's running very slowly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1769368] Re: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1769368 Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. Status in opencv package in Ubuntu: New Bug description: Estaba haciendo un sudo apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat May 5 10:54:05 2018 DpkgTerminalLog: dpkg: error al procesar el paquete libopencv-contrib3.2:amd64 (--remove): el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: opencv Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1769368/+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 1769369] Re: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1769369 Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. Status in opencv package in Ubuntu: New Bug description: Estaba haciendo un sudo apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat May 5 10:54:05 2018 DpkgTerminalLog: dpkg: error al procesar el paquete libopencv-contrib3.2:amd64 (--remove): el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: opencv Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1769369/+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 1769370] Re: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1769370 Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. Status in opencv package in Ubuntu: New Bug description: Estaba haciendo un sudo apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sat May 5 10:54:05 2018 DpkgTerminalLog: dpkg: error al procesar el paquete libopencv-contrib3.2:amd64 (--remove): el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: opencv Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de intentar desinstalarlo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1769370/+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 1769375] Re: package gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1769375 Title: package gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: No estaba haciendo nada, solo salió ese mensaje ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: libgstreamer-opencv1.0-0:amd64: Install gstreamer1.0-opencv:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 5 11:19:05 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gst-plugins-bad1.0 Title: package gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1769375/+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 1769712] Re: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769712 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in initramfs-tools package in Ubuntu: New Bug description: a plain 17-10 to 18.04 distribution upgrade gave this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cp 1600 F pulseaudio Date: Mon May 7 18:47:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2017-08-28 (252 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Studio 1737 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3b44acaa-ce70-4d0f-89cd-b1dc78f53a0e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: Upgraded to bionic on 2018-05-07 (0 days ago) dmi.bios.date: 10/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd10/09/2008:svnDellInc.:pnStudio1737:pvrA01:rvnDellInc.:rn0P792H:rvrA01:cvnDellInc.:ct8:cvrA01: dmi.product.name: Studio 1737 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769712/+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 1769712] [NEW] package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Public bug reported: a plain 17-10 to 18.04 distribution upgrade gave this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cp 1600 F pulseaudio Date: Mon May 7 18:47:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2017-08-28 (252 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Studio 1737 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3b44acaa-ce70-4d0f-89cd-b1dc78f53a0e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: Upgraded to bionic on 2018-05-07 (0 days ago) dmi.bios.date: 10/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd10/09/2008:svnDellInc.:pnStudio1737:pvrA01:rvnDellInc.:rn0P792H:rvrA01:cvnDellInc.:ct8:cvrA01: dmi.product.name: Studio 1737 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769712 Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in initramfs-tools package in Ubuntu: New Bug description: a plain 17-10 to 18.04 distribution upgrade gave this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cp 1600 F pulseaudio Date: Mon May 7 18:47:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2017-08-28 (252 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: Dell Inc. Studio 1737 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3b44acaa-ce70-4d0f-89cd-b1dc78f53a0e ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-20-generic 4.15.0-20.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: Upgraded to bionic on 2018-05-07 (0 days ago) dmi.bios.date: 10/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0P792H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A01 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd10/09/2008:svnDellInc.:pnStudio1737:pvrA01:rvnDellInc.:rn0P792H:rvrA01:cvnDellInc.:ct8:cvrA01: dmi.product.name: Studio 1737 dmi.product.version: A01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769712/+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 50093] Re: Some sysctls are ignored on boot
A workaround for this that we're using now is to put the sysctl processing into crontab after reboot. e.g. @reboot root sleep 5 && sysctl --system Maybe one day someone will fix this bug :) -- 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/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1767864] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Thank You Steve! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1767864 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: Invalid Bug description: da ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun Apr 29 16:55:42 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-11-11 (533 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767864/+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 1769500] Re: will not update
** Information type changed from Private Security to Public -- 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/1769500 Title: will not update Status in xorg package in Ubuntu: New Bug description: will not update. Gives error msg public key 8BAF9A6F ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 6 15:07:21 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] [1002:9804] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6250] [103c:3577] InstallationDate: Installed on 2017-11-26 (161 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=ed27f603-858e-45f5-9ba1-0b1789b36c0f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.48 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.4A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068C11000320491620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.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 xserver.bootTime: Sat May 5 13:58:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769500/+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 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
It should probably also check for 127.0.0.53, not just 127.0.0.1 ** Also affects: avahi (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898038 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Confirmed Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in avahi package in Debian: Unknown Bug description: On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+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 1769371] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1767864 *** https://bugs.launchpad.net/bugs/1767864 Specifically, your system is running an openssl from Ondřej Surý's php ppa, which needs to have the fix for LP: #1764848 backported to it. See https://github.com/oerdnj/deb.sury.org/issues/859. ** Bug watch added: github.com/oerdnj/deb.sury.org/issues #859 https://github.com/oerdnj/deb.sury.org/issues/859 ** This bug has been marked a duplicate of bug 1767864 package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1769371 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: Invalid Bug description: I upgrade to 18.04 LTS then I start face this issue which cause of late os start and somehow makes Ubuntu so slow and stuck in start up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 18:06:36 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-08-14 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-27 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1769371/+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 1701023] Please test proposed package
Hello Sven, or anyone else affected, Accepted ifupdown into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ifupdown/0.8.17ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: Fix Committed Status in vlan source package in Bionic: Fix Committed Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: [impact] in bug 1573272, the vlan pkg was changed to perform a full ifup inside its if-pre-up.d/vlan script. This allowed correct ordering of ifup for a vlan and its raw-device, as previously there was a race condition between them (see that bug for details). However, this causes hangs during ifup with certain specific configs. The reasons are given starting in comment 13. The result is a regression for those using the specific ifupdown configs; when they try to reboot and/or ifup -a, it will hang trying to bring up their network, preventing boot from finishing (or hanging before the network is fully configured). [test case] upgrade to the latest vlan package and configure the system with an affected ifupdown config, then reboot. The reboot will hang while trying to bring the network up. see the original description below for an example ifupdown config to reproduce this, although there are other possible configs that will/may trigger this regression. [regression potential] The fix for this moves the creation of the vlan(s) corresponding to a physical raw-device 'hotplug' event out of the udev processing path for the raw-device, and into an ifup post script for the raw-device ifup. If this is not done correctly, then any interfaces that are hotplugged, and have vlans configured on them, may fail to correctly create/configure their vlan(s). This change does remove the direct call to ifup from the if-pre-up.d (or if-up.d) scripts, so there should not be any regression potential for more ifup deadlocks. [other info] this required both ifupdown and vlan to be patched. vlan was patched to remove the problematic call to ifup from the vlan pre-up script, and add a call to create the vlan interface(s) from a new post-up script, as well as adding a parameter to vlan-network-interface script to handle the call from udev itself differently than a call from elsewhere (such as the if-up.d/vlan script). this works for bootup and ifup/ifup -a, but fails for device hotplug because of a bug in ifupdown that prevents calling ifquery from an ifup script; that has been patched upstream already, and is the only ifupdown change needed here. [original description] When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0
[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
Hello Sven, or anyone else affected, Accepted vlan into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: vlan (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: ifupdown (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: Fix Committed Status in vlan source package in Bionic: Fix Committed Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: [impact] in bug 1573272, the vlan pkg was changed to perform a full ifup inside its if-pre-up.d/vlan script. This allowed correct ordering of ifup for a vlan and its raw-device, as previously there was a race condition between them (see that bug for details). However, this causes hangs during ifup with certain specific configs. The reasons are given starting in comment 13. The result is a regression for those using the specific ifupdown configs; when they try to reboot and/or ifup -a, it will hang trying to bring up their network, preventing boot from finishing (or hanging before the network is fully configured). [test case] upgrade to the latest vlan package and configure the system with an affected ifupdown config, then reboot. The reboot will hang while trying to bring the network up. see the original description below for an example ifupdown config to reproduce this, although there are other possible configs that will/may trigger this regression. [regression potential] The fix for this moves the creation of the vlan(s) corresponding to a physical raw-device 'hotplug' event out of the udev processing path for the raw-device, and into an ifup post script for the raw-device ifup. If this is not done correctly, then any interfaces that are hotplugged, and have vlans configured on them, may fail to correctly create/configure their vlan(s). This change does remove the direct call to ifup from the if-pre-up.d (or if-up.d) scripts, so there should not be any regression potential for more ifup deadlocks. [other info] this required both ifupdown and vlan to be patched. vlan was patched to remove the problematic call to ifup from the vlan pre-up script, and add a call to create the vlan interface(s) from a new post-up script, as well as adding a parameter to vlan-network-interface script to handle the call from udev itself differently than a call from elsewhere (such as the if-up.d/vlan script). this works for bootup and ifup/ifup -a, but fails for device hotplug because of a bug in ifupdown that prevents calling ifquery from an ifup script; that has been patched upstream already, and is the only ifupdown change needed here. [original description] When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 in
[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
Seeing that the previous change caused regressions, I would feel better if a wider call-for-testing could be done on these packages in bionic- proposed, performing tests on various different configurations. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: Fix Committed Status in vlan source package in Bionic: Fix Committed Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: [impact] in bug 1573272, the vlan pkg was changed to perform a full ifup inside its if-pre-up.d/vlan script. This allowed correct ordering of ifup for a vlan and its raw-device, as previously there was a race condition between them (see that bug for details). However, this causes hangs during ifup with certain specific configs. The reasons are given starting in comment 13. The result is a regression for those using the specific ifupdown configs; when they try to reboot and/or ifup -a, it will hang trying to bring up their network, preventing boot from finishing (or hanging before the network is fully configured). [test case] upgrade to the latest vlan package and configure the system with an affected ifupdown config, then reboot. The reboot will hang while trying to bring the network up. see the original description below for an example ifupdown config to reproduce this, although there are other possible configs that will/may trigger this regression. [regression potential] The fix for this moves the creation of the vlan(s) corresponding to a physical raw-device 'hotplug' event out of the udev processing path for the raw-device, and into an ifup post script for the raw-device ifup. If this is not done correctly, then any interfaces that are hotplugged, and have vlans configured on them, may fail to correctly create/configure their vlan(s). This change does remove the direct call to ifup from the if-pre-up.d (or if-up.d) scripts, so there should not be any regression potential for more ifup deadlocks. [other info] this required both ifupdown and vlan to be patched. vlan was patched to remove the problematic call to ifup from the vlan pre-up script, and add a call to create the vlan interface(s) from a new post-up script, as well as adding a parameter to vlan-network-interface script to handle the call from udev itself differently than a call from elsewhere (such as the if-up.d/vlan script). this works for bootup and ifup/ifup -a, but fails for device hotplug because of a bug in ifupdown that prevents calling ifquery from an ifup script; that has been patched upstream already, and is the only ifupdown change needed here. [original description] When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
> could we get the SRU template information included in this bug? doh. sorry, been awfully busy lately. added. ** Description changed: + [impact] + + in bug 1573272, the vlan pkg was changed to perform a full ifup inside + its if-pre-up.d/vlan script. This allowed correct ordering of ifup for + a vlan and its raw-device, as previously there was a race condition + between them (see that bug for details). + + However, this causes hangs during ifup with certain specific configs. + The reasons are given starting in comment 13. + + The result is a regression for those using the specific ifupdown + configs; when they try to reboot and/or ifup -a, it will hang trying to + bring up their network, preventing boot from finishing (or hanging + before the network is fully configured). + + [test case] + + upgrade to the latest vlan package and configure the system with an + affected ifupdown config, then reboot. The reboot will hang while + trying to bring the network up. + + see the original description below for an example ifupdown config to + reproduce this, although there are other possible configs that will/may + trigger this regression. + + [regression potential] + + The fix for this moves the creation of the vlan(s) corresponding to a + physical raw-device 'hotplug' event out of the udev processing path for + the raw-device, and into an ifup post script for the raw-device ifup. + If this is not done correctly, then any interfaces that are hotplugged, + and have vlans configured on them, may fail to correctly + create/configure their vlan(s). + + This change does remove the direct call to ifup from the if-pre-up.d (or + if-up.d) scripts, so there should not be any regression potential for + more ifup deadlocks. + + [other info] + + this required both ifupdown and vlan to be patched. vlan was patched to + remove the problematic call to ifup from the vlan pre-up script, and add + a call to create the vlan interface(s) from a new post-up script, as + well as adding a parameter to vlan-network-interface script to handle + the call from udev itself differently than a call from elsewhere (such + as the if-up.d/vlan script). this works for bootup and ifup/ifup -a, + but fails for device hotplug because of a bug in ifupdown that prevents + calling ifquery from an ifup script; that has been patched upstream + already, and is the only ifupdown change needed here. + + + [original description] + When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a - └─run-parts,1501 /etc/network/if-pre-up.d - └─bridge,1502 /etc/network/if-pre-up.d/bridge - └─bridge,1508 /etc/network/if-pre-up.d/bridge - └─vlan,1511 /etc/network/if-pre-up.d/vlan - └─ifup,1532 eth0 - + └─run-parts,1501 /etc/network/if-pre-up.d + └─bridge,1502 /etc/network/if-pre-up.d/bridge + └─bridge,1508 /etc/network/if-pre-up.d/bridge + └─vlan,1511 /etc/network/if-pre-up.d/vlan + └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static - address 192.168.10.65 - netmask 255.255.255.192 - gateway 192.168.10.66 + address 192.168.10.65 + netmask 255.255.255.192 + gateway 192.168.10.66 auto eth0.11 - address 192.168.11.1 - netmask 255.255.255.0 + address 192.168.11.1 + netmask 255.255.255.0 auto br1134 iface br1134 inet manual - bridge_ports eth0.1134 - bridge_stp off - bridge_fd 0 + bridge_ports eth0.1134 + bridge_stp off + bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: [impact] in bug 1573272, the vlan pkg was changed to perform a full ifup inside its if-pre-up.d/vlan script. This allowed co
[Touch-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
** Package changed: ubuntu => network-manager (Ubuntu) -- 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/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769480/+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 1769480] [NEW] Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
You have been subscribed to a public bug: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- Ubuntu 18.04 - networkmanager dont show other wifi after few minutes https://bugs.launchpad.net/bugs/1769480 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- 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 1769371] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
libssl from a PPA. ** Changed in: ca-certificates (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1769371 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: Invalid Bug description: I upgrade to 18.04 LTS then I start face this issue which cause of late os start and somehow makes Ubuntu so slow and stuck in start up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 18:06:36 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-08-14 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-27 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1769371/+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 1747871] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You have a broken third party init script named "jasperserver" that you will need to remove. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- 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/1747871 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: I can't proceed with the update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Feb 7 16:45:49 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-26 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.19 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1747871/+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 1769684] [NEW] audio crashes on start up and volume slider does not control volume output levels (Can only be muted or at max volume)
Public bug reported: using alsa-mixer master volume changes with audio slider but output volume does not change but can still be muted. - changing PCM values directly changes output volume still works - This problem does not occur when headphones are plugged in even after start up Description:Ubuntu 16.04.4 LTS Release:16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neo2345 F pulseaudio neo3794 F alsamixer CurrentDesktop: Unity Date: Mon May 7 22:53:40 2018 InstallationDate: Installed on 2018-05-04 (3 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE 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.:bvrUX550VE.304:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-05T00:06:39.133243 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1769684 Title: audio crashes on start up and volume slider does not control volume output levels (Can only be muted or at max volume) Status in alsa-driver package in Ubuntu: New Bug description: using alsa-mixer master volume changes with audio slider but output volume does not change but can still be muted. - changing PCM values directly changes output volume still works - This problem does not occur when headphones are plugged in even after start up Description: Ubuntu 16.04.4 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neo2345 F pulseaudio neo3794 F alsamixer CurrentDesktop: Unity Date: Mon May 7 22:53:40 2018 InstallationDate: Installed on 2018-05-04 (3 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE 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.:bvrUX550VE.304:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-05T00:06:39.133243 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1769684/+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 1581084] Re: CMS Consistency Test failed
** Patch removed: "update-expired-smime-test-certs.patch" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1581084/+attachment/4661310/+files/update-expired-smime-test-certs.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1581084 Title: CMS Consistency Test failed Status in openssl package in Ubuntu: Confirmed Bug description: It looks like the CMS test certificates are expired and are causing verification failures. openssl_1.0.1f-1ubuntu2.19_amd64.deb When building from source I get the following error: CMS consistency test /usr/bin/perl cms-test.pl CMS => PKCS#7 compatibility tests signed content DER format, RSA key: verify error make[2]: *** [test_cms] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1581084/+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 1752053] Re: nvidia-390 fails to boot graphical display
Back to where I started with a non-bootable machine, after modifying xorg.conf listed in post #121. I will go aheada purge these nvidia drivers again, and try #123 to see if that works. This is a crazy mess!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1747411] Re: Change of default database file format to SQL
Corosync is actually a sync for Cosmic, with all Delta dropped: * Merge with Debian unstable (LP: #1747411). Remaining changes: * Dropped Changes: - Properly restart corosync and pacemaker together (LP: #1740892) d/rules: pass --restart-after-upgrade to dh_installinit. (this is default in compat >=10, and the package is 11) - d/control: indicate this version breaks all older pacemaker, to force an upgrade of pacemaker. (Upgrades have gone through Bionic, so we can drop this now) - d/corosync.postinst: if flagged to do so by pacemaker, start pacemaker on upgrade. (Can be dropped after Bionic) - New upstream release 2.4.3 (now in Debian) - Drop upstreamed patches and refresh others. (now in Debian) To get a second opinion on that I opened: https://code.launchpad.net/~paelzer/ubuntu/+source/corosync/+git/corosync/+merge/345184 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/corosync/+git/corosync/+merge/345184 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1747411 Title: Change of default database file format to SQL Status in certmonger package in Ubuntu: Fix Released Status in corosync package in Ubuntu: New Status in dogtag-pki package in Ubuntu: Fix Released Status in freeipa package in Ubuntu: Fix Released Status in libapache2-mod-nss package in Ubuntu: Won't Fix Status in nss package in Ubuntu: New Bug description: nss in version 3.35 in upstream changed [2] the default file format [1] (if no explicit one is specified). For now we reverted that change in bug 1746947 until all packages depending on it are ready to work with that correctly. This bug here is about to track when the revert can be dropped. Therefore we list all known-to-be-affected packages and once all are resolved this can be dropped. [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql [2]: https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/certmonger/+bug/1747411/+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 1750051] Re: cron doesn't support MAILFROM
I looked at the patch (didn't test it) and I think the fprintf call is missing an argument to format as a string. It should read like this IMHO: - fprintf(mail, "From: root (Cron Daemon)\n"); + fprintf(mail, "From: %s\n", mailfrom); -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1750051 Title: cron doesn't support MAILFROM Status in cron package in Ubuntu: Triaged Status in cron package in Debian: New Bug description: Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. $ apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 16 15:52:54 2018 InstallationDate: Installed on 2016-12-06 (436 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css
I proposed a fix here: https://gitlab.gnome.org/GNOME/gnome-control- center/merge_requests/40/diffs ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759468/+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 1769674] Re: package python-minimal 2.7.14-2ubuntu1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1769674 Title: package python-minimal 2.7.14-2ubuntu1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: sudo apt-get --reinstall install python Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: bbswitch-dkms dkms gcc-6-base gcj-6-jre-lib gnome-orca lib32gcc1 libbsd0:i386 libc6-i386 libffi6:i386 libgcj-common libgcj17 libgl1:i386 libglvnd0:i386 libglx0:i386 libiso9660-10 libiso9660-8 liblivemedia58 libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2 libmircore-dev libnvidia-cfg1-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libprotobuf-dev libruby2.3 libvcdinfo0 libvlccore8 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx264-148 libx265-130 libxau6:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 linux-headers-4.13.0-38 linux-headers-4.13.0-38-generic linux-image-4.13.0-38-generic linux-image-extra-4.13.0-37-generic linux-image-extra-4.13.0-38-generic linux-signed-image-4.13.0-38-generic linux-signed-image-generic linux-tools-4.13.0-38 linux-tools-4.13.0-38-generic nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-utils-390 ruby2.3 ruby2.3-dev xserver-xorg-video-nvidia-390 Use 'sudo apt autoremove' to remove them. Suggested packages: python-doc python-tk The following packages will be upgraded: python 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. Need to get 140 kB of archives. After this operation, 2.048 B disk space will be freed. Get:1 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 python amd64 2.7.15~rc1-1 [140 kB] Fetched 140 kB in 0s (686 kB/s) Setting up python-minimal (2.7.15~rc1-1) ... dpkg: error processing package python-minimal (--configure): installed python-minimal package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: python-minimal E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-minimal 2.7.14-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 7 16:10:10 2018 DuplicateSignature: package:python-minimal:2.7.14-2ubuntu1 Setting up python-minimal (2.7.14-2ubuntu1) ... dpkg: error processing package python-minimal (--configure): installed python-minimal package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python-minimal package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-11-14 (174 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: python-defaults Title: package python-minimal 2.7.14-2ubuntu1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1769674/+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 1769674] [NEW] package python-minimal 2.7.14-2ubuntu1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1
Public bug reported: sudo apt-get --reinstall install python Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: bbswitch-dkms dkms gcc-6-base gcj-6-jre-lib gnome-orca lib32gcc1 libbsd0:i386 libc6-i386 libffi6:i386 libgcj-common libgcj17 libgl1:i386 libglvnd0:i386 libglx0:i386 libiso9660-10 libiso9660-8 liblivemedia58 libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2 libmircore-dev libnvidia-cfg1-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libprotobuf-dev libruby2.3 libvcdinfo0 libvlccore8 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx264-148 libx265-130 libxau6:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 linux-headers-4.13.0-38 linux-headers-4.13.0-38-generic linux-image-4.13.0-38-generic linux-image-extra-4.13.0-37-generic linux-image-extra-4.13.0-38-generic linux-signed-image-4.13.0-38-generic linux-signed-image-generic linux-tools-4.13.0-38 linux-tools-4.13.0-38-generic nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-utils-390 ruby2.3 ruby2.3-dev xserver-xorg-video-nvidia-390 Use 'sudo apt autoremove' to remove them. Suggested packages: python-doc python-tk The following packages will be upgraded: python 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. Need to get 140 kB of archives. After this operation, 2.048 B disk space will be freed. Get:1 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 python amd64 2.7.15~rc1-1 [140 kB] Fetched 140 kB in 0s (686 kB/s) Setting up python-minimal (2.7.15~rc1-1) ... dpkg: error processing package python-minimal (--configure): installed python-minimal package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: python-minimal E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-minimal 2.7.14-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 7 16:10:10 2018 DuplicateSignature: package:python-minimal:2.7.14-2ubuntu1 Setting up python-minimal (2.7.14-2ubuntu1) ... dpkg: error processing package python-minimal (--configure): installed python-minimal package post-installation script subprocess returned error exit status 1 ErrorMessage: installed python-minimal package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-11-14 (174 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: python-defaults Title: package python-minimal 2.7.14-2ubuntu1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-07 (0 days ago) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1769674 Title: package python-minimal 2.7.14-2ubuntu1 failed to install/upgrade: installed python-minimal package post-installation script subprocess returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: sudo apt-get --reinstall install python Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: bbswitch-dkms dkms gcc-6-base gcj-6-jre-lib gnome-orca lib32gcc1 libbsd0:i386 libc6-i386 libffi6:i386 libgcj-common libgcj17 libgl1:i386 libglvnd0:i386 libglx0:i386 libiso9660-10 libiso9660-8 liblivemedia58 libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2 libmircore-dev libnvidia-cfg1-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libprotobuf-dev libruby2.3 libvcdinfo0 libvlccore8 libwayland-client0:i386 libwayland-
[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
Same issue in Ubuntu 18.04, fresh install on Lenovo e540 notebook, with two different bluetooth mouse - Logitech M557 - Tecknet BM307 The problem occurs in the following cases: - Mouse Switch off then on - Mouse inactivity (leaving the notebook for 5/10 minutes) - Notebook sleep - Notebook reboot The bluetooth mouse can't reconnect. I have to reboot or "systemctl restart bluetooth" and run the pair again. syslog relevant messages during notebook idle: May 7 15:34:42 alastor /usr/lib/gdm3/gdm-x-session[1748]: (II) config/udev: removing device BM30X mouse May 7 15:34:42 alastor /usr/lib/gdm3/gdm-x-session[1748]: (**) Option "fd" "113" May 7 15:34:42 alastor /usr/lib/gdm3/gdm-x-session[1748]: (II) event16 - BM30X mouse: device removed May 7 15:34:42 alastor /usr/lib/gdm3/gdm-x-session[1748]: (II) UnloadModule: "libinput" May 7 15:34:42 alastor /usr/lib/gdm3/gdm-x-session[1748]: (II) systemd-logind: releasing fd for 13:80 May 7 15:34:42 alastor upowerd[1118]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:0A5C:4503.0005 syslog relevant messages activating the notebook: May 7 15:42:36 alastor bluetoothd[13044]: Can't get HIDP connection info May 7 15:42:41 alastor kernel: [14272.937283] Bluetooth: hci0: last event is not cmd complete (0x0f) May 7 15:42:41 alastor bluetoothd[13044]: connect error: Host is down (112) lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4) 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) 05:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 8087:07dc Intel Corp. <-- Bletooth controller Bus 001 Device 004: ID 0bda:5719 Realtek Semiconductor Corp. Bus 001 Device 003: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc.
[Touch-packages] [Bug 1751252] Proposed package upload rejected
An upload of ubiquity to bionic-proposed has been rejected from the
upload queue for the following reason: "All looks good with the package
itself, but sadly there seems to be some leftover .gladep file included
with the changes. Could you reupload without it? Or, if it's needed,
just mention that in the bug? Thank you!".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
In Progress
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
T
[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
@ddstreet - could we get the SRU template information included in this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1769657] [NEW] update toolchain packages for bionic
Public bug reported: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Affects: build-essential (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-7 (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-7-cross (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-7-cross-ports (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-8 (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-8-cross (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-8-cross-ports (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-defaults (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-defaults-ports (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-8 (Ubuntu) Importance: Undecided Status: New ** Also affects: binutils (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-defaults (Ubuntu) Importance: Undecided Status: New ** Also affects: build-essential (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-7-cross (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-7-cross-ports (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-8-cross (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-8-cross-ports (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-defaults-ports (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: New Status in build-essential package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+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 1747411] Re: Change of default database file format to SQL
For corosync the affected components are corosync-qnetd. I checked and without adaption on install they would be fine as they initialize a new DB and nowhere does anyone specify the type. But as with some other tools on an upgrade we have to assume that the old DBM format will be tried to be read as SQL and then fail. Worth to notice is that Fedora who started all of this in [1] in their NSS build still uses DBM as default :-) corosync 2.4.4-1 of 20th of April made corosync compatible with the nss change. They prefix all calls with dbm to stay compat until the upgrade is handled by upstream. So a merge of this or latter version will address this for corosync. Afterwards nss can be merged dropping the change of the default. [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1747411 Title: Change of default database file format to SQL Status in certmonger package in Ubuntu: Fix Released Status in corosync package in Ubuntu: New Status in dogtag-pki package in Ubuntu: Fix Released Status in freeipa package in Ubuntu: Fix Released Status in libapache2-mod-nss package in Ubuntu: Won't Fix Status in nss package in Ubuntu: New Bug description: nss in version 3.35 in upstream changed [2] the default file format [1] (if no explicit one is specified). For now we reverted that change in bug 1746947 until all packages depending on it are ready to work with that correctly. This bug here is about to track when the revert can be dropped. Therefore we list all known-to-be-affected packages and once all are resolved this can be dropped. [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql [2]: https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/certmonger/+bug/1747411/+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 1769637] [NEW] Update evolution-data-server to 3.28.2
Public bug reported: Impact == evolution-data-server (e-d-s) has released a new stable bugfix release. (These will happen about once every month until 3.30 is released in Septebmer) Updating e-d-s is required to update evolution to 3.28.2 (LP: #) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-28 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-28 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. ** Affects: evolution-data-server (Ubuntu) Importance: Low Status: Fix Committed ** Affects: evolution-data-server (Ubuntu Bionic) Importance: Low Status: Triaged ** Tags: bionic upgrade-software-version ** Also affects: evolution-data-server (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu Bionic) Status: New => Triaged ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1769637 Title: Update evolution-data-server to 3.28.2 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Bionic: Triaged Bug description: Impact == evolution-data-server (e-d-s) has released a new stable bugfix release. (These will happen about once every month until 3.30 is released in Septebmer) Updating e-d-s is required to update evolution to 3.28.2 (LP: #) https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-28 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-28 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1769637/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
@cyphermox, has there been any proper solution of this since then? Is the patch still needed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
>None of the packages which you are having an issue with are ones from the official Ubuntu archive, subsequently there is nothing we (the developers of Ubuntu) can do about this. You'll need to take up the issue with the people who develop these packages. Maybe considering whether to break Slack and Virtualbox is a nice idea when updating libraries for an LTS. Just a thought. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1769616] Re: pc no stop
*** This bug is a duplicate of bug 1769615 *** https://bugs.launchpad.net/bugs/1769615 ** This bug has been marked a duplicate of bug 1769615 pc no stop -- 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/1769616 Title: pc no stop Status in xorg package in Ubuntu: New Bug description: mon ne veut pas s'arrêter merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon May 7 12:21:19 2018 DistUpgraded: 2018-05-02 15:20:23,031 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] [174b:2150] InstallationDate: Installed on 2016-12-17 (505 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3210 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-02 (4 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: P01-B2 dmi.board.name: WMCP78M dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3210 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon May 7 12:12:39 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB RECEIVER MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769616/+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 1769616] [NEW] pc no stop
Public bug reported: mon ne veut pas s'arrêter merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon May 7 12:21:19 2018 DistUpgraded: 2018-05-02 15:20:23,031 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] [174b:2150] InstallationDate: Installed on 2016-12-17 (505 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3210 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-02 (4 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: P01-B2 dmi.board.name: WMCP78M dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3210 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon May 7 12:12:39 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB RECEIVER MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769616 Title: pc no stop Status in xorg package in Ubuntu: New Bug description: mon ne veut pas s'arrêter merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon May 7 12:21:19 2018 DistUpgraded: 2018-05-02 15:20:23,031 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] [174b:2150] InstallationDate: Installed on 2016-12-17 (505 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3210 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-02 (4 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: P01-B2 dmi.board.name: WMCP78M dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3210 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I just tested the thing in #123 and I can only conclude: i am writing this note in 18.04 with nvidia-396 drivers on a Lenovo Y720. So I can only agree to what Thijs says. This sounds like a timing problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1650389] Re: Installing snapd on 14.04.5 desktop downgrades xorg et al.
I'm marking this as invalid as it seems to be a bug specific to systemd packaging, not to snapd per se. ** Changed in: snappy Status: Confirmed => Invalid -- 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/1650389 Title: Installing snapd on 14.04.5 desktop downgrades xorg et al. Status in Snappy: Invalid Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Trusty: Fix Committed Bug description: When trying to install the latest snapd on a 14.04.5 desktop image, the installation of systemd (as a dependency of snapd) triggers a whole bunch of downgrades as systemd-shim is removed and replaced with systemd. We have to adjust the packaging such that installation of systemd does not trigger such behavior for packages depending on systemd-shim in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1650389/+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 1769615] [NEW] pc no stop
Public bug reported: mon pc ne veut pas s'arrêter Merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon May 7 12:14:55 2018 DistUpgraded: 2018-05-02 15:20:23,031 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] [174b:2150] InstallationDate: Installed on 2016-12-17 (505 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3210 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-02 (4 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: P01-B2 dmi.board.name: WMCP78M dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3210 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon May 7 12:12:39 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB RECEIVER MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769615 Title: pc no stop Status in xorg package in Ubuntu: New Bug description: mon pc ne veut pas s'arrêter Merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon May 7 12:14:55 2018 DistUpgraded: 2018-05-02 15:20:23,031 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] [174b:2150] InstallationDate: Installed on 2016-12-17 (505 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3210 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-02 (4 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: P01-B2 dmi.board.name: WMCP78M dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3210 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
Re: [Touch-packages] [Bug 1769029] Re: Display on Dell 1440x900 is not available
And now it is working on Dell 1440x900. Thanks a lot for the immediate support. -VK Joseph On Sat, May 5, 2018 at 12:29 PM, Launchpad Bug Tracker < 1769...@bugs.launchpad.net> wrote: > Status changed to 'Confirmed' because the bug affects multiple users. > > ** Changed in: xorg (Ubuntu) >Status: New => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1769029 > > Title: > Display on Dell 1440x900 is not available > > Status in xorg package in Ubuntu: > Confirmed > > Bug description: > Monitor resolution is limited to 1024x768 with no option for higher > resolution > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri May 4 09:44:54 2018 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] > (rev 02) (prog-if 00 [VGA controller]) > Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics > Controller [1458:d000] > InstallationDate: Installed on 2018-05-03 (0 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > Lsusb: >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_IN >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic > root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash > vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/26/2007 > dmi.bios.vendor: Award Software International, Inc. > dmi.bios.version: FG > dmi.board.name: 945GZM-S2 > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007: > svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr: > rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr: > cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: > dmi.product.name: 945GZM-S2 > dmi.sys.vendor: Gigabyte Technology Co., Ltd. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.91-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769029/+subscriptions > -- 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/1769029 Title: Display on Dell 1440x900 is not available Status in xorg package in Ubuntu: Confirmed Bug description: Monitor resolution is limited to 1024x768 with no option for higher resolution ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 4 09:44:54 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root
[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0%
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135278/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135276/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135275/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135277/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135274/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135273/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1769075/+attachment/5135271/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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
