[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig
** Description changed: [SRU Justification] A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail because of trying to process triggers out of order. Since the trigger being run is that of the currently-installed plymouth package, it is not guaranteed to be sufficient to fix the version of the package in 18.04. [Test case] - 1. Install plymouth-themes-ubuntu-text from artful-proposed. + 1. Install plymouth-themes-ubuntu-text from -proposed. 2. Run a release upgrade with each of update-manager -d, do-release-upgrade -d, and apt-get dist-upgrade (the last after manually changing sources.list). 3. Verify that in each case, the upgrade completes successfully, with no errors about out-of-order trigger configuration. [Regression potential] noawait triggers have been supported in dpkg since 1.16.1, which is older than the version in precise (https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html). A noawait trigger is considered appropriate whenever the triggered package does not need to block the triggering package. There is no reason for a plymouth theme package to need to block configuration of an essential package in this case. noawait triggers are well-exercised in the distro now, so the risk of regression from this change should be low. There is unfortunately not a known reproducer for the original bug, so the test case, while it should guard against regressions, is not strong confirmation that the bug is fixed. - [Original description] Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 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 Date: Sun Feb 18 23:41:49 2018 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-10-24 (118 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.5.1 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago) dmi.bios.date: 01/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 01W6F7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. -- 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/1750465 Title: upgrade attempting to process triggers out of order (package plymouth- theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed) Status in apt package in Ubuntu: Confirmed Status in budgie-artwork package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Fix Released Status in ubuntu-gnome-default-settings package in Ubuntu: Confirmed Status in ubuntu-mate-artwork package in Ubuntu: Confirmed Status in apt source package in Xenial: Confirmed Status in budgie-artwork source package in Xenial: Confirmed Status in kubuntu-settings source package in Xenial: Confirmed Status in plymouth source package in Xenial: Fix Committed Status in ubuntu-gnome-default-settings source package in Xenial: Confirmed Status in ubuntu-mate-artwork source package in Xenial: Confirme
[Touch-packages] [Bug 1758498] Re: perl crashed with SIGABRT in _dbus_abort()
i have this 3g modem that works but this not show up in top bar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1758498 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Confirmed Bug description: I was browsing the internet using firefox installed from ubuntu repo ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Fri Mar 23 22:56:12 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2018-03-15 (9 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1758498/+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 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record
** Changed in: systemd (Ubuntu) Status: Expired => Won't Fix ** Changed in: systemd (Ubuntu) Status: Won't Fix => 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/1717015 Title: libc resolver stops searching domain search list after getting back NSEC record Status in systemd package in Ubuntu: New Bug description: Suppose that: 1. you have a "search" line in your /etc/resolv.conf file; 2. it has two domains in it; and 3. the first of the two domains does DNSSEC, including returning NSEC records for nonexisting hosts. In this situation, when you try to look up a host name in the second domain without specifying the domain part of the host name, the libc resolver will stop after it gets back the NSEC record and report that the host name doesn't exist, rather than moving on to the second domain in the search list and searching for the host in that domain. See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014 . ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libc6 2.24-9ubuntu2.2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Sep 13 16:00:45 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 InstallationDate: Installed on 2016-08-09 (400 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: glibc UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+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 1717015] Re: libc resolver stops searching domain search list after getting back NSEC record
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1717015 Title: libc resolver stops searching domain search list after getting back NSEC record Status in systemd package in Ubuntu: Expired Bug description: Suppose that: 1. you have a "search" line in your /etc/resolv.conf file; 2. it has two domains in it; and 3. the first of the two domains does DNSSEC, including returning NSEC records for nonexisting hosts. In this situation, when you try to look up a host name in the second domain without specifying the domain part of the host name, the libc resolver will stop after it gets back the NSEC record and report that the host name doesn't exist, rather than moving on to the second domain in the search list and searching for the host in that domain. See also https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1717014 . ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libc6 2.24-9ubuntu2.2 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Sep 13 16:00:45 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 InstallationDate: Installed on 2016-08-09 (400 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: glibc UpgradeStatus: Upgraded to zesty on 2017-04-19 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717015/+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 1746587] Re: my bug's
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1746587 Title: my bug's Status in xorg package in Ubuntu: Expired Bug description: see my bugs please. Thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 31 20:47:44 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] [1002:954f] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV710 [Radeon HD 4350/4550] [1458:21ae] InstallationDate: Installed on 2017-04-22 (284 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) MachineType: Acer APF6/AST660/ASE560 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-B1 dmi.board.name: E415SM dmi.board.vendor: Acer dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-B1:bd04/02/2007:svnAcer:pnAPF6/AST660/ASE560:pvr1.0:rvnAcer:rnE415SM:rvr1.0:cvnAcer:ct3:cvr: dmi.product.name: APF6/AST660/ASE560 dmi.product.version: 1.0 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jan 31 20:43:32 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746587/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
** Also affects: totem (Ubuntu) Importance: Undecided Status: New ** Changed in: totem (Ubuntu) Status: New => Confirmed -- 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/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GTK+: Fix Released Status in totem-pl-parser: Confirmed Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gtk package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in totem package in Ubuntu: Confirmed Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698270/+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 1760415] Re: gnome-shell crashed with SIGSEGV
** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV + gnome-shell crashed with SIGSEGV inintel_miptree_supports_hiz() from needs_separate_stencil() ** Summary changed: - gnome-shell crashed with SIGSEGV inintel_miptree_supports_hiz() from needs_separate_stencil() + gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from needs_separate_stencil() ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: 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/1760415 Title: gnome-shell crashed with SIGSEGV in intel_miptree_supports_hiz() from needs_separate_stencil() Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Screen had automatically locked overnight. Bug report prompt appeared a few seconds after I logged in. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 31 10:24:03 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-10-23 (159 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8c18dbc870:mov(%rdi),%eax PC (0x7f8c18dbc870) ok source "(%rdi)" (0x0074) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-17 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760415/+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 566826] Re: ubuntu server ISO TESTING can't connect crash database on Lucid
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 566826 and any other logs that are relevant for this particular issue. -- 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/566826 Title: ubuntu server ISO TESTING can't connect crash database on Lucid Status in apport package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: Binary package hint: ubiquity Hello, I tried Ubuntu Server amd64 [20100419.] ISO TESTING on virtualbox 3.1.6 x86 64 and after installed without any problems the system, i restarted and was a bug i would to report but i get a message about permission denied: Erno 131, permission denied : cannot connect to crash database /var/log/installer/partman And so i still unable to send report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/566826/+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 1758107] Re: Firefox: View > Toolbars is Missing "Bookmarks Toolbar"
Great video, thanks. The menu in the top bar is actually displayed by the shell, and communicated from Firefox via 'libdbusmenu'. So I'm moving this bug there. It's not a theme issue. ** Summary changed: - View > Toolbars is Missing "Bookmarks Toolbar" + Firefox: View > Toolbars is Missing "Bookmarks Toolbar" ** Package changed: ubuntu-themes (Ubuntu) => libdbusmenu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1758107 Title: Firefox: View > Toolbars is Missing "Bookmarks Toolbar" Status in firefox package in Ubuntu: Confirmed Status in libdbusmenu package in Ubuntu: Confirmed Bug description: The "Bookmarks Toolbar" toggler is missing from the View > Toolbars menu in Firefox 59 on Ubuntu 16.04.4. Video: https://youtu.be/Josm0VqtUDQ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 59.0.1+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lonnie 1902 F pulseaudio /dev/snd/pcmC0D0p: lonnie 1902 F...m pulseaudio /dev/snd/controlC0: lonnie 1902 F pulseaudio BuildID: 20180316021607 Channel: Unavailable CurrentDesktop: Unity Date: Thu Mar 22 11:42:51 2018 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-02-09 (41 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.77.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.77.0/24 dev enp3s0 proto kernel scope link src 192.168.77.252 metric 100 NoProfiles: True RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 7001 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv8 Notebook PC dmi.product.version: 04992224121000104 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758107/+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 1760341] Re: Intermittent freeze in display output, XPS 9530 with nouveau
*** This bug is a duplicate of bug 1756877 *** https://bugs.launchpad.net/bugs/1756877 ** This bug has been marked a duplicate of bug 1756877 High visual latency in 18.04 when using nouveau -- 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/1760341 Title: Intermittent freeze in display output, XPS 9530 with nouveau Status in xorg package in Ubuntu: New Bug description: Display output intermittently pauses for approximately a second, causing the system to appear "stuttery". During freezes mouse input doesn't seem to be registered and keyboard input is repeated, as though keys are being held down. Watching the journal via `journalctl -f`, the following message appears each time the problem occurs: Mar 31 20:16:18 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 0002 FAULT at 4188ac [ IBUS ] Mar 31 20:16:27 luke-ultrabook kernel: nouveau :02:00.0: bus: MMIO write of 0002 FAULT at 4188ac [ IBUS ] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 31 20:11:01 2018 DistUpgraded: 2018-03-31 16:47:43,480 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05fe] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fe] InstallationDate: Installed on 2018-01-29 (61 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 15 9530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=58327001-b3e0-4118-a0e6-03e8221a44f2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-31 (0 days ago) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1760341/+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 1733707] Re: Ambiance/Radiance: add styling for mate-panel
I thought MATE fixes landed in December/January. Is this still a bug? ** Changed in: ubuntu-themes Importance: Undecided => Wishlist ** Changed in: ubuntu-themes Status: New => Incomplete ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- 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/1733707 Title: Ambiance/Radiance: add styling for mate-panel Status in Ubuntu theme: Incomplete Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: Both themes look odd in MATE Desktop. Consider adding specific styling for mate-panel, like gnome-panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1733707/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions
Yes I can confirm that. But I think it should be discussed in a different bug report. -- 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/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions Status in GTK+: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1693609] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click
The update that was released actually solved more subtle issues. It didn't solve this bug, as was mentioned in https://code.launchpad.net/~3v1n0/ubuntu-themes/windowbuttons-bg-and- padding/+merge/342171 ** Changed in: ubuntu-themes (Ubuntu) Status: Fix Released => Confirmed ** Changed in: ubuntu-themes (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Triaged -- 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/1693609 Title: The "Minimize", " Maximize" and "Close" buttons are too small to click Status in Ubuntu UX: Confirmed Status in ubuntu-themes package in Ubuntu: Triaged Bug description: The window control buttons ( _ 🗖 X ) in Ambiance are noticeably smaller than other icon buttons in the headerbar of a "native" GNOME3 app. I think this is both a visual issue and an accessibility issue since it is harder to click the window control buttons than the other buttons. Please compare with Adwaita which has a much larger click area for the window control buttons. Commentary -- Remember that one of the major strengths of GNOME 3 is that it is usable on a touch-enabled laptop. And while there are many people that complain about Adwaita, I believe many more actually like the proportions and padding of the default GNOME theme! ubuntu-themes 16.10+17.10.20170518-0ubuntu1 Ubuntu 17.10 Alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1693609/+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 566826] Re: ubuntu server ISO TESTING can't connect crash database on Lucid
** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- 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/566826 Title: ubuntu server ISO TESTING can't connect crash database on Lucid Status in apport package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: Binary package hint: ubiquity Hello, I tried Ubuntu Server amd64 [20100419.] ISO TESTING on virtualbox 3.1.6 x86 64 and after installed without any problems the system, i restarted and was a bug i would to report but i get a message about permission denied: Erno 131, permission denied : cannot connect to crash database /var/log/installer/partman And so i still unable to send report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/566826/+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 1547561] Re: Unable to use Scilab with default Ambiance theme because of low contrast in the menu
It looks like Scilab is hard-coding black (and white) fonts in a couple of places. That may be a problem confined to the Scilab source code. ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Incomplete -- 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/1547561 Title: Unable to use Scilab with default Ambiance theme because of low contrast in the menu Status in scilab package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Install Ubuntu with all default settings (Ambiance theme) 2. Install Scilab 3. Launch Scilab 4. Try to use Scilab menu on the top of its window 5. This menu has low contrast (see screenshot from 14.04). Temporary solution: switch theme to light (Radiance) theme. Affected Ubuntu versions: 12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10, 17.04, 17.10, 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: scilab 5.5.0-2 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Fri Feb 19 18:31:09 2016 InstallationDate: Installed on 2015-12-12 (68 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all SourcePackage: scilab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1547561/+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 1197395] Re: /run/user/$ID/pulse owned by root and not by the user
This bug is closed. If you have any issues, please open a new bug.
--
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/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
Status in elementary OS:
New
Status in pulseaudio package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in pulseaudio source package in Saucy:
Invalid
Status in systemd source package in Saucy:
Fix Released
Status in systemd package in Fedora:
Won't Fix
Bug description:
I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a
media player (I use Musique), it freezes, as it finds that it cannot write into
/run/user/$ID/pulse.
If I change the owner of that directory to me, the media player starts as
usual and is able to play music.
I've never had this problem with previous versions of Ubuntu.
Someone says that running PulseAudio with the -D argument changes the owner
of that directory, but I didn't try.
This is before manually changing the owner of that directory:
$ musique
Failed to create secure directory (/run/user/1000/pulse): Permission denied+
... # it doesn't crash, it keeps waiting
If needed:
(dmesg attached)
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1
(rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2
(rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3
(rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5
(rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6
(rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4
port SATA Controller [AHCI mode] (rev 03)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter
(PCI-Express) (rev 01)
85:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8072 PCI-E
Gigabit Ethernet Controller (rev 10)
From /var/log/syslog:
Jul 3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] core-util.c:
Failed to create secure directory (/run/user/1000/pulse): Permission denied
Jul 3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] main.c:
User-configured server at
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to
start/autospawn.
Jul 3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] core-util.c:
Failed to create secure directory (/run/user/1000/pulse): Permission denied
Jul 3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] main.c:
User-configured server at
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to
start/autospawn.
This is a fresh installation, I haven't updated it from a previous version.
I'm using Ubuntu with Unity, not a derivative.
These are my PPAs:
canonical-qt5-edgers-qt5-proper-saucy.list
dropbox.list
dukto.list
google-earth.list
jd-team-jdownloader-saucy.list
kivy-team-kivy-saucy.list
mitya57-ppa-saucy.list
numix-icon-theme-dev-utouch-saucy.list
otto-kesselgulasch-gimp-saucy.list
phablet-team-desktop-deps-saucy.list
satyajit-happy-themes-saucy.list
steam.list
ubuntu-sdk-team-ppa-saucy.list
ubuntutrucchi.list
ubuntutrucchi-testing.list
ubuntu-wine-ppa-saucy.list
webupd8team-y-ppa-manager-saucy.list
SRU INFORMATION
===
TEST CASE:
- Ensure that as a normal user "echo $XDG_RUNTIME_DIR" is something like
"/r
[Touch-packages] [Bug 1649262] Re: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: canonical-devices-system-image Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1649262 Title: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7 Status in Canonical System Image: Incomplete Status in qtdeclarative-opensource-src package in Ubuntu: Incomplete Bug description: 17.04 unity7 ~$ webbrowser-app libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information (webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. (webbrowser-app:4695): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. UCUriHandler: Empty "APP_ID" environment variable, ignoring. unity::action::ActionManager::ActionManager(QObject*): Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable. libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information could not open containers config file "/home/pixel/.local/share/libertine/ContainersConfig.json" APP_ID isn't set, the handler can not be registered Input device added: "Power Button" "/dev/input/event1" QFlags(0x1) Input device added: "Power Button" "/dev/input/event0" QFlags(0x1) Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20) Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20) Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20) Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" QFlags(0x2) Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10) Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1) (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Permission denied QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader QOpenGLShader: could not create shader APP_ID isn't set, the handler ignored qml: Loaded 13 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js ^CSegmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649262/+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 566826] Re: ubuntu server ISO TESTING can't connect crash database on Lucid
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 566826 and any other logs that are relevant for this particular issue. ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/566826 Title: ubuntu server ISO TESTING can't connect crash database on Lucid Status in apport package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: Binary package hint: ubiquity Hello, I tried Ubuntu Server amd64 [20100419.] ISO TESTING on virtualbox 3.1.6 x86 64 and after installed without any problems the system, i restarted and was a bug i would to report but i get a message about permission denied: Erno 131, permission denied : cannot connect to crash database /var/log/installer/partman And so i still unable to send report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/566826/+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 1759961] Re: Update to 5.49 in Bionic (mostly bug-fix release)
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Tags added: bluez-5.49 -- 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/1759961 Title: Update to 5.49 in Bionic (mostly bug-fix release) Status in bluez package in Ubuntu: Triaged Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1760739] Re: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1760739 Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: New Bug description: failure on update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 21:07:40 2018 DpkgHistoryLog: Start-Date: 2018-04-02 21:07:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.123' Upgrade: lshw:amd64 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5) DuplicateSignature: package:libkrb5-26-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-03 (150 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: heimdal Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1760739/+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 1760739] [NEW] package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstal
Public bug reported: failure on update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 21:07:40 2018 DpkgHistoryLog: Start-Date: 2018-04-02 21:07:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.123' Upgrade: lshw:amd64 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5) DuplicateSignature: package:libkrb5-26-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-03 (150 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: heimdal Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1760739 Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: New Bug description: failure on update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 21:07:40 2018 DpkgHistoryLog: Start-Date: 2018-04-02 21:07:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.123' Upgrade: lshw:amd64 (02.17-1.1ubuntu3.4, 02.17-1.1ubuntu3.5) DuplicateSignature: package:libkrb5-26-heimdal:amd64:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libkrb5-26-heimdal:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-03 (150 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: heimdal Title: package libkrb5-26-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1760739/+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 1732970] Re: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive
Why did there get removed? We at UBports depend on these. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtfeedback-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1732970 Title: Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems- opensource-src from archive Status in cordova-ubuntu-3.4 package in Ubuntu: Fix Released Status in qtfeedback-opensource-src package in Ubuntu: Fix Released Status in qtsystems-opensource-src package in Ubuntu: Fix Released Bug description: cordova-ubuntu is dead upstream (https://github.com/apache/cordova- ubuntu had last commit in Oct 2016), Ubuntu packaging has no active maintainer and has not been updated since 2014. I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe to remove it: https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43 qtfeedback-opensource-src and qtsystems-opensource-src are libraries which have never become part of official Qt releases, and their only user in Ubuntu was cordova-ubuntu-3.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu-3.4/+bug/1732970/+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 1760073] Re: No network from suspend resume
Network issue is either kernel or Network Manager. After the issue occurs we need to see the current 'dmesg' log (which will show if devices resumed successfully) and /var/log/syslog (where Network Manager is very verbose). We also need to know which devices the system has: lspci -nnk lsusb -- 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/1760073 Title: No network from suspend resume Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Following a resume from suspend - no network available on machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:53:22 2018 InstallationDate: Installed on 2018-03-08 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-08 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic third-party-packages Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-08 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic third-party-packages Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-08 (23 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760073/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor
I was having this same issue after plugging in my screen. Oddly enough this issue was resolved when I was trying to solve another issue about screen locking up when opening a new application. Here is the solution that fixed both issues. https://support.displaylink.com/knowledgebase/articles/1843660-screen- freezes-after-opening-an-application-only -- 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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1748147] Re: Upgrading systemd sets incorrect permissions on /var/log/
** Changed in: debhelper 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/1748147 Title: Upgrading systemd sets incorrect permissions on /var/log/ Status in debhelper: New Status in debhelper package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 3,634 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu21.1 [3,634 kB] Fetched 3,634 kB in 0s (24.3 MB/s) (Reading database ... 86614 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ... Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd (229-4ubuntu21.1) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxr-xr-x 8 root syslog 4096 Feb 7 13:45 /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/debhelper/+bug/1748147/+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 1760411] Re: I don know
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** 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/1760411 Title: I don know Status in xorg package in Ubuntu: Incomplete Bug description: i don know ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 1 16:29:14 2018 DistUpgraded: 2018-03-31 14:06:35,805 DEBUG /openCache(), new cache size 86473 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80c1] InstallationDate: Installed on 2018-03-26 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-03-31 (1 days ago) dmi.bios.date: 10/27/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: HP dmi.board.version: 96.51 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.24:bd10/27/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook 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.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 31 13:56:55 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1760411/+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 1759921] Re: Problem with Lexmark Optra E310: printing system doesn't work
** Summary changed: - printing system doesn't work + Problem with Lexmark Optra E310: printing system doesn't work -- 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/1759921 Title: Problem with Lexmark Optra E310: printing system doesn't work Status in cups package in Ubuntu: New Bug description: My printer, Lexmark Optra E310, is configured automatically by the system and it worked perfectly in Linux until now. The Printer is OK, it works perfectly in Windows, but now in Linux everytime I try to print something, whatever it is, it prints the next messages on paper: ERROR: configurationerror OFFENDING COMMAND: setpagedevice STACK: --nostringval-- false 842 595 0 0 842 595 --nostringval-- 5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Mar 29 19:38:02 2018 Lpstat: device for Lexmark-Optra-E310: usb://Lexmark/Optra%20E310?serial=5163293 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: a4 PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript (recommended) ProcEnviron: LANGUAGE=es_ES TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: N68-GS3 UCC 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.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1760721] [NEW] Resolution is stuck at 640x480
Public bug reported: This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 resolution, this happened since the first boot. I researched and found in forums that xdiagnose provides a workaround by deactivating some graphics at boot, so I installed it and it worked, however, just as a workaround. I can change the resolution now, but the size of apps sometimes takes way more screen space than it should, and the screen flickers randomly. By selecting "inform errors" in xdiagnose I got a pop up message saying the computer is providing 3D by software instead of hardware, I don't know how to fix this, any guidance? Let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic i686 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Apr 2 16:30:13 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1025:0083] InstallationDate: Installed on 2018-04-02 (0 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release i386 (20180105) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Aspire 3000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a37feeb6-1e6a-47c6-b003-a161b5612912 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/06 dmi.bios.vendor: Acer dmi.bios.version: 3A32 dmi.board.name: Lugano M dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: , Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A32:bd02/20/06:svnAcer,inc.:pnAspire3000:pvrNotApplicable:rvnAcer,Inc.:rnLuganoM:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 3000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Apr 2 16:18:06 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 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/1760721 Title: Resolution is stuck at 640x480 Status in xorg package in Ubuntu: New Bug description: This is a fresh install of Xubuntu 17.10. The OS is stuck at 640x480 resolution, this happened since the first boot. I researched and found in forums that xdiagnose provides a workaround by deactivating some graphics at boot, so I installed it and it worked, however, just as a workaround. I can change the resolution now, but the size of apps sometimes takes way more screen space than it should, and the screen flickers randomly. By selecting "inform errors" in xdiagnose I got a pop up message saying the computer is providing 3D by software instead of hardware, I don't know how to fix this, any guidance? Let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic i686 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 CompizPlugins: No
[Touch-packages] [Bug 1759985] Re: can python-crypto and pycryptodome co-exist?
Beautiful! Thanks Steve.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-crypto in Ubuntu.
https://bugs.launchpad.net/bugs/1759985
Title:
can python-crypto and pycryptodome co-exist?
Status in pycryptodome package in Ubuntu:
Invalid
Status in python-crypto package in Ubuntu:
Invalid
Bug description:
Hello,
The pycryptodome docs have:
> The installation procedure depends on the package you want the library in.
> PyCryptodome can be used as:
>$
> #. **a drop-in replacement for the old PyCrypto library**.
>You install it with::
>$
>pip install pycryptodome
> $$$
>In this case, all modules are installed under the ``Crypto`` package.
>
>One must avoid having both PyCrypto and PyCryptodome installed
>at the same time, as they will interfere with each other.
>$
>This option is therefore recommended only when you are sure that
>the whole application is deployed in a ``virtualenv``.
>$
> #. **a library independent of the old PyCrypto**.
>You install it with::
>$
>pip install pycryptodomex
> $$$
>In this case, all modules are installed under the ``Cryptodome`` package.
>PyCrypto and PyCryptodome can coexist.
>$
Currently there's no Breaks or Conflicts lines in either package:
$ grep -e Break -e Conflict pycryptodome/bionic/pycryptodome-3.4.7/debian/*
python-crypto/bionic/python-crypto-2.6.1/debian/*
grep: pycryptodome/bionic/pycryptodome-3.4.7/debian/patches: Is a directory
grep: pycryptodome/bionic/pycryptodome-3.4.7/debian/source: Is a directory
grep: pycryptodome/bionic/pycryptodome-3.4.7/debian/tests: Is a directory
grep: pycryptodome/bionic/pycryptodome-3.4.7/debian/upstream: Is a directory
python-crypto/bionic/python-crypto-2.6.1/debian/changelog:- Remove
obsolete Breaks+Replaces
python-crypto/bionic/python-crypto-2.6.1/debian/changelog: * Drop obsolete
Conflicts/Replaces with python2.3-crypto and
python-crypto/bionic/python-crypto-2.6.1/debian/changelog:- Add Breaks
python{,3}-keyring (<= 0.7.1-1) to python{,3}-crypto.
grep: python-crypto/bionic/python-crypto-2.6.1/debian/patches: Is a directory
grep: python-crypto/bionic/python-crypto-2.6.1/debian/source: Is a directory
grep: python-crypto/bionic/python-crypto-2.6.1/debian/tests: Is a directory
Can these two packages be installed side-by-side? Or is this something
that matters only to 'pip' installs?
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pycryptodome/+bug/1759985/+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 1760714] [NEW] getlogin_r is performing NSS lookups when loginid isn't set
Public bug reported: This the eglibc duplicate of https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1760713 (which is for glibc) For configurations that use networked naming services for passwd (in particular LDAP), processes that have no login UID, there are excessive delays when getlogin_r() is called. For such processes, /proc/self/loginid is set to a sentinel value (-1), when files is the only backend, or if nscd is running this returns quickly. However if ldap is configured as a backend for passwd, and nscd isn't being used (which for various political and economic reasons is not always feasible) network requests to the configured LDAP servers will occur which can slow down process creation enough to cause timeouts in parent processes in certain contexts. Good news, however, as this was recently fixed upstream by: https://sourceware.org/git/?p=glibc.git;a=commit;h=cc8a1620eb97ccddd337d157263c13c57b39ab71 ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1760714 Title: getlogin_r is performing NSS lookups when loginid isn't set Status in eglibc package in Ubuntu: New Bug description: This the eglibc duplicate of https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1760713 (which is for glibc) For configurations that use networked naming services for passwd (in particular LDAP), processes that have no login UID, there are excessive delays when getlogin_r() is called. For such processes, /proc/self/loginid is set to a sentinel value (-1), when files is the only backend, or if nscd is running this returns quickly. However if ldap is configured as a backend for passwd, and nscd isn't being used (which for various political and economic reasons is not always feasible) network requests to the configured LDAP servers will occur which can slow down process creation enough to cause timeouts in parent processes in certain contexts. Good news, however, as this was recently fixed upstream by: https://sourceware.org/git/?p=glibc.git;a=commit;h=cc8a1620eb97ccddd337d157263c13c57b39ab71 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1760714/+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 1756006] Re: FFe: Support suspend-to-hibernate
The rename is done upstream, it's now suspend-then-hibernate. I'm uploading systemd with these patches. As for G-S-D, I've adjusted it for the rename too but it's still waiting to be merged. ** Changed in: systemd (Ubuntu) Status: New => Fix Committed ** Summary changed: - FFe: Support suspend-to-hibernate + FFe: Support suspend-then-hibernate -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: New Status in systemd package in Ubuntu: Fix Committed Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs
** Summary changed: - Enable configuring resume offset via sysfs + FFe: Enable configuring resume offset via sysfs -- 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/1760106 Title: FFe: Enable configuring resume offset via sysfs Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in klibc source package in Bionic: New Status in linux source package in Bionic: Triaged Status in systemd source package in Bionic: New Bug description: In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1760693] [NEW] gstreamer openglmixers
Public bug reported: I've been trying to test using the openglmixers sinks, and found an easily reproducible bug on todays build of bionic beaver. I've done quite a bit using previous versions of the same plugins in 16.04, and never ran into this one. Steps to reproduce: 1) Fresh-install of bionic-beaver gstreamer1.0-plugins-bad with all of the corresponding bits. 2) execute `gst-inspect-1.0 glvideomixer` Results: (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: Trying to dispose object "mixer", but it still has a parent "(null)". You need to let the parent manage the object instead of unreffing the object directly. ... Any gstreamer pipeline using the glvideomixer dies with the same errors above. If I switch back to using the non-open-gl version of 'videomixer', the pipeline mostly-works, but is not hardware accelerated... and tries to do everything in CPU, resulting in horrible performance. Additionally, I am unable to pass multiple sink elements into the non-gl videomixer without getting many nondescript errors: ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc3: Internal data stream error. Additional debug info: gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc3: streaming stopped, reason not-negotiated (-4) ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1760693 Title: gstreamer openglmixers Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: I've been trying to test using the openglmixers sinks, and found an easily reproducible bug on todays build of bionic beaver. I've done quite a bit using previous versions of the same plugins in 16.04, and never ran into this one. Steps to reproduce: 1) Fresh-install of bionic-beaver gstreamer1.0-plugins-bad with all of the corresponding bits. 2) execute `gst-inspect-1.0 glvideomixer` Results: (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_bin_add: assertion 'GST_IS_ELEMENT (element)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (src)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_element_get_static_pad: assertion 'GST_IS_ELEMENT (element)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: gst_element_link_pads_full: assertion 'GST_IS_ELEMENT (dest)' failed (gst-inspect-1.0:2868): GStreamer-CRITICAL **: 15:28:33.427: Trying to dispose object "mixer", but it still has a parent "(null)". You need to let the parent manage the object instead of unreffing the object directly. ... Any gstreamer pipeline using the glvideomixer dies with the same errors above. If I switch back to using the non-open-gl version of 'videomixer', the pipeline mostly-works, but is not hardware accelerated... and tries to do everything in CPU, resulting in horrible performance. Additionally, I am unable to pass multiple sink elements into the non-gl videomixer without getting many nondescript errors: ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc3: Internal data stream error. Additional debug info: gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc3: streaming stopped, reason not-negotiated (-4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1760693/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
On Thu, Mar 29, 2018 at 06:27:18PM -, Alkis Georgopoulos wrote:
> For the maintainers of the affected packages to be able to help in this
> issue, addressing the main question already stated above would be most
> helpful:
> To support netplan, do we have to implement netlink events listeners
> ourselves?
> I'm not sure all maintainers are willing to do that.
> Or is there another package that provides this functionality that we could
> rely on? E.g. NetworkManager does have a dispatcher.d directory that we
> can use, but does Ubuntu ship something similar (networkd-dispatcher?) in
> systems that don't use NetworkManager?
We are looking at integrating networkd-dispatcher for 18.04.
Many of these package tasks may become SRU material after 18.04 releases,
due to the timing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Confirmed
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStat
[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: laptop-mode-tools (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- 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/1726930 Title: System fails to start (boot) on battery due to read-only root file- system Status in laptop-mode-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Confirmed Status in laptop-mode-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Status in systemd package in Debian: Fix Released Bug description: This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery. We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue. This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only. The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log. From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times. $ grep 'EXT4-fs.*sda6' systemd-debug.log Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Those last five appear to be carrying options generated by laptop- mode-tools. User has disabled laptop-mode.service and laptop-mode.timer, and lmt- poll.service, but the issue remains. We see several reports of "read-only file-system": $ grep 'Read-only' systemd-debug.log Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system. Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system) Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system ... Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system We also see several problems with systemd's connection to Dbus: $ grep 'Transport endpoint' systemd-debug.log Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change signal for polkit.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service:
[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: klibc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic kernel-da-key ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1760106 Title: Enable configuring resume offset via sysfs Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in klibc source package in Bionic: New Status in linux source package in Bionic: Triaged Status in systemd source package in Bionic: New Bug description: In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next&id=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1757538] Re: Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-insta
Reference https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659 Most directly my work around: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/comments/13 -- 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/1757538 Title: Some packages, e.g. systemd, fail to upgrade in Ubuntu app on Windows WSL (package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1) Status in systemd package in Ubuntu: Confirmed Bug description: This occurred after running do-release-upgrade on Ubuntu 16.04 on the Linux Subsystem Windows. After the upgrade has failed, there are now dependency problems with udev and libudev1, but I do not know whether these are connected. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 234-2ubuntu12.3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Wed Mar 21 21:51:43 2018 Dmesg: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.2.26 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. Title: package systemd 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1757538/+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 1760371] Re: LightDM and GDM fail to start after systemd update in VirtualBox guest
** Summary changed: - LightDM and GDM fail to start after systemd update + LightDM and GDM fail to start after systemd update in VirtualBox guest -- 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/1760371 Title: LightDM and GDM fail to start after systemd update in VirtualBox guest Status in lightdm package in Ubuntu: New Bug description: 1) Output of lsb_release -rd: Description: Ubuntu 16.04.4 LTS Release: 16.04 2) Output of apt-cache policy lightdm: lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What I expected to happen: - Expected the display manager to take me to the lightdm user login screen. 4) What happened instead: - lightdm made 5 attempts to start before failing. Failure messages were "failed to start Detect the available GPUs and deal with any system changes" and "Failed to start Light Display Manager". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Mar 31 17:43:08 2018 InstallationDate: Installed on 2015-11-23 (859 days ago) InstallationMedia: ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2017-01-18 (437 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760371/+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 1760640] Re: package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1760640 Title: package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 Status in isc-dhcp package in Ubuntu: New Bug description: cześć mam problem z ubuntu nie działa mi centrum oprogramowania i nie wiem co robić przy każdej metodzie wyskakują mi błędy ProblemType: Package DistroRelease: Ubuntu 14.04 Package: isc-dhcp-client 4.2.4-7ubuntu12.13 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Apr 2 18:25:58 2018 DhclientLeases: DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.13:podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 InstallationDate: Installed on 2016-10-27 (521 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=b1eb634c-aa2d-45ff-83de-f2663d237fbc ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1760640/+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 1760640] [NEW] package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2
Public bug reported: cześć mam problem z ubuntu nie działa mi centrum oprogramowania i nie wiem co robić przy każdej metodzie wyskakują mi błędy ProblemType: Package DistroRelease: Ubuntu 14.04 Package: isc-dhcp-client 4.2.4-7ubuntu12.13 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Apr 2 18:25:58 2018 DhclientLeases: DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.13:podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 InstallationDate: Installed on 2016-10-27 (521 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=b1eb634c-aa2d-45ff-83de-f2663d237fbc ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1760640 Title: package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 Status in isc-dhcp package in Ubuntu: New Bug description: cześć mam problem z ubuntu nie działa mi centrum oprogramowania i nie wiem co robić przy każdej metodzie wyskakują mi błędy ProblemType: Package DistroRelease: Ubuntu 14.04 Package: isc-dhcp-client 4.2.4-7ubuntu12.13 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Mon Apr 2 18:25:58 2018 DhclientLeases: DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.13:podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 InstallationDate: Installed on 2016-10-27 (521 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=b1eb634c-aa2d-45ff-83de-f2663d237fbc ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.2.4-7ubuntu12.13 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1760640/+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 1701297] Re: NTP reload failure (unable to read library) on overlayfs
Hi all, sorry to necro a thread, but I'm having this issue on MAAS 2.3.1. Is anyone able to provide some insight into this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Won't Fix Status in apparmor package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: Incomplete Status in linux package in Ubuntu: Fix Committed Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f- 0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. Related bugs: * bug 1645644: cloud-init ntp not using expected servers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+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 1760435] Re: Use Ubuntu language packs for various indicators
Yep, that's another way. But identifying each and every package may not be the most urgent thing. The big problem has proved to be that several (most?) Unity packages have the line "X-Ubuntu-Use-Langpack: yes" in the source, but their translation templates have been deleted from LP. Fixing this in one way or another for *the most visible packages with many translatable strings* should be prio one. Hope that Sebastien will advise us about it tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1760435 Title: Use Ubuntu language packs for various indicators Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Invalid Status in indicator-power package in Ubuntu: Invalid Status in indicator-session package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: Invalid Status in unity package in Ubuntu: New Bug description: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+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 1760625] [NEW] /usr/share/apport/apport-gtk:11:visit_decref:dict_traverse:subtract_refs:collect:collect_with_callback
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.7-0ubuntu3.7, the problem page at https://errors.ubuntu.com/problem/c0d8d8079dd85ddb7fc7f704224beaa7ee0ebcf1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: artful saucy trusty utopic vivid wily xenial yakkety zesty -- 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/1760625 Title: /usr/share/apport/apport- gtk:11:visit_decref:dict_traverse:subtract_refs:collect:collect_with_callback Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.7-0ubuntu3.7, the problem page at https://errors.ubuntu.com/problem/c0d8d8079dd85ddb7fc7f704224beaa7ee0ebcf1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760625/+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 1760626] [NEW] /usr/share/apport/apport-checkreports:11:update_refs:collect:collect_with_callback:collect_generations:_PyObject_GC_Alloc
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.7-0ubuntu3.7, the problem page at https://errors.ubuntu.com/problem/24243179659aa14a1843734077beeb4d0e0a04c7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: artful xenial yakkety zesty -- 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/1760626 Title: /usr/share/apport/apport- checkreports:11:update_refs:collect:collect_with_callback:collect_generations:_PyObject_GC_Alloc Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.7-0ubuntu3.7, the problem page at https://errors.ubuntu.com/problem/24243179659aa14a1843734077beeb4d0e0a04c7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760626/+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 1760435] Re: Use Ubuntu language packs for various indicators
Something else to work with could be the 17.04 manifest (its `unity` packages (use Ctrl+F) and the relevant dependencies of them). ** Attachment added: "ubuntu-17.04-desktop-amd64.manifest" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+attachment/5098889/+files/ubuntu-17.04-desktop-amd64.manifest -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1760435 Title: Use Ubuntu language packs for various indicators Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Invalid Status in indicator-power package in Ubuntu: Invalid Status in indicator-session package in Ubuntu: Invalid Status in indicator-sound package in Ubuntu: Invalid Status in unity package in Ubuntu: New Bug description: The Unity family of packages was previously part of standard Ubuntu. Thus all the translation templates were made available to the translators via Launchpad, and the translations were included in the language packs. Since those packages are no longer part of standard Ubuntu, they have been moved from main to universe. And translations are dropped. At the moment, it is feasible for us to keep using langpacks. That means adding "X-Ubuntu-Use-Langpack: yes" to their debian/control and doing an upload. See: https://community.ubuntu.com/t/translation-of-unity-packages/4919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1760435/+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 1760614] Re: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured
*** This bug is a duplicate of bug 545790 *** https://bugs.launchpad.net/bugs/545790 ** Package changed: cups (Ubuntu) => dpkg (Ubuntu) ** This bug has been marked a duplicate of bug 545790 package PACKAGE failed to install/upgrade: error writing to '': Success -- 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/1760614 Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured Status in dpkg package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcups2:i386 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 CupsErrorLog: Date: Mon Apr 2 14:42:56 2018 DuplicateSignature: package:libcups2:i386:2.1.3-4ubuntu0.4 Processing triggers for doc-base (0.10.7) ... 1 hinzugefügte Doc-base-Datei wird verarbeitet... dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package libcups2:i386 is already installed and configured InstallationDate: Installed on 2018-01-22 (69 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Precision M6500 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: cups Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0R1203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1760614/+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 1760411] Re: I don know
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1760411 Title: I don know Status in xorg package in Ubuntu: New Bug description: i don know ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 1 16:29:14 2018 DistUpgraded: 2018-03-31 14:06:35,805 DEBUG /openCache(), new cache size 86473 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80c1] InstallationDate: Installed on 2018-03-26 (5 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: HP HP Notebook ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-03-31 (1 days ago) dmi.bios.date: 10/27/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: HP dmi.board.version: 96.51 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.24:bd10/27/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook 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.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Mar 31 13:56:55 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1760411/+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 1760613] Re: perl crashed with SIGABRT in _dbus_abort()
*** This bug is a duplicate of bug 1743216 *** https://bugs.launchpad.net/bugs/1743216 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1743216, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1760613/+attachment/5098824/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1760613/+attachment/5098826/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1760613/+attachment/5098831/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1760613/+attachment/5098832/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1760613/+attachment/5098833/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1760613/+attachment/5098834/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1760613/+attachment/5098835/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1743216 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1760613 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Apr 2 15:13:04 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2018-03-14 (18 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180312) Signal: 6 SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1760613/+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 1760614] Re: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured
** Tags removed: need-duplicate-check -- 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/1760614 Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured Status in cups package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcups2:i386 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 CupsErrorLog: Date: Mon Apr 2 14:42:56 2018 DuplicateSignature: package:libcups2:i386:2.1.3-4ubuntu0.4 Processing triggers for doc-base (0.10.7) ... 1 hinzugefügte Doc-base-Datei wird verarbeitet... dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package libcups2:i386 is already installed and configured InstallationDate: Installed on 2018-01-22 (69 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Precision M6500 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: cups Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0R1203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1760614/+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 1760614] [NEW] package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcups2:i386 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 CupsErrorLog: Date: Mon Apr 2 14:42:56 2018 DuplicateSignature: package:libcups2:i386:2.1.3-4ubuntu0.4 Processing triggers for doc-base (0.10.7) ... 1 hinzugefügte Doc-base-Datei wird verarbeitet... dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package libcups2:i386 is already installed and configured InstallationDate: Installed on 2018-01-22 (69 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Precision M6500 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: cups Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0R1203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 xenial -- 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/1760614 Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured Status in cups package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcups2:i386 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: i386 CupsErrorLog: Date: Mon Apr 2 14:42:56 2018 DuplicateSignature: package:libcups2:i386:2.1.3-4ubuntu0.4 Processing triggers for doc-base (0.10.7) ... 1 hinzugefügte Doc-base-Datei wird verarbeitet... dpkg: error processing package udev (--configure): package udev is already installed and configured ErrorMessage: package libcups2:i386 is already installed and configured InstallationDate: Installed on 2018-01-22 (69 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Precision M6500 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=9462ef34-9556-46db-94c6-ce06a3438530 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: cups Title: package libcups2:i386 2.1.3-4ubuntu0.4 failed to install/upgrade: package libcups2:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0R1203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Precision M6500 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1760614/+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 1760612] [NEW] ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/lib/chromium-browser/content_utility.service
Public bug reported: Was sending a previous report via a not opened chromium browser, and these output were displayed into the terminal: oem@lapubu:~$ ubuntu-bug apt-xapian-index Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= [2237:2281:0402/144056.666268:ERROR:nss_util.cc(724)] After loading Root Certs, loaded==false: NSS error code: -8018 [2237:2237:0402/144112.274986:ERROR:gpu_process_transport_factory.cc(1019)] Lost UI shared context. [2237:2237:0402/144130.282625:ERROR:navigation_entry_screenshot_manager.cc(135)] Invalid entry with unique id: 1 [2237:2281:0402/144619.994476:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/lib/chromium-browser/content_utility.service ^CTraceback (most recent call last): File "/usr/share/apport/apport-gtk", line 598, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 663, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 503, in run_report_bug self.file_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 1274, in file_report self.open_url(url) File "/usr/lib/python3/dist-packages/apport/ui.py", line 1147, in open_url (pid, status) = os.wait() ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic i686 ApportLog: ApportVersion: 2.20.9-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Mon Apr 2 15:13:17 2018 InstallationDate: Installed on 2013-10-21 (1624 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- 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/1760612 Title: ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/lib/chromium-browser/content_utility.service Status in apport package in Ubuntu: New Bug description: Was sending a previous report via a not opened chromium browser, and these output were displayed into the terminal: oem@lapubu:~$ ubuntu-bug apt-xapian-index Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= [2237:2281:0402/144056.666268:ERROR:nss_util.cc(724)] After loading Root Certs, loaded==false: NSS error code: -8018 [2237:2237:0402/144112.274986:ERROR:gpu_process_transport_factory.cc(1019)] Lost UI shared context. [2237:2237:0402/144130.282625:ERROR:navigation_entry_screenshot_manager.cc(135)] Invalid entry with unique id: 1 [2237:2281:0402/144619.994476:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/lib/chromium-browser/content_utility.service ^CTraceback (most recent call last): File "/usr/share/apport/apport-gtk", line 598, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 663, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 503, in run_report_bug self.file_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 1274, in file_report self.open_url(url) File "/usr/lib/python3/dist-packages/apport/ui.py", line 1147, in open_url (pid, status) = os.wait() ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic i686 ApportLog: ApportVersion: 2.20.9-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Mon Apr 2 15:13:17 2018 InstallationDate: Installed on 2013-10-21 (1624 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760612/+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 1742941] Re: zlib: improve crc32 performance on P8
--- Comment From bren...@br.ibm.com 2018-04-02 08:58 EDT--- (In reply to comment #45) > IBM, Can you please update this bug when this patch lands upstream? Yes, but I do not think we can make 18.04 anymore. Deferring to 18.10. ** Tags removed: targetmilestone-inin1804 ** Tags added: targetmilestone-inin1810 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Incomplete Status in zlib package in Ubuntu: New Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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 1760609] [NEW] liblxc-common missing Replaces on lxc1
Public bug reported: On upgrade from xenial to bionic: Selecting previously unselected package liblxc-common. Preparing to unpack .../liblxc-common_3.0.0-0ubuntu1_amd64.deb ... Unpacking liblxc-common (3.0.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/liblxc-common_3.0.0-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/init.lxc', which is also in package lxc1 2.0.8-0ubuntu1~16.04.2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1760609 Title: liblxc-common missing Replaces on lxc1 Status in lxc package in Ubuntu: New Bug description: On upgrade from xenial to bionic: Selecting previously unselected package liblxc-common. Preparing to unpack .../liblxc-common_3.0.0-0ubuntu1_amd64.deb ... Unpacking liblxc-common (3.0.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/liblxc-common_3.0.0-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/init.lxc', which is also in package lxc1 2.0.8-0ubuntu1~16.04.2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760609/+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 1760566] Re: mesa does not include vaExportSurfaceHandle support for vaapi
The attachment "0001-st-va-Enable-vaExportSurfaceHandle.patch" 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1760566 Title: mesa does not include vaExportSurfaceHandle support for vaapi Status in mesa package in Ubuntu: Confirmed Bug description: Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa misses one tiny patch to make modern AMD GPUs work with VAAPI on wayland / gbm / mir. We tried to get this into final 18.0 but was not yet accepted. The change itself is a minor. Without it a certain feature is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1760566/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
Thank you Mauro! One thing that worth to take a look is that you're using kernel 3.13, and this could be related to the high CPU utilization issue you're observing. We're changing the approach of this fix to not rely on cgmanager anymore. The CPU utilization issue is however another bug that needs investigation - I'll use the LP #1303649 for that. Cheers, Guilherme -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Committed Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1526960] Re: on_ac_power doesn't notice usb powersupply
This bug was fixed in the package powermgmt-base - 1.33 --- powermgmt-base (1.33) unstable; urgency=medium * Add some technical documentation. * Drop pre-pleistocene Replaces. * Multi-Arch: foreign. -- Adam Borowski Tue, 20 Mar 2018 14:19:42 +0100 powermgmt-base (1.32) unstable; urgency=medium * New maintainer. (Closes: #829683) * Redo the packaging using dh. * Rewrite the copyright file. * Drop ancient upstream changelog and README.Debian. * Consider USB power to be AC (despite being DC...). (Closes: LP#1526960) * Same for Apple charging bricks (untested). * Unbreak APM support (untested) — still available in i386 kernels. * But don't try to create APM devices — there's udev, and the fallback code was broken anyway. * Drop removal of pre-2006 conffiles. * Man page and description updates. * Move sbin manpages to section 8. (Closes: #476403) * VCS at Salsa. -- Adam Borowski Wed, 14 Mar 2018 01:54:43 +0100 ** Changed in: powermgmt-base (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1526960 Title: on_ac_power doesn't notice usb powersupply Status in powermgmt-base package in Ubuntu: Fix Released Bug description: Some ARM-Boards have more then one possible power-supply, for example you can power them also over USB. But /usr/bin/on_ac_power returns that there is no connected power-supply if its an usb power-supply. you can solve the Problem if you also allow an USB Device as a power-supply. This causes Problems like unattended-upgrades and other features are not working. You can do this if you patch the /usr/bin/on_ac_power script with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1526960/+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 1760590] Re: systemd-journald crashed with SIGABRT in fsync()
*** This bug is a duplicate of bug 1750855 *** https://bugs.launchpad.net/bugs/1750855 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1750855, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1760590/+attachment/5098747/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1760590/+attachment/5098750/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1760590/+attachment/5098757/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1760590/+attachment/5098759/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1760590/+attachment/5098760/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1760590/+attachment/5098761/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1760590/+attachment/5098762/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1750855 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1760590 Title: systemd-journald crashed with SIGABRT in fsync() Status in systemd package in Ubuntu: New Bug description: a ProblemType: Crash 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 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Mar 30 17:17:18 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-21 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) MachineType: LENOVO 80RS ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=49f3f5af-8bc4-4b34-b8d6-eef7c490fda3 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: fsync (fd=54) at ../sysdeps/unix/sysv/linux/fsync.c:27 ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so 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. Title: systemd-journald crashed with SIGABRT in fsync() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.modalias: dmi:bvnLENOVO:bvrD5CN46WW:bd03/15/2016:svnLENOVO:pn80RS:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RS dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1760590/+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 1760566] Re: mesa does not include vaExportSurfaceHandle support for vaapi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1760566 Title: mesa does not include vaExportSurfaceHandle support for vaapi Status in mesa package in Ubuntu: Confirmed Bug description: Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa misses one tiny patch to make modern AMD GPUs work with VAAPI on wayland / gbm / mir. We tried to get this into final 18.0 but was not yet accepted. The change itself is a minor. Without it a certain feature is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1760566/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
@serge-hallyn, I've attached output of as requested. I hadn't subscribed to notification. That's now been fixed. Missed your request when you posted it. Happy to do more. ** Attachment added: "trace-cgmanager-ubuntu-14.04.5-00.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1303649/+attachment/5098667/+files/trace-cgmanager-ubuntu-14.04.5-00.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1760566] [NEW] mesa does not include vaExportSurfaceHandle support for vaapi
Public bug reported: Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa misses one tiny patch to make modern AMD GPUs work with VAAPI on wayland / gbm / mir. We tried to get this into final 18.0 but was not yet accepted. The change itself is a minor. Without it a certain feature is not available. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: kodi mpv ubuntu vaapi vaexportsurfacehandle ** Patch added: "0001-st-va-Enable-vaExportSurfaceHandle.patch" https://bugs.launchpad.net/bugs/1760566/+attachment/5098636/+files/0001-st-va-Enable-vaExportSurfaceHandle.patch -- 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/1760566 Title: mesa does not include vaExportSurfaceHandle support for vaapi Status in mesa package in Ubuntu: New Bug description: Ubuntu prepares to ship libva 2.1 and mesa 18.x for Bionic. Mesa misses one tiny patch to make modern AMD GPUs work with VAAPI on wayland / gbm / mir. We tried to get this into final 18.0 but was not yet accepted. The change itself is a minor. Without it a certain feature is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1760566/+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 1760371] Re: LightDM and GDM fail to start after systemd update
Here is also the boot history, to match against the software install/update history log that I attached earlier. The issue occurred on the first reboot on March 31st, the prior successful reboot was March 13th. The history.log file shows updates to systemd and openbox on March 25th that may be relevant to this issue, but I do not know what else to do to investigate the underlying cause. % last reboot -f wtmp.1 reboot system boot 4.4.0-116-generi Sat Mar 31 18:35 still running reboot system boot 4.4.0-116-generi Sat Mar 31 10:06 still running reboot system boot 4.4.0-116-generi Sat Mar 31 08:54 - 17:05 (08:11) reboot system boot 4.4.0-116-generi Sat Mar 31 05:33 - 17:05 (11:32) reboot system boot 4.4.0-116-generi Sat Mar 31 05:13 - 12:33 (07:20) reboot system boot 4.4.0-116-generi Sat Mar 31 04:32 - 12:33 (08:00) reboot system boot 4.4.0-112-generi Sat Mar 31 04:24 - 12:33 (08:08) reboot system boot 4.4.0-116-generi Sat Mar 31 04:08 - 11:23 (07:15) reboot system boot 4.4.0-116-generi Sat Mar 31 04:02 - 11:23 (07:21) reboot system boot 4.4.0-116-generi Tue Mar 13 19:39 - 11:23 (17+15:44) reboot system boot 4.4.0-116-generi Sat Mar 10 09:32 - 11:23 (21+00:51) reboot system boot 4.4.0-116-generi Sat Mar 10 04:09 - 16:48 (12:38) reboot system boot 4.4.0-116-generi Mon Mar 5 08:56 - 16:48 (5+07:51) reboot system boot 4.4.0-116-generi Sat Mar 3 08:17 - 16:10 (2+07:53) reboot system boot 4.4.0-116-generi Sat Mar 3 04:36 - 14:05 (09:29) -- 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/1760371 Title: LightDM and GDM fail to start after systemd update Status in lightdm package in Ubuntu: New Bug description: 1) Output of lsb_release -rd: Description: Ubuntu 16.04.4 LTS Release: 16.04 2) Output of apt-cache policy lightdm: lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What I expected to happen: - Expected the display manager to take me to the lightdm user login screen. 4) What happened instead: - lightdm made 5 attempts to start before failing. Failure messages were "failed to start Detect the available GPUs and deal with any system changes" and "Failed to start Light Display Manager". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Mar 31 17:43:08 2018 InstallationDate: Installed on 2015-11-23 (859 days ago) InstallationMedia: ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2017-01-18 (437 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760371/+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
