[Touch-packages] [Bug 1794022] [NEW] [Inspiron 15-3567, Realtek ALC3246, Black Headphone Out, Front] No sound at all from Ear phones.
Public bug reported: I was having trouble getting any audio into my Ear phones. It happened only today. It was working till yesterday. I have tried command in terminal "alsactl restore" when I faced similar problem before. But now this didn't work. Please help me. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sashi 4207 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:30:47 2018 InstallationDate: Installed on 2018-05-08 (138 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1648 F pulseaudio sashi 4207 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 15-3567, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05269N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd06/05/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn05269N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1794022 Title: [Inspiron 15-3567, Realtek ALC3246, Black Headphone Out, Front] No sound at all from Ear phones. Status in alsa-driver package in Ubuntu: New Bug description: I was having trouble getting any audio into my Ear phones. It happened only today. It was working till yesterday. I have tried command in terminal "alsactl restore" when I faced similar problem before. But now this didn't work. Please help me. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sashi 4207 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:30:47 2018 InstallationDate: Installed on 2018-05-08 (138 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1648 F pulseaudio sashi 4207 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 15-3567, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05269N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd06/05/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn05269N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1794022/+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 1794018] Re: graphics problem
you're using the HWE stack, try x-x-v-intel-hwe-16.04 instead ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1794018 Title: graphics problem Status in xorg package in Ubuntu: Invalid Bug description: when I type this sudo apt-get install xserver-xorg-video-intel It's showing below results Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>= 2:1.17.99.902) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 24 11:53:44 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:832a] InstallationDate: Installed on 2018-02-07 (228 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5180 Quanta Computer, Inc. Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs1xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=7dedbb81-ba0d-434b-a5b4-8d89a4e31a00 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.46 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.32:bd11/23/2017:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.46:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-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: Mon Sep 24 11:07:41 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794018/+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 1793837] Re: xorg gives low resolution on HDMI port
You probably need to file it upstream at bugs.freedesktop.org (DRI; DRM/Intel) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1793837 Title: xorg gives low resolution on HDMI port Status in linux package in Ubuntu: Confirmed Bug description: This is a Zotac CI547 box. It has to video outputs: one HDMI and one DisplayPort. The HDMI port appears as DP-1 in the logs, the DisplayPort as DP-2. The hardware is Intel HD 620 and is allegedly able to run two displays simultaneously at 4K. I have one WQHD monitor (=2560x1440) and I get that full resolution over the DisplayPort. However, I would like to also get that resolution over the HDMI port (in order to connect two identical monitors), but over HDMI I only get 1024x768. Updating the kernel to the latest 4.18.8 using UKUU made no difference. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.18.8-041808-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat Sep 22 00:21:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 620 [8086:] InstallationDate: Installed on 2018-09-19 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ZOTAC ZBOX-CI527/CI547 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.8-041808-generic root=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef ro quiet splash acpi_backlight=native pci=nomsi resume=UUID=a3c0f54d-b5ae-4a0f-89ec-8e47ad34e2ef resume_offset=34816 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B331P206 dmi.board.asset.tag: NA dmi.board.name: ZBOX-CI527/CI547 dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB331P206:bd04/25/2017:svnZOTAC:pnZBOX-CI527/CI547:pvrXX:rvnZOTAC:rnZBOX-CI527/CI547:rvrXX:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-CI527/CI547 dmi.product.sku: NA dmi.product.version: XX dmi.sys.vendor: ZOTAC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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/linux/+bug/1793837/+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 1605811] Re: x11 crashes
try 18.04 or newer, if you have issues file a new bug with 'ubuntu-bug xorg' ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1605811 Title: x11 crashes Status in xorg package in Ubuntu: Invalid Bug description: somehow during update or something we have like very unstable x11 pulled in. also affects stretch upstream. the desire is for the video driver, open or else.ABOVE jessie or 15.10. Well I had the else(force freeze x117), a kernel update to 4.6 broke it, so I went open. hassle but not a big deal. Obviously this means reinstalling x118. Ok. -or so I thought. x118 with kernel 4.6 somehow breaks all of the x11 depends, so NO driver will load and x11 complains its (now bleeding) head off, and wont load. If it loads at all, im impressed. vesa-fail fbdev-fail ati-fail radeon-fail and a few other drivers --all depends of radeon ati... Its not ramdom gibberish to me but what it entails is that X11 CANT load as the video driver is broken at every depends level for the ati driver at least, mayhaps the entire x11 video driver subsystem.Its looks to someone like something didnt get linked correctly. Those sorts of errors. xyz missing from yada yada... X11 cant load...but CANT is never in programmer vocabulary.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1605811/+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 1793755] Re: [FFe] Feature freeze exception for Mir 1.0
I see it does have some reverse-depends (ubuntu-app-launch, libsdl2 etc), but none of them are seeded (or even in main) so it seems safe to release (indeed if no ABI/API has been broken). The package is in 'supported' so please be sure it doesn't introduce any visible regressions. FFe approved. ** Changed in: mir (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mir (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1793755 Title: [FFe] Feature freeze exception for Mir 1.0 Status in mir package in Ubuntu: Triaged Bug description: We'd like to get Mir 1.0 into Cosmic. It has no rdepends in the archive, but is used *from* the archive for snap builds, and we want the latest release available there. (Somewhat surprisingly!) No ABI changes in this release. The debian/changelog is maintained by us; it's a good overview of the changes. The relevant sections are: - New features . [Wayland] A configuration mechanism to select the Wayland extensions . [Wayland] Support XDG shell stable . [Wayland] Improve protocol scanner . [libmiral] Display configuration file support . [libmiral] Make the pid of external clients available . [libmiral] Add DisplayConfiguration . [console] Ensure the_console_services() is constructed only once . [console] An option to select the ConsoleServices provider . [mir-demos] Move legacy binaries out of mir-demos package . [mir-test-tools] Drop internal test binaries from mir-test-tools package . [X11] Experimental X11 support via Xwayland - Bugs fixed: . [Wayland] creating a shell_surface should associate a role immediately. (Fixes #512) . [Wayland] Default for positioner gravity . [Wayland] Use miral test framework for wlcs tests . [Wayland] Send popup configure events . [Wayland] When setting the pointer cursor apply it. (Fixes #555) . [Wayland] Hook the OutputManager into display reconfiguration notifications. (Fixes #585) . [Wayland] Remove hard coded values for output geometry (screen orientation and pixel arrangement). (Fixes #601) . [miral-kiosk] Don't allow apps to specify size of "maximized" windows. (Fixes #454) . [Mir-on-X] Fixed keyboard grab issue on Arch. (Fixes #549) . [eglstream-kms] Platform re-enabled, but no GL client support . [console] Fix VT switching with LinuxVirtualTerminal. (Fixes #499) . [console] Avoid breaking X11 desktops that have not claimed the VT from logind. (Fixes #535, #539) . [console] LogindConsoleServices: Support VT switching. (Fixes #459) . [libmiral] Parents of the active window also have focus. (Fixes #522) . Fix "sanitize" builds . Racy shutdown in miral-tests and miral_wlcs_tests. (Fixes #543) . Fix a locale initialization crash on musl . [mesa] Use both id and drm_fd as output identifier for cursor buffer as we're not sure of the uniqueness of either. (Fixes #556) . [mesa] Disconnected hardware has no modes: invent a (slow) refresh rate. (Fixes #587) . [input] Guess output for touchscreen (works with one of each). (Fixes #605) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1793755/+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 1784514] Re: Update evolution-data-server to 3.28.5
This bug was fixed in the package evolution-data-server - 3.28.5-0ubuntu0.18.04.1 --- evolution-data-server (3.28.5-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1784514) -- Jeremy Bicha Tue, 31 Jul 2018 10:14:54 -0400 ** Changed in: evolution-data-server (Ubuntu Bionic) 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/1784514 Title: Update evolution-data-server to 3.28.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Bionic: Fix Released Bug description: Impact == 3.28.5 is the final scheduled bug fix release in the 3.28 series. Updating e-d-s is required to update evolution to 3.28.5 (LP: #1784522) https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/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/1784514/+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 1794053] [NEW] pkgCacheFile unlocks in destructor even if it did not acquire lock
Public bug reported:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly breaks
ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens a
cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That said,
any potential regression should be easily noticable, as it would be a
case of not unlocking where we were unlocking before.
** Affects: apt (Ubuntu)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Affects: apt (Ubuntu Trusty)
Importance: High
Status: Triaged
** Affects: apt (Ubuntu Xenial)
Importance: High
Status: Triaged
** Affects: apt (Ubuntu Bionic)
Importance: High
Status: Triaged
** Affects: apt (Ubuntu Cosmic)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Status: New => In Progress
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Cosmic)
Importance: High
Assignee: Julian Andres Klode (juliank)
Status: In Progress
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: apt (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: apt (Ubuntu Trusty)
Status: New => Triaged
** Changed in: apt (Ubuntu Xenial)
Status: New => Triaged
** Changed in: apt (Ubuntu Bionic)
Status: New => Triaged
--
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/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
In Progress
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Triaged
Status in apt source package in Bionic:
Triaged
Status in apt source package in Cosmic:
In Progress
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+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 1793755] Re: [FFe] Feature freeze exception for Mir 1.0
I thought sdl2 dropped the Mir dependency back in 18.04? It hasn't worked since the "Mir EGL" patch was dropped from mesa. Anyway, I have tested some SDL2 apps with Mir 1.0.0: On 16.04 where the SDL_VIDEODRIVER=mir option is still supported they work with it. On 18.04 and 18.10 they work with SDL_VIDEODRIVER=wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1793755 Title: [FFe] Feature freeze exception for Mir 1.0 Status in mir package in Ubuntu: Triaged Bug description: We'd like to get Mir 1.0 into Cosmic. It has no rdepends in the archive, but is used *from* the archive for snap builds, and we want the latest release available there. (Somewhat surprisingly!) No ABI changes in this release. The debian/changelog is maintained by us; it's a good overview of the changes. The relevant sections are: - New features . [Wayland] A configuration mechanism to select the Wayland extensions . [Wayland] Support XDG shell stable . [Wayland] Improve protocol scanner . [libmiral] Display configuration file support . [libmiral] Make the pid of external clients available . [libmiral] Add DisplayConfiguration . [console] Ensure the_console_services() is constructed only once . [console] An option to select the ConsoleServices provider . [mir-demos] Move legacy binaries out of mir-demos package . [mir-test-tools] Drop internal test binaries from mir-test-tools package . [X11] Experimental X11 support via Xwayland - Bugs fixed: . [Wayland] creating a shell_surface should associate a role immediately. (Fixes #512) . [Wayland] Default for positioner gravity . [Wayland] Use miral test framework for wlcs tests . [Wayland] Send popup configure events . [Wayland] When setting the pointer cursor apply it. (Fixes #555) . [Wayland] Hook the OutputManager into display reconfiguration notifications. (Fixes #585) . [Wayland] Remove hard coded values for output geometry (screen orientation and pixel arrangement). (Fixes #601) . [miral-kiosk] Don't allow apps to specify size of "maximized" windows. (Fixes #454) . [Mir-on-X] Fixed keyboard grab issue on Arch. (Fixes #549) . [eglstream-kms] Platform re-enabled, but no GL client support . [console] Fix VT switching with LinuxVirtualTerminal. (Fixes #499) . [console] Avoid breaking X11 desktops that have not claimed the VT from logind. (Fixes #535, #539) . [console] LogindConsoleServices: Support VT switching. (Fixes #459) . [libmiral] Parents of the active window also have focus. (Fixes #522) . Fix "sanitize" builds . Racy shutdown in miral-tests and miral_wlcs_tests. (Fixes #543) . Fix a locale initialization crash on musl . [mesa] Use both id and drm_fd as output identifier for cursor buffer as we're not sure of the uniqueness of either. (Fixes #556) . [mesa] Disconnected hardware has no modes: invent a (slow) refresh rate. (Fixes #587) . [input] Guess output for touchscreen (works with one of each). (Fixes #605) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1793755/+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 1794053] Re: pkgCacheFile unlocks in destructor even if it did not acquire lock
** Changed in: apt (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
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/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Triaged
Status in apt source package in Bionic:
Triaged
Status in apt source package in Cosmic:
Fix Committed
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+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 1794043] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: upgrade from ubuntu 16.10 to new LTS 18.10.04 i think ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 24 05:49:36 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-11-29 (1394 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1794043 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: upgrade from ubuntu 16.10 to new LTS 18.10.04 i think ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 24 05:49:36 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-11-29 (1394 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1794043/+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 1574347] Re: WiFi networks list disappears (device type not reloaded)
wifi disconnects frequently -- 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/1574347 Title: WiFi networks list disappears (device type not reloaded) Status in NetworkManager: Fix Released Status in OEM Priority Project: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: 💥 WARNING 💥 If you are still experiencing this bug please don't comment here, but look at these: (https://goo.gl/LdPpYG) ** HOW TO REPRODUCE ** Boot the system. RESULT From time to time, some of these happen: - The applet doesn't list any wireless network. - The applet doesn't show the name of the current network. - The icon shows the wired connection symbol, instead of the wifi one. * WORK AROUND * (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues) * FIX * The applet needs to re-read the DEVTYPE after the device name changed. *** HOW TO TEST A FIX *** In the Terminal application enter: nmcli dev If it works, in the line for the wireless device, the TYPE column should be "wifi". If it doesn't it will be "ethernet". To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1784514] Update Released
The verification of the Stable Release Update for evolution-data-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1784514 Title: Update evolution-data-server to 3.28.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Bionic: Fix Released Bug description: Impact == 3.28.5 is the final scheduled bug fix release in the 3.28 series. Updating e-d-s is required to update evolution to 3.28.5 (LP: #1784522) https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/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/1784514/+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 1793726] Re: bluetooth device "disappears", rtl 8822, combo wifi + bt
** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1793726 Title: bluetooth device "disappears", rtl 8822, combo wifi + bt Status in bluez package in Ubuntu: New Bug description: The BT part of mobo mounted combo device rtl 8822 with wifi and BT disappears sometimes. Wifi seems to work without problems. BT can just seem to disappear. I have not found a way to reinitialize it. Rebooting "sometimes" works. BT can work fine for a while, then suddenly disappear. Booting into Fedora 28, BT has always been present. Upon booting back into Mint 19, BT is present here too. In the cases when BT has disappeared, bluetooth manager applet says "no adapters". bluetoothctl: power on does not work. linux-firmware/bionic-updates,bionic-updates,now 1.173.1 linux-image-4.15.0-34-generic/bionic-updates,bionic-security,now 4.15.0-34.37 amd64 when working: $ lsmod | grep 8822 r8822be 851968 0 mac80211 778240 1 r8822be cfg80211 622592 2 mac80211,r8822be $ lsmod | grep btusb btusb 45056 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel16384 1 btusb bluetooth 548864 43 btrtl,btintel,bnep,btbcm,rfcomm,btusb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 InstallationDate: Installed on 2018-09-05 (15 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP OMEN X by HP Desktop PC 900-2XX NonfreeKernelModules: nvidia_modeset nvidia Package: bluez 5.48-0ubuntu3.1 [origin: Ubuntu] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=928f0c4b-9a59-45d0-a6d9-f0c36f073288 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: tara third-party-packages Uname: Linux 4.15.0-34-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/16/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.name: 839F dmi.board.vendor: HP dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.21:bd05/16/2018:svnHP:pnOMENXbyHPDesktopPC900-2XX:pvr:rvnHP:rn839F:rvr1.0:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M OMEN X dmi.product.name: OMEN X by HP Desktop PC 900-2XX dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 90:32:4B:90:93:6A ACL MTU: 1021:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:2521415 acl:87 sco:0 events:188278 errors:0 TX bytes:145780806 acl:163568 sco:0 commands:2186 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1793726/+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 1792873] Re: FFE: 18.2.x for cosmic
** Changed in: mesa (Ubuntu) Status: Triaged => New -- 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/1792873 Title: FFE: 18.2.x for cosmic Status in mesa package in Ubuntu: New Bug description: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 1794078] [NEW] Rebooting / booting and battery charging
Public bug reported: Does not reboot and battery does not charge fully. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 24 08:41:54 2018 DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir6,2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0107.B00.180437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0107.B00.180437:bd04/11/2018:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 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.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 Sep 24 08:29:25 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 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/1794078 Title: Rebooting / booting and battery charging Status in xorg package in Ubuntu: New Bug description: Does not reboot and battery does not charge fully. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 24 08:41:54 2018 DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir6,2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0107.B00.180437 dmi.board.
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
all cross packages now built, and installable. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports 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 Status in binutils source package in Bionic: Fix Committed Status in cross-toolchain-base source package in Bionic: Fix Committed Status in cross-toolchain-base-ports source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: 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 [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. 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 1793092] Re: [FFe] openssl 1.1.1
** Tags added: block-proposed -- 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/1793092 Title: [FFe] openssl 1.1.1 Status in openssl package in Ubuntu: Confirmed Bug description: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Resulting in the following changes in Ubuntu: - openssl moves from 1.1.0 series to 1.1.1 LTS series - TLS1.3 is enabled, and used by default, when possible. Major feature. - All existing delta, and minimally accepted key sizes, and minimally accepted protocol versions remain the same. Proposed package is in https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of all the reverse dependencies. It demonstrates that openssl compiled as above is more compatible and has less issues than debian config. There are a few FTBFS, which are also present in cosmic-release; there are some test-suite expectations mismatch (connectivity succeeds with tls1.3 even though lower/different algos are expected); there are very little connectivity tests thus connectivity interop are the biggest issues which will be unavoidable with introducing 1.3. === Ubuntu delta summary versus debian unstable in this merge: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Further decrease security level from 1 to 0, for compatibility with openssl 1.0.2. These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/bionic/cosmic releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Test build of xkeyboard-config available here: https://launchpad.net/~gunnarhj/+archive/ubuntu/xkeyboard-config Not sure it makes a difference wrt airplane mode, though. Please feel free to test, Mario. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Triaged Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1789924] Re: Missing Intel GPU pci-id's
Hello Timo, or anyone else affected, Accepted xorg-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.19.6-1ubuntu4.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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: Fix Committed Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state
** Changed in: ubuntu-power-systems Status: Incomplete => Triaged -- 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/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Triaged Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 0e4f79d56818 [ 73.058099] GPR20: 0e4f79d8d5d8 0001 7efce644 [ 73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 0002
Re: [Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
I've found that just sticking with kernel 4.13 has been working fine for me. It works around this problem and for my use case hasn't had any downsides. On Sun, Sep 23, 2018 at 2:15 PM SB <1759...@bugs.launchpad.net> wrote: > why is this still not fixed, it is quite a showstopper on dell systems > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1759836 > > Title: > systemd-udevd consumes 100% of CPU > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions > -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1794104] [NEW] Xorg crash on first boot after apt upgrade
Public bug reported: I installed a daily snapshot of 18.10 in a VM. After removing some unneccessary application, I ran apt update apt upgrade and rebooted. I noticed X crashing after the reboot, taking me back to the login manager. I have the option selected to automatically login without password. X did not crash when coming up the second time, tough. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: CompositorRunning: None Date: Mon Sep 24 15:54:18 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 5.2.18, 4.18.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-09-14 (10 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=ecdea6ce-6b53-45e4-ac1e-1caae18058d5 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic crash regression single-occurrence ubuntu ** Attachment added: "core file" https://bugs.launchpad.net/bugs/1794104/+attachment/5192428/+files/core.xz -- 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/1794104 Title: Xorg crash on first boot after apt upgrade Status in xorg package in Ubuntu: New Bug description: I installed a daily snapshot of 18.10 in a VM. After removing some unneccessary application, I ran apt update apt upgrade and rebooted. I noticed X crashing after the reboot, taking me back to the login manager. I have the option selected to automatically login without password. X did not crash when coming up the second time, tough. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: CompositorRunning: None Date: Mon Sep 24 15:54:18 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 5.2.18, 4.18.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-09-14 (10 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=ecdea6ce-6b53-45e4-ac1e-1caae18058d5 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: d
[Touch-packages] [Bug 1794104] Re: Xorg crash on first boot after apt upgrade
(gdb) bt full
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {171515904, 0, 0, 0, 0, 94870821356889, 94870821322000,
67108868, 140427223543248, 0, 0, 978464917824351488, 54, 94870838790880,
140727493513216, 140427243872632}}
pid =
tid =
ret =
#1 0x7fb7c2a90535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x36, sa_sigaction = 0x36},
sa_mask = {__val = {94870838790880, 140727493513216, 140427243872632, 1, 384,
0, 978464917824351488, 206158430256, 94870821333191,
171515904, 0, 0, 67108868, 140427223543248, 978464917824351488,
0}}, sa_flags = -711032432, sa_restorer = 0x7ffdac42d0f0}
sigs = {__val = {32, 0 }}
#2 0x5648d59ae96a in OsAbort ()
No symbol table info available.
#3 0x5648d59b4473 in ?? ()
No symbol table info available.
#4 0x5648d59b52d9 in FatalError ()
No symbol table info available.
#5 0x5648d59abd81 in ?? ()
No symbol table info available.
#6
No locals.
#7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 94870844899072, 0, 140427222016815,
18446744073637036032, 94870844899072, 94870844899173, 94870844899072,
94870844899072, 94870844899180, 94870844899372, 94870844899072, 94870844899372,
0,
0, 0}}
pid =
tid =
ret =
#8 0x7fb7c2a90535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x5648d72c5880, sa_sigaction
= 0x5648d72c5880}, sa_mask = {__val = {0, 6, 5, 0, 0, 0, 140727493515688,
21474836480, 140727493515536, 140427223237216,
140427223222360, 0, 978464917824351488, 140427223207162, 0,
140427223222360}}, sa_flags = -711201992, sa_restorer = 0x5648d59beb7d}
sigs = {__val = {32, 0 }}
#9 0x7fb7c2a9040f in __assert_fail_base (fmt=0x7fb7c2c1c858 "%s%s%s:%u:
%s%sAssertion `%s' failed.\n%n", assertion=0x5648d59beb7d
"!global_keys[type].created", file=0x5648d59beb38 "../../../../dix/privates.c",
line=384, function=) at assert.c:92
str = 0x5648d72c5880 ""
total = 4096
#10 0x7fb7c2aa0142 in __GI___assert_fail (assertion=0x5648d59beb7d
"!global_keys[type].created", file=0x5648d59beb38 "../../../../dix/privates.c",
line=384, function=0x5648d59bede0 "dixRegisterPrivateKey")
at assert.c:101
No locals.
#11 0x5648d586be89 in dixRegisterPrivateKey ()
No symbol table info available.
#12 0x7fb7b98bf529 in glamor_init () from
/usr/lib/xorg/modules/libglamoregl.so
No symbol table info available.
#13 0x7fb7c14a4a2d in ?? () from
/usr/lib/xorg/modules/drivers/modesetting_drv.so
No symbol table info available.
#14 0x7fb7c149cb97 in ?? () from
/usr/lib/xorg/modules/drivers/modesetting_drv.so
No symbol table info available.
#15 0x5648d584dc90 in AddGPUScreen ()
No symbol table info available.
#16 0x5648d58a7d8c in ?? ()
No symbol table info available.
--Type for more, q to quit, c to continue without paging--c
#17 0x5648d58ad5e1 in ?? ()
No symbol table info available.
#18 0x5648d58a9ec9 in ?? ()
No symbol table info available.
#19 0x5648d58aa340 in ?? ()
No symbol table info available.
#20 0x5648d59ac731 in ?? ()
No symbol table info available.
#21 0x5648d59a5983 in WaitForSomething ()
No symbol table info available.
#22 0x5648d584d64c in ?? ()
No symbol table info available.
#23 0x5648d5851846 in ?? ()
No symbol table info available.
#24 0x7fb7c2a9209b in __libc_start_main (main=0x5648d583b5c0, argc=11,
argv=0x7ffdac42ebf8, init=, fini=,
rtld_fini=, stack_end=0x7ffdac42ebe8) at ../csu/libc-start.c:308
self =
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 5132712507193217625,
94870819812816, 140727493520368, 0, 0, 1464229968777368153,
1496638397908963929}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0,
0x7ffdac42ec58, 0x7fb7c45ca190}, data = {prev = 0x0, cleanup = 0x0, canceltype
= -1404900264}}}
not_first_call =
#25 0x5648d583b5fa in _start ()
No symbol table info available.
(gdb)
--
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/1794104
Title:
Xorg crash on first boot after apt upgrade
Status in xorg package in Ubuntu:
New
Bug description:
I installed a daily snapshot of 18.10 in a VM.
After removing some unneccessary application, I ran
apt update
apt upgrade
and rebooted. I noticed X crashing after the reboot, taking me back to the
login manager. I have the option selected to automatically login without
password.
X did not crash when coming up the second time, tough.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.1
[Touch-packages] [Bug 1792873] Re: FFE: 18.2.x for cosmic
I would like to wait with this until the new 18.2.1 version builds. Could you perform some upgrade testing on it and leave a comment about how it went? I'll pick this up tomorrow and we'll decide then. The LLVM 7 part seems like a separate thing though? Since it still doesn't seem to be available, I guess it would require another FFe/NEW, I suppose? Seems a bit bigger, especially so close to release. -- 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/1792873 Title: FFE: 18.2.x for cosmic Status in mesa package in Ubuntu: New Bug description: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I can confirm that the bug is back in initramfs-tools 0.130ubuntu3.3 (it was OK with 0.130ubuntu3.2) The difference is even visible when running update-initramfs -u -k all (on 3.2 you see LVM name, on 3.3 you see UUID). with initramfs-tools 0.130ubuntu3.2: update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/vg_system-lv_swap) I: Set the RESUME variable to override this. => no delay while booting and with initramfs-tools 0.130ubuntu3.3: update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (UUID=c2849fd0-bfeb-11e8-82df-e63cc106402d) I: Set the RESUME variable to override this. => delay 30s while booting -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1794144] [NEW] Ubuntu 14.04 Has experienced an internal error aptd crashed with sigsegv in pkgacqarchive::done ()
Public bug reported: my linux machine is popping up the screen saying Ubuntu 14.04 Has experienced an internal error some details title : aptd crashed with sigsegv in pkgacqarchive::done () apport version 2.14.1-oubuntu3.29 package aptdaemon 1.1.1-1ubuntu3.29 ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1794144 Title: Ubuntu 14.04 Has experienced an internal error aptd crashed with sigsegv in pkgacqarchive::done () Status in apt package in Ubuntu: New Bug description: my linux machine is popping up the screen saying Ubuntu 14.04 Has experienced an internal error some details title : aptd crashed with sigsegv in pkgacqarchive::done () apport version 2.14.1-oubuntu3.29 package aptdaemon 1.1.1-1ubuntu3.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794144/+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 1681249] Re: tracker-extract crashed with signal 31 in chdir()
It is happening for me in Ubuntu 18.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1681249 Title: tracker-extract crashed with signal 31 in chdir() Status in tracker package in Ubuntu: Confirmed Bug description: tracker crash while indexing my homedir ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: tracker-extract 1.12.0-0ubuntu1 Uname: Linux 4.10.8-041008-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 8 14:00:45 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/tracker/tracker-extract ExecutableTimestamp: 1490023113 JournalErrors: No journal files were found. -- No entries -- ProcCmdline: /usr/lib/tracker/tracker-extract ProcCwd: /home/bonnaudl Signal: 31 SourcePackage: tracker Title: tracker-extract crashed with signal 31 in chdir() UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1681249/+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 1794146] [NEW] package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127
Public bug reported: error displays on login through xrdp using xfce4 desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 13:27:41 2018 DuplicateSignature: package:ibus:1.5.17-3ubuntu4 Removing ibus (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not found dpkg: error processing package ibus (--remove): installed ibus package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed ibus package pre-removal script subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: ibus Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1794146 Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127 Status in ibus package in Ubuntu: New Bug description: error displays on login through xrdp using xfce4 desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 13:27:41 2018 DuplicateSignature: package:ibus:1.5.17-3ubuntu4 Removing ibus (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not found dpkg: error processing package ibus (--remove): installed ibus package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed ibus package pre-removal script subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: ibus Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1794146/+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 1794146] Re: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1794146 Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127 Status in ibus package in Ubuntu: New Bug description: error displays on login through xrdp using xfce4 desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Thu Sep 20 13:27:41 2018 DuplicateSignature: package:ibus:1.5.17-3ubuntu4 Removing ibus (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/ibus.prerm: 7: /var/lib/dpkg/info/ibus.prerm: dconf: not found dpkg: error processing package ibus (--remove): installed ibus package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed ibus package pre-removal script subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: ibus Title: package ibus 1.5.17-3ubuntu4 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1794146/+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 1794148] [NEW] Rebooting / booting and battery charging
Public bug reported: charging only to 85% and booting up slow after several trials. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 24 12:38:18 2018 DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir6,2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro drm.debug=0xe plymouth:debug nopat vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0107.B00.180437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0107.B00.180437:bd04/11/2018:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 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.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 Sep 24 12:33:15 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 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/1794148 Title: Rebooting / booting and battery charging Status in xorg package in Ubuntu: New Bug description: charging only to 85% and booting up slow after several trials. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 24 12:38:18 2018 DistUpgraded: 2018-09-23 21:15:55,906 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-34-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-135-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Apple Inc. MacBookAir6,2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=4add3271-ffc7-4961-97a0-f796b33a7d0f ro drm.debug=0xe plymouth:debug nopat vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: Upgr
[Touch-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Thanks, Gunnar. I could not test it yet on the Asus from this bugreport, it will take a few days until I can get my hands on this one. However, I tested with my own Dell XPS 15 9575 and it breaks the Airplane mode switch there, which works perfectly with the standard xkb- data=2.23.1-1ubuntu1 from Cosmic: 2.23.1-1ubuntu1: 1. Press Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Works. Pop-up says "Airplane mode disabled", icon disappears from panel, Wifi and BT are on. Updated 2.24-0ubuntu1, rebooted: 1. Press Fn+Pos1 -> Works same as before. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", icon remains in panel, Wifi and BT remain on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Triaged Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendo
[Touch-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
** Description changed: + To the release team: Asking for FFe since it appears to be a good idea + to fix this bug through an upgrade to latest version of xkeyboard-config + rather than just patching a single upstream commit. + + [Original description] + Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Summary changed: - Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) + [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) ** Description changed: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard-config rather than just patching a single upstream commit. + + Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu + /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, s
[Touch-packages] [Bug 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Sorry for typo in previous comment, should have been OFF at the end: Updated 2.24-0ubuntu1, rebooted: 1. Press Fn+Pos1 -> Works same as before. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", icon remains in panel, Wifi and BT remain *OFF* [not "on"] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:
[Touch-packages] [Bug 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Thanks Mario! That's bad news. Looks like there is more into it then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I have had this problem in the past and it reemerged on an upgrade from 16.04 to 18.04 and have resolved it. For me (Lenovo Yoga) the issue is with USB rewaking the machine. The following fix worked for me. 1) Created file: /etc/systemd/system/toggle.XHC.to.fix.suspend.issue.service with following informaiton [Unit] Description="Make suspend ignore USB wake up." [Service] ExecStart=/bin/bash -c "echo XHC >> /proc/acpi/wakeup" [Install] WantedBy=multi-user.target 2) Created a symbolic link to above script in /etc/systemd/system/multi- user.target.wants 3) Executed following commands sudo systemctl daemon-reload sudo systemctl start toggle.XHC.to.fix.suspend.issue.service 4) checked service was started with sudo systemctl status toggle.XHC.to.fix.suspend.issue.service 5) Enable it on boot with sudo systemctl enable toggle.XHC.to.fix.suspend.issue.service Notes: -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I have had this problem in the past and it reemerged on an upgrade from 16.04 to 18.04 and have resolved it. For me (Lenovo Yoga) the issue is with USB rewaking the machine. The following fix worked for me. 1) Created file: /etc/systemd/system/toggle.XHC.to.fix.suspend.issue.service with following informaiton [Unit] Description="Make suspend ignore USB wake up." [Service] ExecStart=/bin/bash -c "echo XHC >> /proc/acpi/wakeup" [Install] WantedBy=multi-user.target 2) Created a symbolic link to above script in /etc/systemd/system/multi- user.target.wants 3) Executed following commands sudo systemctl daemon-reload sudo systemctl start toggle.XHC.to.fix.suspend.issue.service 4) checked service was started with sudo systemctl status toggle.XHC.to.fix.suspend.issue.service 5) Enable it on boot with sudo systemctl enable toggle.XHC.to.fix.suspend.issue.service Last steps are based on https://www.reddit.com/r/archlinux/comments/3zxg65/how_to_permanently_change_procacpiwakeup_or/ -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
** Patch added: "rebased on 1.12.2-0ubuntu5" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff -- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+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 1794178] [NEW] Install failure
Public bug reported: apt-get install libxext6 Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libxmuu1 Use 'apt autoremove' to remove it. The following NEW packages will be installed: libxext6 0 upgraded, 1 newly installed, 0 to remove and 27 not upgraded. Need to get 29.4 kB of archives. After this operation, 125 kB of additional disk space will be used. Err:1 http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu xenial/main amd64 libxext6 amd64 2:1.3.3-1 Unknown date format Bad header data E: Failed to fetch http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu/pool/main/libx/libxext/libxext6_1.3.3-1_amd64.deb Unknown date format Bad header data E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? ** Affects: libxext (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxext in Ubuntu. https://bugs.launchpad.net/bugs/1794178 Title: Install failure Status in libxext package in Ubuntu: New Bug description: apt-get install libxext6 Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libxmuu1 Use 'apt autoremove' to remove it. The following NEW packages will be installed: libxext6 0 upgraded, 1 newly installed, 0 to remove and 27 not upgraded. Need to get 29.4 kB of archives. After this operation, 125 kB of additional disk space will be used. Err:1 http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu xenial/main amd64 libxext6 amd64 2:1.3.3-1 Unknown date format Bad header data E: Failed to fetch http://xxx.xxx.xxx.xxx:80/data/040d470b23b0f368/archive.ubuntu.com/ubuntu/pool/main/libx/libxext/libxext6_1.3.3-1_amd64.deb Unknown date format Bad header data E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1794178/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I agree. It appears that version 0.130ubuntu3.3 is broken again. When looking at the changelog here: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools /initramfs-tools_0.130ubuntu3.3/changelog ...and comparing it to the changelog at: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools /initramfs-tools_0.130ubuntu3.2/changelog ...it looks like the Steve Langasek's fixes introduced in version 0.130ubuntu3.2 to fix this bug are lost in package version 0.130ubuntu3.3. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Confirmed -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Confirmed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1792873] Re: FFE: 18.2.x for cosmic
LLVM 7 is the default in cosmic :) and mesa 18.2.1 is built now, installs fine from the ppa -- 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/1792873 Title: FFE: 18.2.x for cosmic Status in mesa package in Ubuntu: New Bug description: Mesa 18.2.0 was recently released after several delays, but at least it doesn't have any known regressions on Intel hw. We tend to get the latest major version in the devel series ~2 weeks after FF, but since a month has passed now I thought it would be best to file an actual FFE request. We'd also build it against LLVM 7, which is about to be released. Together these provide support for AMD Vega20 (kernel support still needed) among other things. New features from mesa upstream reldocs: OpenGL 4.3 on virgl OpenGL 4.4 Compatibility profile on radeonsi OpenGL ES 3.2 on radeonsi and virgl GL_ARB_ES3_2_compatibility on radeonsi GL_ARB_fragment_shader_interlock on i965 GL_ARB_sample_locations and GL_NV_sample_locations on nvc0 (GM200+) GL_ANDROID_extension_pack_es31a on radeonsi. GL_KHR_texture_compression_astc_ldr on radeonsi GL_NV_conservative_raster and GL_NV_conservative_raster_dilate on nvc0 (GM200+) GL_NV_conservative_raster_pre_snap_triangles on nvc0 (GP102+) multisampled images on nvc0 (GM107+) (now supported on GF100+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1792873/+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 1746856] Re: usb printer does not print (canon d530)
Hi, Thank you for the email. Prompted by your email I downloaded the latest drivers from canon and installed them. Printer now works! I am so happy. Thanks for checking in. -Alex On Fri, Aug 31, 2018 at 12:25 PM gf <1746...@bugs.launchpad.net> wrote: > Hello Alex, > Thank you for submitting this bug and reporting a problem with cups. You > made this bug report some time ago and Ubuntu and cups have been updated > since then. > > Could you confirm that this is no longer a problem and that we can close > the ticket? > If it is still a problem, are you still interested in finding a solution > to this bug? > If you are, could you let us know and, in the current version, could you > run the following (only once): > apport-collect 1746856 > and upload the updated logs and and any other logs that are relevant for > this particular issue. > > Thank you again for helping make Ubuntu and cups better. > G > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1746856 > > Title: > usb printer does not print (canon d530) > > Status in cups package in Ubuntu: > Incomplete > > Bug description: > Bus 002 Device 005: ID 04a9:2775 Canon, Inc. > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo > Integrated Camera (0.3MP) > Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 > Mouse > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Description: Ubuntu 17.10 > Release: 17.10 > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: cups 2.2.4-7ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 > Uname: Linux 4.13.0-32-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Feb 1 19:14:46 2018 > InstallationDate: Installed on 2018-01-22 (10 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 > (20180105.1) > Lpstat: device for Canon_D530_D560: cnusb:/dev/usb/lp0 > MachineType: LENOVO 4239CTO > Papersize: letter > PpdFiles: Error: command ['fgrep', '-H', '*NickName', > '/etc/cups/ppd/Canon_D530_D560.ppd'] failed with exit code 2: grep: > /etc/cups/ppd/Canon_D530_D560.ppd: Permission denied > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic > root=UUID=1aa4feb1-4b49-43d5-bcce-25b90425a69e ro quiet splash vt.handoff=7 > SourcePackage: cups > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/05/2012 > dmi.bios.vendor: LENOVO > dmi.bios.version: 8AET58WW (1.38 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 4239CTO > 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:bvr8AET58WW(1.38):bd07/05/2012:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.family: ThinkPad T520 > dmi.product.name: 4239CTO > dmi.product.version: ThinkPad T520 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1746856/+subscriptions > -- Alexander Yasbek, P.E. - Civil Engineer 831 334 9054 Wastewater and Water Treatment Projects -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1746856 Title: usb printer does not print (canon d530) Status in cups package in Ubuntu: Incomplete Bug description: Bus 002 Device 005: ID 04a9:2775 Canon, Inc. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP) Bus 001 Device 004: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Description: Ubuntu 17.10 Release: 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: cups 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Fe
[Touch-packages] [Bug 1317386] Re: Script install-css.sh from libdvdread4 is vulnerable to MITM attack
The script is no longer part of libdvdread. ** Changed in: libdvdread (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1317386 Title: Script install-css.sh from libdvdread4 is vulnerable to MITM attack Status in libdvdread package in Ubuntu: Fix Released Bug description: There is install-css.sh in libdvdread4 package which downloads and installs libdvdcss package which is needed for playing of DVDs (those infected by DRM CSS technology – probably most of them). The libdvdcss package is downloaded over unencrypted HTTP protocol and is installed immediately after downloading without any integrity checks. Anybody between the server (download.videolan.org) and the user can modify on-the-fly this package and add some malware/backdoor into it. This installation equals downloading some untrusted code from the Net and executing it with root permissions (the package can containt post-installation script). User is not warned (neither in help https://help.ubuntu.com/community/RestrictedFormats/PlayingDVDs nor interactively by the script) that his computer might be infected. The script MUST verify the digital signature of downloaded package and install it only if it is valid. The package is already signed: http://download.videolan.org/pub/debian/stable/stable/libdvdcss_1.2.13-0.dsc So please verify that the PGP key C0AFF10F (Rafaël Carré) is valid and can be trusted for this purpose. And add signature verification into the install-css.sh script. Please consult with lawyers also other solution: isn't is possible to distribute DeCSS source code instead of downloading it from an external site? So the subject of distribution will be just data, nothing executable. The compilation will be done by the user on his computer (he will run the same script: install-css.sh). It will not be vulnerable to MITM attack – standard methods for package signing and verification will be used – and it will also be independent from Internet connectivity – it will by possible to install it e.g. from CDs on an offline computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1317386/+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 1192042] Re: package libdvdread4 4.2.0+20121016-1ubuntu1 failed to install/upgrade: package libdvdread4 is already installed and configured
** Package changed: libdvdread (Ubuntu) => aptdaemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1192042 Title: package libdvdread4 4.2.0+20121016-1ubuntu1 failed to install/upgrade: package libdvdread4 is already installed and configured Status in aptdaemon package in Ubuntu: Confirmed Bug description: just installed, i dont know what is it, ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libdvdread4 4.2.0+20121016-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Jun 18 14:06:36 2013 DuplicateSignature: package:libdvdread4:4.2.0+20121016-1ubuntu1:package libdvdread4 is already installed and configured ErrorMessage: package libdvdread4 is already installed and configured InstallationDate: Installed on 2013-06-18 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: libdvdread Title: package libdvdread4 4.2.0+20121016-1ubuntu1 failed to install/upgrade: package libdvdread4 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1192042/+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 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
Hello I have the same issue. I tried for a couple days to fix it without any results. I have the latest drivers installed (https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS). I then tried to set all configurations to default and ran alsa-info. The ouput is located at the following url and in the attached text document. I hope this is helpful. http://www.alsa- project.org/db/?f=79aa0cb7023e375b7255e6789c7bd19c26a70d4f thankyou ** Attachment added: "My Sound card information" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+attachment/5192618/+files/alsa_info.txt -- 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/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
I've hit this issue right after upgrading from 16.04 to 18.04
--
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/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+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 1767797] Re: sir my bluetooth is not working .
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1767797 Title: sir my bluetooth is not working . Status in bluez package in Ubuntu: Expired Bug description: sir my bluetooth is not working so can you solve this problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 18:16:13 2018 InstallationDate: Installed on 2018-04-28 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767797/+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 411688] Re: pulseaudio floods network with multicast packets
This ticket was opened 9 years ago. Bug still exists in Ubuntu 16.04.05. /etc/pulse/default.pa ``` load-module module-null-sink sink_name=rtp load-module module-rtp-send source=rtp.monitor set-default-sink rtp ``` This feature still floods the network with packets. Disabling it isn't a fix, its merely opting out of a broken feature. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 000
[Touch-packages] [Bug 1794229] [NEW] python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
Public bug reported: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ** Affects: alembic (Ubuntu) Importance: Critical Status: New ** Affects: astroid (Ubuntu) Importance: Critical Status: New ** Affects: dh-python (Ubuntu) Importance: Critical Status: New ** Affects: debian Importance: Unknown Status: Unknown ** Changed in: dh-python (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: New Status in astroid package in Ubuntu: New Status in dh-python package in Ubuntu: New Status in Debian: Unknown Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+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 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
It appears these packages are in main but mainly pulled in (at least on my system) by 'devscripts'. This affects cosmic. ** Also affects: alembic (Ubuntu) Importance: Undecided Status: New ** Also affects: astroid (Ubuntu) Importance: Undecided Status: New ** Changed in: astroid (Ubuntu) Importance: Undecided => Critical ** Changed in: alembic (Ubuntu) Importance: Undecided => Critical ** Bug watch added: Debian Bug tracker #907871 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907871 ** Also affects: debian via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907871 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: New Status in astroid package in Ubuntu: New Status in dh-python package in Ubuntu: New Status in Debian: Unknown Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+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 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
Looks like the recent astroid rebuild/changes removed the file, but it's still present in alembic ** Changed in: alembic (Ubuntu) Importance: Critical => High ** Changed in: astroid (Ubuntu) Importance: Critical => High ** Changed in: dh-python (Ubuntu) Importance: Critical => High ** Changed in: astroid (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: New Status in astroid package in Ubuntu: Invalid Status in dh-python package in Ubuntu: New Status in Debian: Unknown Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+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 1794231] [NEW] missing driver
Public bug reported: abc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 10:48:44 2018 InstallationDate: Installed on 2017-07-20 (431 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1794231 Title: missing driver Status in xorg package in Ubuntu: New Bug description: abc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 25 10:48:44 2018 InstallationDate: Installed on 2017-07-20 (431 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794231/+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 1794104] Re: Xorg crash on first boot after apt upgrade
install mesa from a ppa: apt-add-repository ppa:canonical-x/x-staging and install updates ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1794104 Title: Xorg crash on first boot after apt upgrade Status in xorg package in Ubuntu: Incomplete Bug description: I installed a daily snapshot of 18.10 in a VM. After removing some unneccessary application, I ran apt update apt upgrade and rebooted. I noticed X crashing after the reboot, taking me back to the login manager. I have the option selected to automatically login without password. X did not crash when coming up the second time, tough. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: CompositorRunning: None Date: Mon Sep 24 15:54:18 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 5.2.18, 4.18.0-7-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-09-14 (10 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=ecdea6ce-6b53-45e4-ac1e-1caae18058d5 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794104/+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
