[Touch-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound
If the problem is that mentioned in comment #14 then indeed it will come and go randomly. Please finish following the steps in comment #14. -- 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/1810861 Title: USB type C audio adapter (from a Pixel 3) doesn't produce any sound Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use a logitech z200 that works fine, i use it with a usb type c adapter that came with my pixel 3, my speakers arent shown at all in the settings or make sound, its not the usb c adapter because it works fine on my windows dual boot and has worked at one point on ubuntu, regardless of the fact that ubuntu has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i use lsusb, one of the results is google inc., which is my headphone adapter, i can tell because when i unplug it it goes away, even when i plug it into the 3.5 mm headphone jack it doesn't work, i don't know if im forgetting something or not, this is the second time im typing this because i accidentally closed the first tab of this, whats interesting, is now that i go to alsamixer, and press f6 i see option 1.Headphone Adapter, i select it and set the volume all the way up and go to something that makes audio and nothing happens, then i unplug it and see if it disappears, surely enough it does --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-21 (78 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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 1811561] Re: their are no additional drivers
I can't see any hardware in your system that requires additional drivers so would expect none to be displayed. Is there some specific driver you expected? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1811561 Title: their are no additional drivers Status in Ubuntu: Incomplete Bug description: their are no additional drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .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: Sun Jan 13 12:31:27 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1085] InstallationDate: Installed on 2018-12-03 (41 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. Bus 001 Device 004: ID 04ca:3014 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=ea0d0eed-c143-43b6-a8de-0a0483dc6598 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: T-Rex_SK dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd08/31/2016:svnAcer:pnAspireES1-572:pvrV1.04:rvnAcer:rnT-Rex_SK:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: SKL dmi.product.name: Aspire ES1-572 dmi.product.version: V1.04 dmi.sys.vendor: Acer 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: Sun Jan 13 12:01:43 2019 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1811561/+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 1811561] [NEW] their are no additional drivers
Public bug reported: their are no additional drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .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: Sun Jan 13 12:31:27 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1085] InstallationDate: Installed on 2018-12-03 (41 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. Bus 001 Device 004: ID 04ca:3014 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=ea0d0eed-c143-43b6-a8de-0a0483dc6598 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: T-Rex_SK dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd08/31/2016:svnAcer:pnAspireES1-572:pvrV1.04:rvnAcer:rnT-Rex_SK:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: SKL dmi.product.name: Aspire ES1-572 dmi.product.version: V1.04 dmi.sys.vendor: Acer 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: Sun Jan 13 12:01:43 2019 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: ubuntu Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1811561 Title: their are no additional drivers Status in Ubuntu: Incomplete Bug description: their are no additional drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .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: Sun Jan 13 12:31:27 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1085] InstallationDate: Installed on 2018-12-03 (41 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:57b3 Realtek Semiconductor Corp. Bus 001 Device 004: ID 04ca:3014 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=ea0d0eed-c143-43b6-a8de-0a0483dc6598 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
This bug is now closed. Please report further issues as new bugs. -- 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/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+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 1811553] [NEW] cron does not expand $USER but should be able to to
Public bug reported: in a script running through crontab I cannot expand $USER, though I can expand $HOME. however $HOME includes $USER therefore CRON should be able to expand $USER if not then CRON is inconsistent ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 13 17:17:18 2019 InstallationDate: Installed on 2019-01-02 (10 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1811553 Title: cron does not expand $USER but should be able to to Status in cron package in Ubuntu: New Bug description: in a script running through crontab I cannot expand $USER, though I can expand $HOME. however $HOME includes $USER therefore CRON should be able to expand $USER if not then CRON is inconsistent ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 13 17:17:18 2019 InstallationDate: Installed on 2019-01-02 (10 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1811553/+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 1803009] Re: cyrus-sasl2 source fails to build
[Expired for cyrus-sasl2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cyrus-sasl2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1803009 Title: cyrus-sasl2 source fails to build Status in cyrus-sasl2 package in Ubuntu: Expired Bug description: apt source cyrus-sasl2 cd cyrus-sasl2-2.1.26.dfsg1 dpkg-buildpackage -rfakeroot -b In amoungst hundreds of warnings, we get this: otp.c:755:17: error: storage size of ‘mdctx’ isn’t known EVP_MD_CTX mdctx; Full Outputs: hacksaw@hacksaw:~/src$ apt source cyrus-sasl2 Reading package lists... Done NOTICE: 'cyrus-sasl2' packaging is maintained in the 'Git' version control system at: git://anonscm.debian.org/pkg-cyrus-sasl2/cyrus-sasl2.git Please use: git clone git://anonscm.debian.org/pkg-cyrus-sasl2/cyrus-sasl2.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 1,592 kB of source archives. Get:1 http://archive.ubuntu.com/ubuntu xenial/main cyrus-sasl2 2.1.26.dfsg1-14build1 (dsc) [3,327 B] Get:2 http://archive.ubuntu.com/ubuntu xenial/main cyrus-sasl2 2.1.26.dfsg1-14build1 (tar) [1,494 kB] Get:3 http://archive.ubuntu.com/ubuntu xenial/main cyrus-sasl2 2.1.26.dfsg1-14build1 (diff) [94.6 kB] Fetched 1,592 kB in 0s (11.6 MB/s) gpgv: Signature made Tue 05 Apr 2016 09:12:33 AM EDT using RSA key ID 75BDD52E gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./cyrus-sasl2_2.1.26.dfsg1-14build1.dsc dpkg-source: info: extracting cyrus-sasl2 in cyrus-sasl2-2.1.26.dfsg1 dpkg-source: info: unpacking cyrus-sasl2_2.1.26.dfsg1.orig.tar.gz dpkg-source: info: unpacking cyrus-sasl2_2.1.26.dfsg1-14build1.debian.tar.xz dpkg-source: info: applying 0001_versioned_symbols.patch dpkg-source: info: applying 0002_testsuite.patch dpkg-source: info: applying 0003_saslauthd_mdoc.patch dpkg-source: info: applying 0005_dbconverter.patch dpkg-source: info: applying 0006_library_mutexes.patch dpkg-source: info: applying 0009_sasldb_al.patch dpkg-source: info: applying 0010_maintainer_mode.patch dpkg-source: info: applying 0011_saslauthd_ac_prog_libtool.patch dpkg-source: info: applying 0012_xopen_crypt_prototype.patch dpkg-source: info: applying 0014_avoid_pic_overwrite.patch dpkg-source: info: applying 0017_db4.8.patch dpkg-source: info: applying 0025_ld_as_needed.patch dpkg-source: info: applying 0026_drop_krb5support_dependency.patch dpkg-source: info: applying 0028_autotools_fixes.patch dpkg-source: info: applying 0029_ldap_fixes.patch dpkg-source: info: applying 0030_dont_use_la_files_for_opening_plugins.patch dpkg-source: info: applying 0031_dont_use_-R_when_search_for_sqlite_libraries.patch dpkg-source: info: applying 0032_revert_1.103_revision_to_unbreak_GSSAPI.patch dpkg-source: info: applying 0033_fix_segfault_in_GSSAPI.patch dpkg-source: info: applying 0034_fix_dovecot_authentication.patch dpkg-source: info: applying 0035_temporary_multiarch_fixes.patch dpkg-source: info: applying 0036_add_reference_to_LDAP_SASLAUTHD_file.patch dpkg-source: info: applying 0038_send_imap_logout.patch dpkg-source: info: applying 0039_fix_canonuser_ldapdb_garbage_in_out_buffer.patch dpkg-source: info: applying 0041_fix_keytab_option_for_MIT_kerberos.patch dpkg-source: info: applying 0042_release_server_creds.patch dpkg-source: info: applying 0043_types_h.patch dpkg-source: info: applying 0044_debug_log_typo_fix.patch dpkg-source: info: applying 0045_revert_upstream_soname_bump.patch dpkg-source: info: applying 0046_fix_void_return.patch dpkg-source: info: applying properly-create-libsasl2.pc.patch dpkg-source: info: applying bug715040.patch dpkg-source: info: applying early-hangup.patch dpkg-source: info: applying CVE-2013-4122.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1803009/+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 1802902] Re: 18.10 gdk-pixbuf-thumbnailer 100% cpu makes system completely unresponsive
[Expired for gdk-pixbuf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdk-pixbuf (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1802902 Title: 18.10 gdk-pixbuf-thumbnailer 100% cpu makes system completely unresponsive Status in gdk-pixbuf package in Ubuntu: Expired Bug description: Nothing gets logged by dmesg or journalctl, and the system suddenly becomes unresponsive so even ttys are slow and unusable. This happened on 3 installs of 18.10. It mostly happens when waking my external monitor but also at random times about every other hour. Despite no logs, I fixed the problem by deleting the folder .cache/thumbnails/fail Don't know why or how this happens and I don't have the log files to upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1802902/+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 1811531] Re: remote execution vulnerability
** Changed in: zeromq3 (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1808109] Re: Upgrade to 1.12
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gpgme1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808109 Title: Upgrade to 1.12 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: GPGme 1.12 was release with a new json help that allows browsers to use gpgme for encryption (see https://www.mailvelope.com/de/blog/mailvelope-3.0 for example). Debian (buster) already includes 1.12 and so should Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1808109/+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 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
I keep getting this with dbus. First on Cosmic (fresh install) regularly, now after update to Disco again. ERROR: apport (pid 17063) Sat Jan 12 23:06:33 2019: wrote report /var/crash/_usr_bin_dbus-daemon.1000.crash ERROR: apport (pid 18123) Sat Jan 12 23:07:21 2019: called for pid 17953, signal 6, core limit 18446744073709551615, dump mode 1 ERROR: apport (pid 18123) Sat Jan 12 23:07:21 2019: ignoring implausibly big core limit, treating as unlimited ** Attachment added: "apport.log" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+attachment/5228764/+files/apport.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Confirmed Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Confirmed Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1784023] Re: Update profiles for usrmerge
Fixed in 2.0+git20181009-2.
** Changed in: surf (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1784023
Title:
Update profiles for usrmerge
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
New
Status in dhcpcanon package in Ubuntu:
New
Status in ejabberd package in Ubuntu:
New
Status in firefox package in Ubuntu:
In Progress
Status in fwknop package in Ubuntu:
New
Status in i2p package in Ubuntu:
New
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in kopanocore package in Ubuntu:
New
Status in libvirt package in Ubuntu:
Fix Released
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
Fix Released
Status in man-db package in Ubuntu:
Fix Released
Status in strongswan package in Ubuntu:
Fix Released
Status in surf package in Ubuntu:
Fix Released
Status in telepathy-mission-control-5 package in Ubuntu:
Fix Released
Status in strongswan package in Debian:
Fix Released
Bug description:
this is about / and /usr merge.
/bin & /sbin merge is out of scope. Anything that was in /sbin/ will
remain in /{,usr/}sbin/.
= src:apparmor =
usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles
upstream git tree
/usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs
= other packages =
Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/
$ sudo grep '[[:space:]]/bin' -r .
./usr.bin.man: /bin/bzip2 rmCx -> _filter,
./usr.bin.man: /bin/gzip rmCx -> _filter,
./usr.bin.man: /bin/bzip2 rm,
./usr.bin.man: /bin/gzip rm,
./usr.sbin.libvirtd: /bin/* PUx,
./abstractions/lightdm: /bin/ rmix,
./abstractions/lightdm: /bin/fusermount Px,
./abstractions/lightdm: /bin/** rmix,
./abstractions/libvirt-qemu: /bin/uname rmix,
./abstractions/libvirt-qemu: /bin/grep rmix,
./usr.bin.chromium-browser: /bin/ps Uxr,
./usr.bin.chromium-browser:/bin/dash ixr,
./usr.bin.chromium-browser:/bin/grep ixr,
./usr.bin.chromium-browser:/bin/readlink ixr,
./usr.bin.chromium-browser:/bin/sed ixr,
./usr.bin.chromium-browser:/bin/which ixr,
./usr.bin.chromium-browser:/bin/mkdir ixr,
./usr.bin.chromium-browser:/bin/mv ixr,
./usr.bin.chromium-browser:/bin/touch ixr,
./usr.bin.chromium-browser:/bin/dash ixr,
./usr.bin.firefox: /bin/which ixr,
./usr.bin.firefox: /bin/ps Uxr,
./usr.bin.firefox: /bin/uname Uxr,
./usr.bin.firefox:/bin/dash ixr,
./sbin.dhclient: /bin/bash mr,
$ sudo grep '[[:space:]]/sbin' -r .
./usr.lib.telepathy:deny /sbin/ldconfig x,
./usr.sbin.libvirtd: /sbin/* PUx,
./abstractions/lightdm: /sbin/ r,
./abstractions/lightdm: /sbin/** rmixk,
./usr.bin.firefox: /sbin/killall5 ixr,
./sbin.dhclient: /sbin/dhclient mr,
./sbin.dhclient: # daemon to run arbitrary code via /sbin/dhclient-script,
it would need to be
./sbin.dhclient: /sbin/dhclient-script Uxr,
$ sudo grep '[[:space:]]/lib' -r .
./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr,
# drop
./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
./abstractions/lightdm: /lib/ r,
./abstractions/lightdm: /lib/** rmixk,
./abstractions/lightdm: /lib32/ r,
./abstractions/lightdm: /lib32/** rmixk,
./abstractions/lightdm: /lib64/ r,
./abstractions/lightdm: /lib64/** rmixk,
./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,
above list might be incomplete
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1784023/+subscriptions
--
Mailing list:
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
The attachment "backported patch for 4.2.5" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Unknown Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
Could this be SRU'ed into Bionic? 18.04LTS currently has version 1.1, so the "Reading database ..." lines will otherwise afflict it for quite some time to come. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt package in Debian: New Bug description: This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+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 1811531] Re: remote execution vulnerability
Launchpad has imported 1 comments from the remote bug at https://bugzilla.opensuse.org/show_bug.cgi?id=1121717. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-01-12T17:40:09+00:00 Luca Boccassi wrote: Created attachment 794269 patch for 4.2.2 and 4.2.3 Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch for 4.2.3 (leap 15) and 4.2.2 (leap 42) (applies cleanly on both). This issue has been introduced in 4.2.0 so SLES 12 is not affected. The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. Reply at: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/comments/3 ** Changed in: zeromq (Suse) Status: Unknown => Confirmed ** Changed in: zeromq (Suse) Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Unknown Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531] Re: remote execution vulnerability
** Description changed: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. + + [1] https://github.com/zeromq/libzmq/issues/3351 ** Bug watch added: Debian Bug tracker #919098 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919098 ** Also affects: zeromq3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919098 Importance: Unknown Status: Unknown ** Bug watch added: bugzilla.opensuse.org/ #1121717 https://bugzilla.opensuse.org/show_bug.cgi?id=1121717 ** Also affects: zeromq (Suse) via https://bugzilla.opensuse.org/show_bug.cgi?id=1121717 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Unknown Status in zeromq package in Suse: Unknown Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811149] Re: 23 wireguard peers hang systemd-networkd
** Changed in: systemd Status: Unknown => New -- 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/1811149 Title: 23 wireguard peers hang systemd-networkd Status in systemd: New Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 18.04.1 LTS with systemd=237-3ubuntu10.9. Linux kernel version is 4.15.0-32-generic #35-Ubuntu SMP. wireguard=0.0.20181218-wg1~bionic from PPA. I have a Wireguard-based VPN server that has several peers. As soon as number of peers is 22 or lower, everything works okay. As soon as I add the 23rd peer, restart of `systemd-networkd` service fails with timeout while systemd-networkd hogs CPU. Moreover, if I reboot the box while wireguard configuration is "broken", systemd-networkd fails to apply network settings on boot and the box is no longer accessible over the network. Configuration is structured in a following way (keys are fake): ==> wg0.netdev [NetDev] Name=wg0 Kind=wireguard Description=Wireguard VPN server [WireGuard] ListenPort=4500 PrivateKey=kNl7tkhCM1Crj8RhUIn8xvwcg+UoOkw26kQjQEtZk1k= [WireGuardPeer] PublicKey=AfM1AN4IIUe5AVypFg2pcNrQmqOtZQIJLgusbkDYXkI= AllowedIPs=fd6f:b446:a2ca:0400:cb6f:b446:a2ca:bd0b/128 AllowedIPs=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [WireGuardPeer] like that ==> wg0.network Name=wg0 [Network] Address=fd6f:b446:a2ca:0400::1/64 [Route] Destination=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [Route] sections like that syslog logs are attached both for "good" and "bad" cases, sample of strace logs is also attached for "bad" case. I'm filling the issue here as the aforementioned systemd version is already out of scope of upstream bug tracker per https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md #filing-issues To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1811149/+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 1811531] Re: remote execution vulnerability
Also note that this was introduced in 4.2.0, so xenial is not affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531] [NEW] remote execution vulnerability
*** This bug is a security vulnerability *** Public security bug reported: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. ** Affects: zeromq3 (Ubuntu) Importance: Undecided Status: New ** Patch added: "backported patch for 4.2.5" https://bugs.launchpad.net/bugs/1811531/+attachment/5228726/+files/pointer_overflow.patch ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811149] Re: 23 wireguard peers hang systemd-networkd
** Bug watch added: github.com/systemd/systemd/issues #11404 https://github.com/systemd/systemd/issues/11404 ** Also affects: systemd via https://github.com/systemd/systemd/issues/11404 Importance: Unknown Status: Unknown -- 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/1811149 Title: 23 wireguard peers hang systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 18.04.1 LTS with systemd=237-3ubuntu10.9. Linux kernel version is 4.15.0-32-generic #35-Ubuntu SMP. wireguard=0.0.20181218-wg1~bionic from PPA. I have a Wireguard-based VPN server that has several peers. As soon as number of peers is 22 or lower, everything works okay. As soon as I add the 23rd peer, restart of `systemd-networkd` service fails with timeout while systemd-networkd hogs CPU. Moreover, if I reboot the box while wireguard configuration is "broken", systemd-networkd fails to apply network settings on boot and the box is no longer accessible over the network. Configuration is structured in a following way (keys are fake): ==> wg0.netdev [NetDev] Name=wg0 Kind=wireguard Description=Wireguard VPN server [WireGuard] ListenPort=4500 PrivateKey=kNl7tkhCM1Crj8RhUIn8xvwcg+UoOkw26kQjQEtZk1k= [WireGuardPeer] PublicKey=AfM1AN4IIUe5AVypFg2pcNrQmqOtZQIJLgusbkDYXkI= AllowedIPs=fd6f:b446:a2ca:0400:cb6f:b446:a2ca:bd0b/128 AllowedIPs=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [WireGuardPeer] like that ==> wg0.network Name=wg0 [Network] Address=fd6f:b446:a2ca:0400::1/64 [Route] Destination=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [Route] sections like that syslog logs are attached both for "good" and "bad" cases, sample of strace logs is also attached for "bad" case. I'm filling the issue here as the aforementioned systemd version is already out of scope of upstream bug tracker per https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md #filing-issues To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1811149/+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 1811149] Re: 23 wireguard peers hang systemd-networkd
I've written a small script to reproduce the issue and I got following results using VMs from Linode: - broken with systemd=237-3ubuntu10.9 on Ubuntu 18.04, 4.15.0-43-generic #46-Ubuntu. - broken with systemd=237-3ubuntu10.11 on Ubuntu 18.04, 4.15.0-43-generic #46-Ubuntu. - broken with systemd=239-7ubuntu10.6 on Ubuntu 18.10, 4.18.0-13-generic #14-Ubuntu. The way I used to reproduce the issue was to 1) start Linode VM, 2) run `./systemd-wg 23`. For some reason, 23 is the magic number of peers: 22 peers, 24 peers and 1500 peers work okay, but 23 peers trigger the bug. Given the fact that 239 is also affected, I'm submitting it upstream. ** Attachment added: "bash script to reproduce the issue" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149/+attachment/5228725/+files/systemd-wg -- 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/1811149 Title: 23 wireguard peers hang systemd-networkd Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 18.04.1 LTS with systemd=237-3ubuntu10.9. Linux kernel version is 4.15.0-32-generic #35-Ubuntu SMP. wireguard=0.0.20181218-wg1~bionic from PPA. I have a Wireguard-based VPN server that has several peers. As soon as number of peers is 22 or lower, everything works okay. As soon as I add the 23rd peer, restart of `systemd-networkd` service fails with timeout while systemd-networkd hogs CPU. Moreover, if I reboot the box while wireguard configuration is "broken", systemd-networkd fails to apply network settings on boot and the box is no longer accessible over the network. Configuration is structured in a following way (keys are fake): ==> wg0.netdev [NetDev] Name=wg0 Kind=wireguard Description=Wireguard VPN server [WireGuard] ListenPort=4500 PrivateKey=kNl7tkhCM1Crj8RhUIn8xvwcg+UoOkw26kQjQEtZk1k= [WireGuardPeer] PublicKey=AfM1AN4IIUe5AVypFg2pcNrQmqOtZQIJLgusbkDYXkI= AllowedIPs=fd6f:b446:a2ca:0400:cb6f:b446:a2ca:bd0b/128 AllowedIPs=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [WireGuardPeer] like that ==> wg0.network Name=wg0 [Network] Address=fd6f:b446:a2ca:0400::1/64 [Route] Destination=fd6f:b446:a2ca:cb6f:b446:a2ca::/96 # and 22 more [Route] sections like that syslog logs are attached both for "good" and "bad" cases, sample of strace logs is also attached for "bad" case. I'm filling the issue here as the aforementioned systemd version is already out of scope of upstream bug tracker per https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md #filing-issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Hmm, I did notice something looked a bit weird up there. But now that you mention it I do see the same issue on my thing too (see screenshot). ** Attachment added: "Screenshot from 2019-01-12 10-43-12.png" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+attachment/5228723/+files/Screenshot%20from%202019-01-12%2010-43-12.png -- 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/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+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 1811524] [NEW] Odd failure about libdvd-pkg
Public bug reported: When I install something by apt, I get this at the end even if the installation seems to be successful: libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.2.orig.tar.bz2: OK libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... Still: $ sudo apt-get check ; echo $? Reading package lists... Done Building dependency tree Reading state information... Done 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 12 16:54:12 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (736 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1811524 Title: Odd failure about libdvd-pkg Status in apt package in Ubuntu: New Bug description: When I install something by apt, I get this at the end even if the installation seems to be successful: libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.2.orig.tar.bz2: OK libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... Still: $ sudo apt-get check ; echo $? Reading package lists... Done Building dependency tree Reading state information... Done 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 12 16:54:12 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (736 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811524/+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 425839] Re: Remove dictionary choice when adding new entry to the OpenOffice spellchecker
Upstream bug showing "RESOLVED FIXED" on 2012-05-18 Target release of 3.6, we're now on 6.x in Ubuntu 18.04 So closing by changing status to "Fix Released" ** Changed in: hundredpapercuts Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openoffice.org- dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/425839 Title: Remove dictionary choice when adding new entry to the OpenOffice spellchecker Status in LibreOffice: Incomplete Status in One Hundred Papercuts: Fix Released Status in openoffice.org-dictionaries package in Ubuntu: Invalid Bug description: When i try to add a word to my dictionary and i have just one, there are a submenu asking for what dictionary i want to use... I think that maybe could be great if we have only the ADD option if we have only one dictionary... I attach a screenshot and sorry because i speak spanish. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/425839/+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 11544] Re: Single click doesn't work in file chooser dialog box
Upstream issue is now at: https://gitlab.gnome.org/GNOME/gtk/issues/228 ** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/11544 Title: Single click doesn't work in file chooser dialog box Status in GTK+: Expired Status in One Hundred Papercuts: In Progress Status in gtk+2.0 package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: when you select single click in file management it works for nautilus and the desktop but not for applications that use the "file chooser dialog box" to open files, i.e. you have to double click to open directories even with single click selected as the gnome default. http://bugzilla.gnome.org/show_bug.cgi?id=121113: http://bugzilla.gnome.org/show_bug.cgi?id=121113 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/11544/+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 924793] Re: GTK3 file dialogs in Kubuntu using left-handed mouse
Upstream GNOME bug is showing "RESOLVED FIXED" on 2012-04-04 Further to comment #3 by reporter will close bug report ** Changed in: hundredpapercuts Importance: Undecided => Low ** Changed in: hundredpapercuts Status: New => Fix Released ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/924793 Title: GTK3 file dialogs in Kubuntu using left-handed mouse Status in One Hundred Papercuts: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: This is a bug report following on from discussion here: http://ubuntuforums.org/showthread.php?t=1863325 To summarize. In KDE with left-handed mouse button enabled... "left-button-click" signal doesn't get passed on to any Gtk3 apps running in KDE." Gedit example: So, for example: Run gedit under kubuntu, CTRL+O to open file open dialog. Clicking on directory tree, or files 'does not work'. Keyboard shortcuts then need to be used to navigate, select. The problem started on ubuntu/kubuntu 11.10. Have now upgraded to KDE 4.8 (to see if issue is solved), but problem still persists. The application functions normally with right-handed mouse. Description: Ubuntu 11.10 Release: 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.2.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.0.0-15.26-generic-pae 3.0.13 Uname: Linux 3.0.0-15-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Feb 1 11:57:54 2012 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to oneiric on 2011-10-13 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/924793/+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 1768026] Re: echo message hides cursor
Will there be a backport? This is really annoying... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1768026 Title: echo message hides cursor Status in vim: Fix Released Status in vim package in Ubuntu: Confirmed Bug description: https://github.com/w0rp/ale/issues/1536#issuecomment-385056702 upstream bug https://github.com/vim/vim/issues/2612 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:16:35 2018 InstallationDate: Installed on 2017-05-17 (347 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1768026/+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 1811495] Re: package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: package-install-segfault ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811495 Title: package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler- Ausgangsstatus 139 zurück Status in systemd package in Ubuntu: Invalid Bug description: ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules 70-snap.gimp.rules Date: Sat Jan 12 08:57:31 2019 ErrorMessage: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück InstallationDate: Installed on 2019-01-09 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Packard Bell EasyNote TE11HC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=afbd8811-f0a6-4acb-a0fa-e0a94b3b6028 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd Title: package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2012 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Packard Bell dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.13 dmi.modalias: dmi:bvnPackardBell:bvrV1.13:bd10/09/2012:svnPackardBell:pnEasyNoteTE11HC:pvrV1.13:rvnPackardBell:rnEG50_HC_HR:rvrType2-BoardVersion:cvnPackardBell:ct10:cvrV1.13: dmi.product.family: Type1Family dmi.product.name: EasyNote TE11HC dmi.product.version: V1.13 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811495/+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 1811495] [NEW] package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules 70-snap.gimp.rules Date: Sat Jan 12 08:57:31 2019 ErrorMessage: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück InstallationDate: Installed on 2019-01-09 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Packard Bell EasyNote TE11HC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=afbd8811-f0a6-4acb-a0fa-e0a94b3b6028 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd Title: package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2012 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Packard Bell dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.13 dmi.modalias: dmi:bvnPackardBell:bvrV1.13:bd10/09/2012:svnPackardBell:pnEasyNoteTE11HC:pvrV1.13:rvnPackardBell:rnEG50_HC_HR:rvrType2-BoardVersion:cvnPackardBell:ct10:cvrV1.13: dmi.product.family: Type1Family dmi.product.name: EasyNote TE11HC dmi.product.version: V1.13 dmi.sys.vendor: Packard Bell ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-package bionic package-install-segfault -- 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/1811495 Title: package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler- Ausgangsstatus 139 zurück Status in systemd package in Ubuntu: Invalid Bug description: ProblemType: Package DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.11 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules 70-snap.gimp.rules Date: Sat Jan 12 08:57:31 2019 ErrorMessage: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück InstallationDate: Installed on 2019-01-09 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Packard Bell EasyNote TE11HC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=afbd8811-f0a6-4acb-a0fa-e0a94b3b6028 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd Title: package udev 237-3ubuntu10.11 failed to install/upgrade: Unterprozess installed udev package post-installation script gab den Fehler-Ausgangsstatus 139 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2012 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Packard Bell dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.13 dmi.modalias: dmi:bvnPackardBell:bvrV1.13:bd10/09/2012:svnPackardBell:pnEasyNoteTE11HC:pvrV1.13:rvnPackardBell:rnEG50_HC_HR:rvrType2-BoardVersion:cvnPackardBell:ct10:cvrV1.13: dmi.product.family: Type1Family dmi.product.name: EasyNote TE11HC dmi.product.version: V1.13 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811495/+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
