[Touch-packages] [Bug 1568772] Re: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
** Bug watch added: Debian Bug tracker #959170 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959170 ** Also affects: alsa-driver (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959170 Importance: Unknown Status: Unknown ** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1568772 Title: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: Unknown Bug description: Get that error logged into journalctl, on a fresh xenial 64 bits installed from mini.iso and sharing a /home partition with a wily installation. No third party package, only genuine default install. Note that sound has no trouble; only this logged. There is no sound card on this system, only a mobo chipset. systemd-udevd[412]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. systemd-udevd[407]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Maybe its related to the 'i' aka '--no-init-fallback' found here: http://manpages.ubuntu.com/manpages/wily/man1/alsactl.1.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1755 F pulseaudio /dev/snd/pcmC0D0p: oem1755 F...m pulseaudio /dev/snd/controlC0: oem1755 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 11 13:50:55 2016 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772/+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 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
This problem still exists in noble:
# journalctl | grep ConfigurationDirectory
Apr 15 11:00:12 vougeot (uetoothd)[3112]: bluetooth.service:
ConfigurationDirectory 'bluetooth' already exists but the mode is different.
(File system: 755 ConfigurationDirectoryMode: 555)
** Tags added: noble
--
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/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
Confirmed
Status in bluez package in Debian:
Confirmed
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 1966203] Re: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1."
** Tags added: noble -- 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/1966203 Title: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." Status in snapd: Confirmed Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Hi, I got hit by this bug after a mantic -> noble upgrade on a desktop system. -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 1899749] Re: Please add DCCP to rarely used protocols
** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
This bug seems to be fixed in Ubuntu noble. Thanks! ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in Ubuntu: Fix Released Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847493/+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 1446865] Re: KDE5/Qt5 does not support session restoration
** No longer affects: qt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration Status in KDE Base Workspace: Fix Released Status in plasma-workspace package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: KDE5/Qt5 does not support proper session restoration. ProblemType: Bug DistroRelease: Ubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+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 1568094] Re: Many error message such as "Start request repeated too quickly."
** No longer affects: laptop-mode-tools (Ubuntu) ** Changed in: laptop-mode-tools (Ubuntu Xenial) Status: New => Fix Released -- 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/1568094 Title: Many error message such as "Start request repeated too quickly." Status in systemd package in Ubuntu: Fix Released Status in laptop-mode-tools source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: * Analysis: The error messages are caused by a bad interaction between systemd and laptop-mode-tools. * Fixes: There is a fix in systemd: https://github.com/systemd/systemd/pull/3148 The problem can also be fixed by updating laptop-mode-tools. * Symptoms: Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu. Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System. Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device. Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen. Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database. Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen... Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu. Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device. Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System. Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database. Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu. Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device. Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System. Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen. Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu. Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root Device. Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database. Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System. Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary Formats. Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen. Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start request repeated too quickly. Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests to Console Directory Watch. Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.servi
[Touch-packages] [Bug 1968857] [NEW] upgading to jammy leaves obsolete conffiles
Public bug reported:
Hi,
after upgrading my system from impish to jammy, it is left with the
following obsolete conffiles:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
c4dbd2117c52f367f1e8b8c229686b10 obsolete
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf
2adb9d174807b0a3521fabf03792fbc8 obsolete
/etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: polkitd 0.105-33
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Apr 13 10:58:03 2022
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
modified.conffile..etc.pam.d.polkit-1: [deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf:
[deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf:
[deleted]
** Affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Affects: policykit-1 (Debian)
Importance: Unknown
Status: Unknown
** Tags: amd64 apport-bug jammy
** Bug watch added: Debian Bug tracker #1006203
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006203
** Also affects: policykit-1 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006203
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1968857
Title:
upgading to jammy leaves obsolete conffiles
Status in policykit-1 package in Ubuntu:
New
Status in policykit-1 package in Debian:
Unknown
Bug description:
Hi,
after upgrading my system from impish to jammy, it is left with the
following obsolete conffiles:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
c4dbd2117c52f367f1e8b8c229686b10 obsolete
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf
2adb9d174807b0a3521fabf03792fbc8 obsolete
/etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: polkitd 0.105-33
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Apr 13 10:58:03 2022
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
modified.conffile..etc.pam.d.polkit-1: [deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf:
[deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf:
[deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1968857/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Great, thank you for the fix! -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Tags added: lunar -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1899749] Re: Please add DCCP to rarely used protocols
** Tags removed: groovy hirsute ** Tags added: jammy kinetic lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 1876068] Re: DeprecationWarning: an integer is required
The bug is now fixed. Thanks! ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- 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/1876068 Title: DeprecationWarning: an integer is required Status in apport package in Ubuntu: Fix Released Bug description: Hi, when I use ubuntu-bug to report a bug, I see the following python deprecation warning: $ ubuntu-bug apport-kde /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 Uname: Linux 5.6.7-050607-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 30 11:16:12 2020 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/1876068/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
** Tags removed: eoan groovy hirsute ** Tags added: jammy kinetic lunar -- 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/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+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 2013324] [NEW] gnome-desktop-testing-runner finds a crash in /usr/libexec/installed-tests/gtk+/scrolledwindow
Public bug reported: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 30 12:05:24 2023 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2013324 Title: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed- tests/gtk+/scrolledwindow Status in gtk+3.0 package in Ubuntu: New Bug description: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 30 12:05:24 2023 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2013324/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
Hi, the recentmanager test seems to run OK, but it generates a crash file: $ /usr/libexec/installed-tests/gtk+/recentmanager TAP version 13 # random seed: R02S11301a509f5dd29b12965d40796527a7 1..8 # Start of recent-manager tests # GLib-GIO-DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs? ok 1 /recent-manager/get-default ok 2 /recent-manager/add ok 3 /recent-manager/add-many ok 4 /recent-manager/has-item ok 5 /recent-manager/move-item ok 6 /recent-manager/lookup-item ok 7 /recent-manager/remove-item ok 8 /recent-manager/purge # End of recent-manager tests $ ls -l /var/crash/ total 1156 -rw-r- 1 bonnaudl whoopsie 1175991 Mar 30 12:10 _usr_libexec_installed-tests_gtk+_recentmanager.1000.crash -rw-r--r-- 1 bonnaudl whoopsie 0 Mar 30 12:10 _usr_libexec_installed-tests_gtk+_recentmanager.1000.upload -rw--- 1 whoopsie whoopsie 37 Mar 30 12:10 _usr_libexec_installed-tests_gtk+_recentmanager.1000.uploaded -- 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/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
This bug is very old, and I do not see it any longer on a newer Dell laptop and a newer Ubuntu release. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1568143] Re: apport-kde crashed with SIGSEGV
This bug is very old, and I am no longer seeing this crash. ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- 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/1568143 Title: apport-kde crashed with SIGSEGV Status in apport package in Ubuntu: Fix Released Bug description: Random crash ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-kde 2.20.1-0ubuntu1 Uname: Linux 4.5.0-040500-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:136:9666180:2016-04-08 20:43:09.867370128 +0200:2016-04-08 20:43:10.867370128 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash CurrentDesktop: KDE Date: Fri Apr 8 20:43:03 2016 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde systemd ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f666ccc6105:mov(%rax),%rax PC (0x7f666ccc6105) ok source "(%rax)" (0x7575757575757575) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-35m-x86_64-linux-gnu.so QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:987 (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() (this=0x7f66691ccb40 <(anonymous namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, __in_chrg=) at accessible/qaccessiblecache_p.h:60 (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() (this=0x7f66691ccb40 <(anonymous namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, __in_chrg=) at accessible/qaccessiblecache.cpp:46 __run_exit_handlers (status=1, listp=0x7f6670b925f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 Title: apport-kde crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2016-03-31 (8 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare staff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1568143/+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 1353792] Re: Detect renamed files and handle by renaming instead of delete/re-send
** Bug watch added: Samba Bugzilla #2294 https://bugzilla.samba.org/show_bug.cgi?id=2294 ** Also affects: rsync via https://bugzilla.samba.org/show_bug.cgi?id=2294 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1353792 Title: Detect renamed files and handle by renaming instead of delete/re-send Status in rsync: Unknown Status in rsync package in Ubuntu: Confirmed Bug description: There has been a report in rsync[0] about this issue since 2005, some patches has been developed detect-renamed[1] and detect-renamed-lax[2] to target the issue, I think it would be great if Ubuntu could patch itself rsync to provide such feature. I've updated those[3] patches[4] to apply to the latest rsync package (3.1.1) and they're working great in my own setup, I also put them in a ppa[5] for further testing. The patches aren't intrusive, they provide some extra flags (--detect-renamed, --detec-moved and --detect-renamed-lax) so I think it shouldn't be disastrous for those who won't use the extra features. [0] https://bugzilla.samba.org/show_bug.cgi?id=2294 [1] https://bugzilla.samba.org/attachment.cgi?id=7435 [2] http://gitweb.samba.org/?p=rsync-patches.git;a=blob;f=detect-renamed-lax.diff;h=4cd23bd4524662f1d0db0bcc90336a77d0bb61c9;hb=HEAD [3] https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed.diff [4] https://github.com/chilicuil/learn/blob/master/patches/rsync-3.1.1-trusty-detect-renamed-lax.diff [5] https://launchpad.net/~minos-archive/+archive/ubuntu/main/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1353792/+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 1968857] Re: Upgrading to jammy leaves obsolete conffiles
Thank you for the fix!
** Summary changed:
- upgading to jammy leaves obsolete conffiles
+ Upgrading to jammy leaves obsolete conffiles
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1968857
Title:
Upgrading to jammy leaves obsolete conffiles
Status in policykit-1 package in Ubuntu:
Fix Committed
Status in policykit-1 package in Debian:
Fix Released
Bug description:
Hi,
after upgrading my system from impish to jammy, it is left with the
following obsolete conffiles:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
c4dbd2117c52f367f1e8b8c229686b10 obsolete
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf
2adb9d174807b0a3521fabf03792fbc8 obsolete
/etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: polkitd 0.105-33
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Apr 13 10:58:03 2022
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
modified.conffile..etc.pam.d.polkit-1: [deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf:
[deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf:
[deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1968857/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Tags added: jammy kinetic -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1915314] [NEW] systemd-xdg-autostart-generator: gnome-systemd-autostart-condition not found: No such file or directory
Public bug reported: Hi, in the kernel logs I see several error messages such as those: # dmesg | grep gnome-systemd-autostart-condition [ 37.704325] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.704421] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.704548] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.705007] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.705094] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory It seems that gnome-systemd-autostart-condition is not available anywhere in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.1 Uname: Linux 5.10.15-051015-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 10 19:58:30 2021 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.15-051015-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 RebootRequiredPkgs: linux-base linux-base SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0VYDFF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd10/21/2020:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.product.sku: 0817 dmi.sys.vendor: Dell Inc. modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2020-10-25T12:26:20.218696 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1915314 Title: systemd-xdg-autostart-generator: gnome-systemd-autostart-condition not found: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hi, in the kernel logs I see several error messages such as those: # dmesg | grep gnome-systemd-autostart-condition [ 37.704325] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.704421] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.704548] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.705007] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory [ 37.705094] systemd-xdg-autostart-generator[2387]: gnome-systemd-autostart-condition not found: No such file or directory It seems that gnome-systemd-autostart-condition is not available anywhere in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1.1 Uname: Linux 5.10.15-051015-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 10 19:58:30 2021 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.15-051015-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 RebootRequiredPkgs: linux-base linux-base SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2020 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0VYDFF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd10/21/2020:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:r
[Touch-packages] [Bug 1922414] [NEW] ssh-agent fails to start (has_option: command not found)
Public bug reported: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probabl
[Touch-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
The /etc/X11/Xsession.d/90x11-common_ssh-agent file is the same in Ubuntu groovy and hirsute. Therefore, the problem is elsewhere. -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
The has_option shell function is not defined in the same file: - in Ubuntu groovy it is defined in /etc/X11/Xsession.d/20x11-common_process-args - in Ubuntu hirsute it is defined in /etc/X11/Xsession -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/+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 1922485] Re: systemd: slice: Failed to migrate controller cgroups
This bugs also exists in Arch Linux: https://bugs.archlinux.org/task/68832 (launchpad did not accept the URL) and Debian. It has been fixed in Debian. -- 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/1922485 Title: systemd: slice: Failed to migrate controller cgroups Status in systemd: Unknown Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: Hi, during boot those error messages appear in the logs: # journalctl | grep controller [...] Apr 02 20:16:23 vougeot systemd[3155]: -.slice: Failed to migrate controller cgroups from /user.slice/user-108.slice/user@108.service, ignoring: Permission denied Apr 02 20:16:31 vougeot systemd[3512]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu2 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 4 13:29:25 2021 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-04-02T13:37:46.839143 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1922485/+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 1922485] [NEW] systemd: slice: Failed to migrate controller cgroups
Public bug reported: Hi, during boot those error messages appear in the logs: # journalctl | grep controller [...] Apr 02 20:16:23 vougeot systemd[3155]: -.slice: Failed to migrate controller cgroups from /user.slice/user-108.slice/user@108.service, ignoring: Permission denied Apr 02 20:16:31 vougeot systemd[3512]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu2 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 4 13:29:25 2021 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-04-02T13:37:46.839143 ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug hirsute ** Bug watch added: Debian Bug tracker #977681 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977681 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977681 Importance: Unknown Status: Unknown ** Bug watch added: github.com/systemd/systemd/issues #18047 https://github.com/systemd/systemd/issues/18047 ** Also affects: systemd via https://github.com/systemd/systemd/issues/18047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1922485 Title: systemd: slice: Failed to migrate controller cgroups Status in systemd: Unknown Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: Hi, during boot those error messages appear in the logs: # journalctl | grep controller [...] Apr 02 20:16:23 vougeot systemd[3155]: -.slice: Failed to migrate controller cgroups from /user.slice/user-108.slice/user@108.service, ignoring: Permission denied Apr 02 20:16:31 vougeot systemd[3512]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu2 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 4 13:29:25 2021 MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2021-04-02T13:37:46.839143 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1922485/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1876068] Re: DeprecationWarning: an integer is required
** Tags added: groovy hirsute -- 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/1876068 Title: DeprecationWarning: an integer is required Status in apport package in Ubuntu: Confirmed Bug description: Hi, when I use ubuntu-bug to report a bug, I see the following python deprecation warning: $ ubuntu-bug apport-kde /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport-kde 2.20.11-0ubuntu27 Uname: Linux 5.6.7-050607-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 30 11:16:12 2020 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/1876068/+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 1899749] Re: Please add DCCP to rarely used protocols
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
** Tags added: focal groovy hirsute -- 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/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681249] Re: tracker-extract crashed with signal 31 in chdir()
I am closing this bug since it is very old, tracker evolved a lot since then, and tracker no longer crashes on my system. ** Changed in: tracker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1681249 Title: tracker-extract crashed with signal 31 in chdir() Status in tracker package in Ubuntu: Fix Released Bug description: tracker crash while indexing my homedir ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: tracker-extract 1.12.0-0ubuntu1 Uname: Linux 4.10.8-041008-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 8 14:00:45 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/tracker/tracker-extract ExecutableTimestamp: 1490023113 JournalErrors: No journal files were found. -- No entries -- ProcCmdline: /usr/lib/tracker/tracker-extract ProcCwd: /home/bonnaudl Signal: 31 SourcePackage: tracker Title: tracker-extract crashed with signal 31 in chdir() UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1681249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
Hi, the bug is still there on an Ubuntu 23.10/mantic system: # journalctl | grep has_option Sep 22 13:46:02 xeelee /usr/libexec/gdm-x-session[2101]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Sep 22 13:46:03 xeelee /usr/libexec/gdm-x-session[2123]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Sep 22 13:46:03 xeelee /usr/libexec/gdm-x-session[2150]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ** Tags added: lunar mantic -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 2013324] Re: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed-tests/gtk+/scrolledwindow
I am closing this bug since it has been fixed in mantic. Thanks! ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2013324 Title: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed- tests/gtk+/scrolledwindow Status in Ubuntu: Fix Released Bug description: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 30 12:05:24 2023 SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2013324/+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 1971242] Re: printing PDF appears always grey, no color
The bug was in cups.
** Changed in: okular (Ubuntu)
Status: Confirmed => Invalid
** Changed in: atril (Ubuntu)
Status: Confirmed => Invalid
--
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/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Invalid
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Invalid
Status in cups source package in Jammy:
Fix Released
Status in cups source package in Lunar:
Fix Released
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
The error messages are still there in mantic: # journalctl | grep unshare Sep 24 10:14:08 vougeot (udev-worker)[1373]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Sep 24 10:14:08 vougeot (udev-worker)[1373]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Sep 24 10:14:08 vougeot (udev-worker)[1367]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. ** Changed in: snapd (Ubuntu) Status: New => Confirmed ** Tags added: mantic ** Summary changed: - Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 + journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." -- 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/1966203 Title: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." Status in snapd: Confirmed Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid ** Changed in: lightdm Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: Invalid Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Invalid Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1899749] Re: Please add DCCP to rarely used protocols
** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
** Tags added: mantic -- 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/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+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 2037207] [NEW] Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
Public bug reported:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
New
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+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 2037212] [NEW] ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Public bug reported:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Affects: bluez (Debian)
Importance: Unknown
Status: Unknown
** Tags: amd64 apport-bug mantic
** Bug watch added: Debian Bug tracker #1017988
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
** Also affects: bluez (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
Importance: Unknown
Status: Unknown
--
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/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
New
Status in bluez package in Debian:
Unknown
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this b
[Touch-packages] [Bug 2037207] Re: Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
>Is this affecting your system in any way?
No.
>Or are you just reporting the fact that a message is logged?
That is the problem. A system with messy logs is harder to debug.
** Changed in: systemd (Ubuntu)
Status: Incomplete => 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/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
New
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+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 2037207] Re: Error message about memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL
OK, thanks for looking at this issue!
I am already looking forward to Ubuntu 24.04 :>.
--
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/2037207
Title:
Error message about memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
Hi,
here is the problem:
$ journalctl | grep memfd_create
Sep 24 10:14:08 vougeot kernel: memfd_create() without MFD_EXEC nor
MFD_NOEXEC_SEAL, pid=1 'systemd'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 10:20:57 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to mantic on 2023-09-22 (2 days ago)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037207/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
The bug has been fixed in Debian just by removing a patch: openjdk-11 (11~28-3) unstable; urgency=medium . * Drop the jdk-freetypeScaler-crash patch. Closes: #905718. ** Bug watch added: Debian Bug tracker #905718 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905718 ** Also affects: openjdk-11 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905718 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Confirmed Status in openjdk-11 package in Debian: Unknown Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
> updating other gtk pacakges did [fix the issue] Indeed. I confirm that on my Debian sid+experimental system, fonts look OK in openjdk-11. I tried to investigate the problem in Ubuntu cosmic by first trying to determine which fonts are used by the JRE. I used this command: cat /proc/$(pidof java)/maps | grep font and only found files from /var/cache/fontconfig/ and no actual font files. Other applications have files from /usr/share/fonts/, but not the JRE. Without this I do not know where to look further :<... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Confirmed Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Confirmed Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
** Tags added: disco eoan -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1847493] [NEW] recentmanager crashed with signal 5 in _g_log_abort()
Public bug reported: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash eoan ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+attachment/5295975/+files/JournalErrors.txt ** Information type changed from Private to Public -- 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/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in gtk+3.0 package in Ubuntu: New Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847493/+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 1766317] [NEW] package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1
Public bug reported: Setting up rsyslog (8.32.0-1ubuntu3) ... Installing new version of config file /etc/init.d/rsyslog ... Installing new version of config file /etc/logrotate.d/rsyslog ... Installing new version of config file /etc/rsyslog.conf ... The user `syslog' is already a member of `adm'. Job for rsyslog.service failed because the control process exited with error code. See "systemctl status rsyslog.service" and "journalctl -xe" for details. invoke-rc.d: initscript rsyslog, action "restart" failed. ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2018-04-23 19:40:06 CEST; 8ms ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 31888 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE) Main PID: 31888 (code=exited, status=1/FAILURE) dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: rsyslog 8.32.0-1ubuntu3 Uname: Linux 4.16.3-041603-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Mon Apr 23 19:40:06 2018 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: rsyslog Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1766317 Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1 Status in rsyslog package in Ubuntu: New Bug description: Setting up rsyslog (8.32.0-1ubuntu3) ... Installing new version of config file /etc/init.d/rsyslog ... Installing new version of config file /etc/logrotate.d/rsyslog ... Installing new version of config file /etc/rsyslog.conf ... The user `syslog' is already a member of `adm'. Job for rsyslog.service failed because the control process exited with error code. See "systemctl status rsyslog.service" and "journalctl -xe" for details. invoke-rc.d: initscript rsyslog, action "restart" failed. ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2018-04-23 19:40:06 CEST; 8ms ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 31888 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE) Main PID: 31888 (code=exited, status=1/FAILURE) dpkg: error processing package rsyslog (--configure): installed rsyslog package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: rsyslog 8.32.0-1ubuntu3 Uname: Linux 4.16.3-041603-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Mon Apr 23 19:40:06 2018 ErrorMessage: installed rsyslog package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: rsyslog Title: package rsyslog 8.32.0-1ubuntu3 failed to install/upgrade: installed rsyslog package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766317/+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 1766337] [NEW] uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte
Public bug reported:
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070:
invalid continuation byte
It can also be seen here:
https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1766337
Title:
uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
decode byte; invalid continuation byte
Status in apport package in Ubuntu:
New
Bug description:
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070:
invalid continuation byte
It can also be seen here:
https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
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/1766337/+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 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte
Thank you for the fix!
--
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/1766337
Title:
uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
decode byte; invalid continuation byte
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
New
Bug description:
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070:
invalid continuation byte
It can also be seen here:
https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
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/1766337/+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 1761858] Re: libx11-6-dbgsym should be in section "debug" insead of section "libs"
** Summary changed: - libx11-6-dbgsym should be insection "debug" insead of section "libs" + libx11-6-dbgsym should be in section "debug" insead of section "libs" ** Summary changed: - libx11-6-dbgsym should be in section "debug" insead of section "libs" + libx11-6-dbgsym should be in section "debug" instead of section "libs" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1761858 Title: libx11-6-dbgsym should be in section "debug" instead of section "libs" Status in libx11 package in Ubuntu: New Bug description: Hi, the problem is that deborphan lists this package as removable, whereas I want to keep it: $ deborphan [...] libx11-6-dbgsym:amd64 It comes from the fact that libx11-6-dbgsym is in section "libs": $ dpkg -s libx11-6-dbgsym [...] Section: libs whereas it should be in section "devel". All other *-dbgsym packages on my system belong to this section. For instance: $ dpkg -s libqt5gui5-dbgsym [...] Section: debug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6-dbgsym 2:1.6.4-3 Uname: Linux 4.15.15-041515-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Apr 6 22:00:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1761858/+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 1761712] Re: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()
I unmerged this bug because the symptoms are the same, but the cause is different. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1761712 Title: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value() Status in gconf package in Ubuntu: New Bug description: This is caused by a missing setting in org.gnome.desktop.wm.preferences. This can be seen thanks to this error message that appears in the backtrace: Settings schema 'org.gnome.desktop.wm.preferences' does not contain a key named 'application-based'" ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gconf2 3.2.6-4ubuntu1 Uname: Linux 4.15.15-041515-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 6 10:48:45 2018 ExecutablePath: /usr/bin/gsettings-data-convert ExecutableTimestamp: 1496904803 ProcCmdline: gsettings-data-convert ProcCwd: /home/bonnaudl Signal: 5 SourcePackage: gconf StacktraceTop: g_settings_schema_get_value (schema=0x562a8ac5da30, key=0x562a8ac6b810 "application-based") at ../../../../gio/gsettingsschema.c:970 g_settings_schema_key_init (key=key@entry=0x7ffcbae8c490, schema=0x562a8ac5da30, name=name@entry=0x562a8ac6b810 "application-based") at ../../../../gio/gsettingsschema.c:1249 g_settings_set_value (settings=settings@entry=0x562a8ac5dc30 [GSettings], key=key@entry=0x562a8ac6b810 "application-based", value=0x562a8ac6f320) at ../../../../gio/gsettings.c:1563 g_settings_set (settings=0x562a8ac5dc30 [GSettings], key=0x562a8ac6b810 "application-based", format=) at ../../../../gio/gsettings.c:1670 handle_file (filename=) at gsettings-data-convert.c:295 Title: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value() UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1761712/+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 1761858] [NEW] libx11-6-dbgsym should be insection "debug" insead of section "libs"
Public bug reported: Hi, the problem is that deborphan lists this package as removable, whereas I want to keep it: $ deborphan [...] libx11-6-dbgsym:amd64 It comes from the fact that libx11-6-dbgsym is in section "libs": $ dpkg -s libx11-6-dbgsym [...] Section: libs whereas it should be in section "devel". All other *-dbgsym packages on my system belong to this section. For instance: $ dpkg -s libqt5gui5-dbgsym [...] Section: debug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6-dbgsym 2:1.6.4-3 Uname: Linux 4.15.15-041515-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Apr 6 22:00:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1761858 Title: libx11-6-dbgsym should be insection "debug" insead of section "libs" Status in libx11 package in Ubuntu: New Bug description: Hi, the problem is that deborphan lists this package as removable, whereas I want to keep it: $ deborphan [...] libx11-6-dbgsym:amd64 It comes from the fact that libx11-6-dbgsym is in section "libs": $ dpkg -s libx11-6-dbgsym [...] Section: libs whereas it should be in section "devel". All other *-dbgsym packages on my system belong to this section. For instance: $ dpkg -s libqt5gui5-dbgsym [...] Section: debug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6-dbgsym 2:1.6.4-3 Uname: Linux 4.15.15-041515-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Apr 6 22:00:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ve
[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first
On my 17.10 systems, this bug no longer shows up.
--
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/1502173
Title:
Python warnings: modules imported without specifying a version first
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
Fix Released
Bug description:
[Description]
Users receive warnings about importing of python modules without a version
being specified. While this isn't a big deal in itself we get lots of bug
reports from people about this issue since it is so obvious. Given that Ubuntu
16.04 is an LTS release we should fix this and prevent further reporting of the
issue.
[Test Case]
1) run /usr/share/apport/apport-gtk in a terminal
2) Observe the following
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
with the version of apport in -proposed you'll no longer receive the
warning.
[Regression Potential]As with any SRU this could cause a regression in
the software if the fix is typo'ed so review it carefully. If there
isn't a typo and then the chance of a regression is very very very
low.
Original Description
Hi,
here is the problem:
$ /usr/share/apport/apport-gtk
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
ProblemType: BugDistroRelease: Ubuntu 15.10
Package: apport-gtk 2.19-0ubuntu1
Uname: Linux 4.2.2-040202-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 2 16:17:14 2015
EcryptfsInUse: Yes
PackageArchitecture: allSourcePackage: apport
UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+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 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted
The error messages about the sap-server are not there any longer in Ubuntu 17.10. Thanks for the fix! ** Changed in: bluez (Ubuntu) Status: Incomplete => Fix Released -- 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/1629632 Title: Sap driver initialization failed, sap-server: Operation not permitted Status in bluez package in Ubuntu: Fix Released Status in bluez package in Debian: New Bug description: Hi, here are are messages from the bluetooth daemon: $ journalctl -b | grep bluetoothd Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41 Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 initialized Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for "Service Changed" characteristic Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed. Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted (1) There are at least 2 errors concerning: - handles - Sap driver/server ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 09:59:43 2016 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:57:27:6F ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:1974 acl:0 sco:0 events:132 errors:0 TX bytes:6033 acl:0 sco:0 commands:132 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+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 1795271] [NEW] incorrect setting in 10_ubuntu-settings.gschema.override
Public bug reported: Hi, each time I install or upgrade a package I see the following error message: Processing triggers for libglib2.0-0:amd64 (2.58.1-2) ... No such key “notify-with-tray” in schema “org.gnome.evolution.calendar” as specified in override file “/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override”; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-settings 18.10.3 Uname: Linux 4.18.10-041810-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: KDE Date: Fri Sep 28 23:40:29 2018 PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to cosmic on 2018-09-28 (0 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795271 Title: incorrect setting in 10_ubuntu-settings.gschema.override Status in ubuntu-settings package in Ubuntu: New Bug description: Hi, each time I install or upgrade a package I see the following error message: Processing triggers for libglib2.0-0:amd64 (2.58.1-2) ... No such key “notify-with-tray” in schema “org.gnome.evolution.calendar” as specified in override file “/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override”; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-settings 18.10.3 Uname: Linux 4.18.10-041810-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: KDE Date: Fri Sep 28 23:40:29 2018 PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to cosmic on 2018-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795271/+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 1706690] Re: [needs-packaging] Please sync openssl from debian stretch
The problem is till there. ** Changed in: openssl (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1706690 Title: [needs-packaging] Please sync openssl from debian stretch Status in openssl package in Ubuntu: New Bug description: OpenSSL 1.1 contains major improvements over 1.0. https://packages.debian.org/stretch/openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1706690/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
** Also affects: consolekit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in consolekit package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 1447154] Re: systemd tries to start pulseaudio several times
This bug still exists in Ubuntu 15.10 and this package version: Package: pulseaudio Version: 1:6.0-0ubuntu12 $ journalctl | grep pulseaudio oct. 02 11:05:12 vougeot pulseaudio[2182]: [pulseaudio] pid.c: Daemon already running. [...] oct. 02 11:05:26 vougeot pulseaudio[2954]: [pulseaudio] pid.c: Daemon already running. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1447154 Title: systemd tries to start pulseaudio several times Status in pulseaudio package in Ubuntu: Confirmed Bug description: Here is what I see in journalctl: # journalctl | grep pulseaudio Apr 21 22:01:16 xeelee pulseaudio[2330]: [pulseaudio] pid.c: Daemon already running. Apr 21 22:01:33 xeelee pulseaudio[2911]: [pulseaudio] pid.c: Daemon already running. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 2895 F pulseaudio CurrentDesktop: KDE Date: Wed Apr 22 14:46:51 2015 SourcePackage: pulseaudio UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1447154/+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 1502173] [NEW] Python warnings: modules imported without specifying a version first
Public bug reported:
Hi,
here is the problem:
$ /usr/share/apport/apport-gtk
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: apport-gtk 2.19-0ubuntu1
Uname: Linux 4.2.2-040202-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 2 16:17:14 2015
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug gnome3-ppa third-party-packages wily
--
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/1502173
Title:
Python warnings: modules imported without specifying a version first
Status in apport package in Ubuntu:
New
Bug description:
Hi,
here is the problem:
$ /usr/share/apport/apport-gtk
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: apport-gtk 2.19-0ubuntu1
Uname: Linux 4.2.2-040202-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 2 16:17:14 2015
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+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 1447146] Re: NetworkManager assertion failure: dir != NULL
I am closing this bug because it no longer exists in current wily. ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1447146 Title: NetworkManager assertion failure: dir != NULL Status in network-manager package in Ubuntu: Fix Released Bug description: Here is an error seen in journalctl: Apr 21 22:01:13 xeelee NetworkManager[1493]: (NetworkManager:1493): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 22 14:24:07 2015 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 802-3-ethernet 1429705273 Wed 22 Apr 2015 02:21:13 PM CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1447146/+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 1447142] Re: systemd: ntpdate is started too soon (before the network)
This bug still exists in wily and this package version: Package: ntp Version: 1:4.2.6.p5+dfsg-3ubuntu8 The error even occurs several times: oct. 02 11:05:10 vougeot ntpdate[1464]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:10 vougeot ntpdate[1464]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:10 vougeot ntpdate[1464]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:10 vougeot ntpdate[1464]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:10 vougeot ntpd[1597]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 oct. 02 11:05:10 vougeot ntpd[1597]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 oct. 02 11:05:10 vougeot ntpd[1597]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 oct. 02 11:05:10 vougeot ntpd[1597]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 oct. 02 11:05:11 vougeot ntpdate[1902]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:11 vougeot ntpdate[1902]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:11 vougeot ntpdate[1902]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:11 vougeot ntpdate[1902]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:11 vougeot ntpd[1997]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 oct. 02 11:05:11 vougeot ntpd[1997]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 oct. 02 11:05:11 vougeot ntpd[1997]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 oct. 02 11:05:11 vougeot ntpd[1997]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 oct. 02 11:05:13 vougeot ntpd_intres[1999]: host name not found: 0.ubuntu.pool.ntp.org oct. 02 11:05:13 vougeot ntpd_intres[1999]: host name not found: 1.ubuntu.pool.ntp.org oct. 02 11:05:13 vougeot ntpd_intres[1999]: host name not found: 2.ubuntu.pool.ntp.org oct. 02 11:05:13 vougeot ntpd_intres[1999]: host name not found: 3.ubuntu.pool.ntp.org -- 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/1447142 Title: systemd: ntpdate is started too soon (before the network) Status in ntp package in Ubuntu: Confirmed Bug description: Here is what I see in journalctl: ntpdate cannot do DNS resolution because NetworkManager has not finished configuring the network interface. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: init! Apr 21 22:01:13 xeelee NetworkManager[1493]: update_system_hostname Apr 21 22:01:13 xeelee NetworkManager[1493]:interface-parser: parsing file /etc/network/interfaces Apr 21 22:01:13 xeelee NetworkManager[1493]:interface-parser: finished parsing file /etc/network/interfaces Apr 21 22:01:13 xeelee NetworkManager[1493]: management mode: unmanaged Apr 21 22:01:13 xeelee NetworkManager[1493]: devices added (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlan0, Apr 21 22:01:13 xeelee NetworkManager[1493]: device added (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlan0, Apr 21 22:01:13 xeelee NetworkManager[1493]: devices added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, Apr 21 22:01:13 xeelee NetworkManager[1493]: device added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, i Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: devices added (path: /sys/devices/virtual/net/lo, iface: lo) Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], no ATA CHECK POWER STATUS support, ignoring -n Directive Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configur Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], is SMART capable. Adding to "monitor" list. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: end _init. Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], state read from /var/lib/smartmontools/smartd.WDC_WD40EZRX_00SPE Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host ntp.ubuntu.com: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the Ne Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], opened Apr 21 22:01:13 xeelee ntpdate[1563]: no servers can be used, exiting Apr 21 22:01:13 xeelee NetworkManager[1493]: Loaded plugin ke
[Touch-packages] [Bug 1502183] [NEW] 10_ubuntu-settings.gschema.override uses invalid key "enable-interactive-search"
Public bug reported: Here is the problem: Processing triggers for libglib2.0-0:amd64 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. It can be reproduced by (re)installing any package that triggers the libglib2.0-0 triggers: # apt install --reinstall eog Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 628 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ wily/main eog amd64 3.16.3-1ubuntu2 [628 kB] Fetched 628 kB in 0s (787 kB/s) (Reading database ... 631380 files and directories currently installed.) Preparing to unpack .../eog_3.16.3-1ubuntu2_amd64.deb ... Unpacking eog (3.16.3-1ubuntu2) over (3.16.3-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for menu (2.1.47ubuntu1) ... Processing triggers for gconf2 (3.2.6-3ubuntu3) ... Processing triggers for man-db (2.7.3-1) ... Processing triggers for libglib2.0-0:i386 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. Processing triggers for libglib2.0-0:amd64 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. Processing triggers for gnome-menus (3.13.3-6ubuntu1) ... Processing triggers for bamfdaemon (0.5.2~bzr0+15.10.20150627.1-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu3) ... Processing triggers for mime-support (3.58ubuntu1) ... Setting up eog (3.16.3-1ubuntu2) ... Processing triggers for menu (2.1.47ubuntu1) ... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.4 Uname: Linux 4.2.2-040202-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 2 16:38:32 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1502183 Title: 10_ubuntu-settings.gschema.override uses invalid key "enable- interactive-search" Status in ubuntu-settings package in Ubuntu: New Bug description: Here is the problem: Processing triggers for libglib2.0-0:amd64 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. It can be reproduced by (re)installing any package that triggers the libglib2.0-0 triggers: # apt install --reinstall eog Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 628 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ wily/main eog amd64 3.16.3-1ubuntu2 [628 kB] Fetched 628 kB in 0s (787 kB/s) (Reading database ... 631380 files and directories currently installed.) Preparing to unpack .../eog_3.16.3-1ubuntu2_amd64.deb ... Unpacking eog (3.16.3-1ubuntu2) over (3.16.3-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for menu (2.1.47ubuntu1) ... Processing triggers for gconf2 (3.2.6-3ubuntu3) ... Processing triggers for man-db (2.7.3-1) ... Processing triggers for libglib2.0-0:i386 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. Processing triggers for libglib2.0-0:amd64 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. Processing triggers for gnome-menus (3.13.3-6ubuntu1) ... Processing triggers for bamfdaemon (0.5.2~bzr0+15.10.20150627.1-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for de
[Touch-packages] [Bug 1502183] Re: 10_ubuntu-settings.gschema.override uses invalid key "enable-interactive-search"
Here it is: $ dpkg -l | grep nautilus ii gnome-sushi 3.18.0-1~wily1 amd64sushi is a quick previewer for nautilus ii libnautilus-extension1a 1:3.18.0-0ubuntu1~wily1 amd64libraries for nautilus components - runtime version ii nautilus 1:3.18.0-0ubuntu1~wily1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:3.18.0-0ubuntu1~wily1 all data files for nautilus ii nautilus-sendto 3.8.2-1ubuntu1 amd64integrates Evolution and Pidgin into the Nautilus file manager ii nautilus-share 0.7.3-1ubuntu5 amd64Nautilus extension to share folder using Samba ii seahorse-nautilus 3.11.92-1 amd64Nautilus extension for Seahorse integration My nautilus comes from the gnome3-staging PPA: $ apt-cache showpkg nautilus Package: nautilus Versions: 1:3.18.0-0ubuntu1~wily1 (/var/lib/apt/lists/ppa.launchpad.net_gnome3-team_gnome3-staging_ubuntu_dists_wily_main_binary-amd64_Packages) (/var/lib/dpkg/status) ** Changed in: ubuntu-settings (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1502183 Title: 10_ubuntu-settings.gschema.override uses invalid key "enable- interactive-search" Status in ubuntu-settings package in Ubuntu: New Bug description: Here is the problem: Processing triggers for libglib2.0-0:amd64 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. It can be reproduced by (re)installing any package that triggers the libglib2.0-0 triggers: # apt install --reinstall eog Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 628 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ wily/main eog amd64 3.16.3-1ubuntu2 [628 kB] Fetched 628 kB in 0s (787 kB/s) (Reading database ... 631380 files and directories currently installed.) Preparing to unpack .../eog_3.16.3-1ubuntu2_amd64.deb ... Unpacking eog (3.16.3-1ubuntu2) over (3.16.3-1ubuntu2) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for menu (2.1.47ubuntu1) ... Processing triggers for gconf2 (3.2.6-3ubuntu3) ... Processing triggers for man-db (2.7.3-1) ... Processing triggers for libglib2.0-0:i386 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. Processing triggers for libglib2.0-0:amd64 (2.46.0-2) ... No such key 'enable-interactive-search' in schema 'org.gnome.nautilus.preferences' as specified in override file '/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring override for this key. Processing triggers for gnome-menus (3.13.3-6ubuntu1) ... Processing triggers for bamfdaemon (0.5.2~bzr0+15.10.20150627.1-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu3) ... Processing triggers for mime-support (3.58ubuntu1) ... Setting up eog (3.16.3-1ubuntu2) ... Processing triggers for menu (2.1.47ubuntu1) ... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-settings 15.10.4 Uname: Linux 4.2.2-040202-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 2 16:38:32 2015 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1502183/+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 1048430] Re: "dnsmasq not available on the bus"
This bug still exists in wily: $ journalctl | grep dnsmasq oct. 02 11:05:10 vougeot NetworkManager[1432]: DNS: loaded plugin dnsmasq oct. 02 11:05:10 vougeot dnsmasq[1621]: started, version 2.75 cachesize 150 oct. 02 11:05:10 vougeot dnsmasq[1621]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify oct. 02 11:05:10 vougeot dnsmasq-dhcp[1621]: DHCP, IP range 10.0.3.2 -- 10.0.3.254, lease time 1h oct. 02 11:05:10 vougeot dnsmasq-dhcp[1621]: DHCP, sockets bound exclusively to interface lxcbr0 oct. 02 11:05:10 vougeot dnsmasq[1621]: no servers found in /etc/resolv.conf, will retry oct. 02 11:05:10 vougeot dnsmasq[1621]: read /etc/hosts - 16 addresses oct. 02 11:05:14 vougeot NetworkManager[1432]: DNS: starting dnsmasq... oct. 02 11:05:14 vougeot NetworkManager[1432]: dnsmasq not available on the bus, can't update servers. oct. 02 11:05:14 vougeot NetworkManager[1432]: [1443776714.530733] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name oct. 02 11:05:14 vougeot NetworkManager[1432]: DNS: plugin dnsmasq update failed [many more error messages] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: "dnsmasq not available on the bus" Status in network-manager package in Ubuntu: Confirmed Bug description: Dnsmasq seems to be having some issues. This occurs whenever I try to connect to my wireless network; sometimes it only happens once, but sometimes the error loops for a while. Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: starting dnsmasq... Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899067] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers. Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899142] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: plugin dnsmasq update failed Sep 9 17:43:51 bkerensa NetworkManager[935]: ((null)): writing resolv.conf to /sbin/resolvconf ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 17:47:22 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+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 1447142] Re: systemd: ntpdate is started too soon (before the network)
> Can you explain why this is actually a problem please? I guess that Ubuntu systems with ntp installed would boot a little faster if ntp was not doing useless work by getting started before the network is fully up. > Won't timesyncd suffice on a desktop that uses NetworkManager now? Perhaps, but timesyncd is not activated by default. I had to type this command to activate it: # timedatectl set-ntp true While timesyncd is probably a fine alternative to ntp, this is a bug in ntp and Ubuntu would be a better system with this bug fixed (or ntp removed and timesyncd activated by default). > Is the time on your system actually falling out of sync, or is the problem > just the noise of the error message? Time is fine on my system, but the noise of the error messages is a problem in itself. ** Changed in: ntp (Ubuntu) Status: Incomplete => New -- 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/1447142 Title: systemd: ntpdate is started too soon (before the network) Status in ntp package in Ubuntu: New Bug description: Here is what I see in journalctl: ntpdate cannot do DNS resolution because NetworkManager has not finished configuring the network interface. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: init! Apr 21 22:01:13 xeelee NetworkManager[1493]: update_system_hostname Apr 21 22:01:13 xeelee NetworkManager[1493]:interface-parser: parsing file /etc/network/interfaces Apr 21 22:01:13 xeelee NetworkManager[1493]:interface-parser: finished parsing file /etc/network/interfaces Apr 21 22:01:13 xeelee NetworkManager[1493]: management mode: unmanaged Apr 21 22:01:13 xeelee NetworkManager[1493]: devices added (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlan0, Apr 21 22:01:13 xeelee NetworkManager[1493]: device added (path: /sys/devices/pci:00/:00:1c.2/:03:00.0/net/wlan0, Apr 21 22:01:13 xeelee NetworkManager[1493]: devices added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, Apr 21 22:01:13 xeelee NetworkManager[1493]: device added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, i Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: devices added (path: /sys/devices/virtual/net/lo, iface: lo) Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], no ATA CHECK POWER STATUS support, ignoring -n Directive Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configur Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], is SMART capable. Adding to "monitor" list. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: end _init. Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdc [USB JMicron], state read from /var/lib/smartmontools/smartd.WDC_WD40EZRX_00SPE Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host ntp.ubuntu.com: Name or service not known (-2) Apr 21 22:01:13 xeelee NetworkManager[1493]: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the Ne Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], opened Apr 21 22:01:13 xeelee ntpdate[1563]: no servers can be used, exiting Apr 21 22:01:13 xeelee NetworkManager[1493]: Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use t Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], WDC WD40EZRX-00SPEB0, S/N:WD-WCC4E0267943, WWN:5-0014ee-25e7069b Apr 21 22:01:13 xeelee NetworkManager[1493]: SCPlugin-Ofono: Acquired D-Bus service com.canonical.NMOfono Apr 21 22:01:13 xeelee NetworkManager[1493]: SCPlugin-Ofono: init! Apr 21 22:01:13 xeelee NetworkManager[1493]: SCPlugin-Ofono: end _init. Apr 21 22:01:13 xeelee NetworkManager[1493]: Loaded plugin ofono: (C) 2013 Canonical Ltd. To report bugs please use the Netwo Apr 21 22:01:13 xeelee NetworkManager[1493]: (25444896) ... get_connections. Apr 21 22:01:13 xeelee NetworkManager[1493]: (25444896) ... get_connections (managed=false): return empty list. Apr 21 22:01:13 xeelee NetworkManager[1493]: SCPlugin-Ofono: (25249376) ... get_connections. Apr 21 22:01:13 xeelee NetworkManager[1493]: SCPlugin-Ofono: (25249376) connections count: 0 Apr 21 22:01:13 xeelee NetworkManager[1493]: get unmanaged devices count: 0 Apr 21 22:01:13 xeelee smartd[1495]: Device: /dev/sdd [USB JMicron], found in smartd datab
[Touch-packages] [Bug 74139] Re: shutdown missing -F (force fsck) option
> fsck in particularly is slowly undergoing big changes that will mean you can do it on the fly, with no need to reboot, etc. 6 years later ext4 still does not support online fsck. > so why support -F ? Because with systemd it is even more cumbersome to force a fsck of the root FS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/74139 Title: shutdown missing -F (force fsck) option Status in Upstart: Won't Fix Status in upstart package in Ubuntu: Invalid Bug description: Binary package hint: upstart Hello, The -F option of the /sbin/shutdown command is useful: it allows you to force the operating system to check all partitions (fsck) at the next reboot. In Ubuntu 6.10, this option has disappeared ! The command "shutdown -rF now" reboots the system, but does not force the checking of the filesystems. Also, the -F option is no longer in the shutdown manpage. It appears the -F option was still there in Ubuntu 6.06. As an aside, since Ubuntu is supposed to be based on Debian GNU/Linux, shutdown does have the -F flag in both Debian 3.1 (sarge) and Debian 4.0 (etch). So, where did -F go ? Package information from apt: Package: upstart Section: base Installed-Size: 300 Maintainer: Scott James Remnant Architecture: i386 Version: 0.2.7-7 Replaces: sysvinit To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/74139/+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 1447154] Re: systemd tries to start pulseaudio several times
On sam., 2015-06-20 at 16:08 +, Raymond wrote: > it is strange yhat your hdmi SONY TV XV is available, line out and > headphone are unplugged but iec958 spdif is your default sink It is a config I made and that allows me to listen to music even when the TV is switched off. -- Laurent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1447154 Title: systemd tries to start pulseaudio several times Status in pulseaudio package in Ubuntu: Confirmed Bug description: Here is what I see in journalctl: # journalctl | grep pulseaudio Apr 21 22:01:16 xeelee pulseaudio[2330]: [pulseaudio] pid.c: Daemon already running. Apr 21 22:01:33 xeelee pulseaudio[2911]: [pulseaudio] pid.c: Daemon already running. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 2895 F pulseaudio CurrentDesktop: KDE Date: Wed Apr 22 14:46:51 2015 SourcePackage: pulseaudio UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1447154/+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 1723244] [NEW] Invalid desktop file: 'file:///usr/share/ubuntu/applications/display-im6*.desktop'
Public bug reported: Hi, in the logs tracker complains that some desktop files are invalid: $ journalctl -b | grep tracker [...] oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Invalid desktop file: 'file:///usr/share/ubuntu/applications/display-im6.q16hdri.desktop' oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Couldn't get name, missing key (Name) oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Invalid desktop file: 'file:///usr/share/ubuntu/applications/display-im6.q16.desktop' oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Couldn't get name, missing key (Name) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.18 Uname: Linux 4.13.6-041306-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Thu Oct 12 21:57:55 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to artful on 2017-09-29 (13 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1723244 Title: Invalid desktop file: 'file:///usr/share/ubuntu/applications/display- im6*.desktop' Status in ubuntu-settings package in Ubuntu: New Bug description: Hi, in the logs tracker complains that some desktop files are invalid: $ journalctl -b | grep tracker [...] oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Invalid desktop file: 'file:///usr/share/ubuntu/applications/display-im6.q16hdri.desktop' oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Couldn't get name, missing key (Name) oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Invalid desktop file: 'file:///usr/share/ubuntu/applications/display-im6.q16.desktop' oct. 12 20:05:15 vougeot tracker-miner-a[5902]: Couldn't get name, missing key (Name) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.18 Uname: Linux 4.13.6-041306-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Thu Oct 12 21:57:55 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to artful on 2017-09-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1723244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681249] Re: tracker-extract crashed with signal 31 in chdir()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1681249 Title: tracker-extract crashed with signal 31 in chdir() Status in tracker package in Ubuntu: New Bug description: tracker crash while indexing my homedir ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: tracker-extract 1.12.0-0ubuntu1 Uname: Linux 4.10.8-041008-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 8 14:00:45 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/tracker/tracker-extract ExecutableTimestamp: 1490023113 JournalErrors: No journal files were found. -- No entries -- ProcCmdline: /usr/lib/tracker/tracker-extract ProcCwd: /home/bonnaudl Signal: 31 SourcePackage: tracker Title: tracker-extract crashed with signal 31 in chdir() UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1681249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
** Tags added: yakkety zesty -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
On my Dell Latitude E6520 with Ubuntu 16.10, after applying the "KEYBOARD_KEY_150=f20" -> "KEYBOARD_KEY_100150=f20" patch, I get this error: janv. 10 14:13:24 vougeot systemd-udevd[954]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x100150, key code 190): Invalid argument -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+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 1502173] Re: Python warnings: modules imported without specifying a version first
Thanks for the fix!
I upgraded my system to yakkety therefore I cannot test myself.
--
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/1502173
Title:
Python warnings: modules imported without specifying a version first
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
Fix Committed
Bug description:
[Description]
Users receive warnings about importing of python modules without a version
being specified. While this isn't a big deal in itself we get lots of bug
reports from people about this issue since it is so obvious. Given that Ubuntu
16.04 is an LTS release we should fix this and prevent further reporting of the
issue.
[Test Case]
1) run /usr/share/apport/apport-gtk in a terminal
2) Observe the following
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
with the version of apport in -proposed you'll no longer receive the
warning.
[Regression Potential]As with any SRU this could cause a regression in
the software if the fix is typo'ed so review it carefully. If there
isn't a typo and then the chance of a regression is very very very
low.
Original Description
Hi,
here is the problem:
$ /usr/share/apport/apport-gtk
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
ProblemType: BugDistroRelease: Ubuntu 15.10
Package: apport-gtk 2.19-0ubuntu1
Uname: Linux 4.2.2-040202-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 2 16:17:14 2015
EcryptfsInUse: Yes
PackageArchitecture: allSourcePackage: apport
UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
I tested with a 4.9.2 mainline kernel. I will try to test with an Ubuntu kernel when I have a chance to reboot my system... -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
This bug has finally improved in Ubuntu 17.04. There are only 2 errors left: # update-mime-database /usr/share/mime Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' However it is not clear to me which file is responsible for this: # grep -r all/allfiles /usr/share/mime /usr/share/mime/all/allfiles.xml:http://www.freedesktop.org/standards/shared-mime-info"; type="all/allfiles"> /usr/share/mime/packages/kde.xml: /usr/share/mime/types:all/allfiles ** Tags removed: i386 ** Tags added: xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in shared-mime-info: Confirmed Status in kde4libs package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Triaged Status in kde4libs package in Debian: New Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/289592/+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 1447154] Re: systemd tries to start pulseaudio several times
This problem is not longer present in zesty. Thanks! ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1447154 Title: systemd tries to start pulseaudio several times Status in pulseaudio package in Ubuntu: Fix Released Bug description: Here is what I see in journalctl: # journalctl | grep pulseaudio Apr 21 22:01:16 xeelee pulseaudio[2330]: [pulseaudio] pid.c: Daemon already running. Apr 21 22:01:33 xeelee pulseaudio[2911]: [pulseaudio] pid.c: Daemon already running. Sound is working, though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 2895 F pulseaudio CurrentDesktop: KDE Date: Wed Apr 22 14:46:51 2015 SourcePackage: pulseaudio UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1447154/+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 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted
This bug still exists in zesty: # journalctl -b | grep bluetoothd Mar 20 11:29:29 xeelee bluetoothd[1113]: Bluetooth daemon 5.43 Mar 20 11:29:29 xeelee bluetoothd[1113]: Starting SDP server Mar 20 11:29:29 xeelee bluetoothd[1113]: Bluetooth management interface 1.14 initialized Mar 20 11:29:29 xeelee bluetoothd[1113]: Failed to obtain handles for "Service Changed" characteristic Mar 20 11:29:29 xeelee bluetoothd[1113]: Sap driver initialization failed. Mar 20 11:29:29 xeelee bluetoothd[1113]: sap-server: Operation not permitted (1) [...] ** Tags added: zesty -- 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/1629632 Title: Sap driver initialization failed, sap-server: Operation not permitted Status in bluez package in Ubuntu: Confirmed Status in bluez package in Debian: New Bug description: Hi, here are are messages from the bluetooth daemon: $ journalctl -b | grep bluetoothd Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41 Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 initialized Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for "Service Changed" characteristic Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed. Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted (1) There are at least 2 errors concerning: - handles - Sap driver/server ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 09:59:43 2016 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:57:27:6F ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:1974 acl:0 sco:0 events:132 errors:0 TX bytes:6033 acl:0 sco:0 commands:132 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+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 1658921] Re: NetworkManager does not manage wired connection
** Tags added: yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1658921 Title: NetworkManager does not manage wired connection Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager does not manage my wired eth0 connection, no matter how I set /etc/network/interfaces or /etc/NetworkManager/NetworkManager.conf Using ubuntu 16.04, /etc/network/interfaces only managed lo, and [ifupdown] section of NetworkManager.conf had set managed=false. With these same settings, after upgrading to ubuntu 16.10, eth0 appears as unmanaged in nm-applet. If I modify /etc/network/interfaces and add auto eth0 iface eth0 inet dhcp And set managed=true in NetworkManager.conf [ifupdown] section, eth0 is still unmanaged despite it does get an IP from DHCP server. This is happening in my five computers (two laptops and three desktops). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 1675892] [NEW] pulseaudio crashed with SIGABRT
Public bug reported: A random pulseaudio crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 Uname: Linux 4.10.4-041004-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 1902 F pulseaudio CurrentDesktop: MATE Date: Thu Mar 23 07:51:00 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio Stacktrace: #0 No locals. #1 0x in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x0 StacktraceTop: ?? () Title: pulseaudio crashed with SIGABRT UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago) UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace zesty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1675892 Title: pulseaudio crashed with SIGABRT Status in pulseaudio package in Ubuntu: New Bug description: A random pulseaudio crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 Uname: Linux 4.10.4-041004-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 1902 F pulseaudio CurrentDesktop: MATE Date: Thu Mar 23 07:51:00 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio Stacktrace: #0 No locals. #1 0x in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x0 StacktraceTop: ?? () Title: pulseaudio crashed with SIGABRT UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago) UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1675892/+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 1629632] Re: Sap driver initialization failed, sap-server: Operation not permitted
According to this: https://raspberrypi.stackexchange.com/questions/40839/sap-error-on- bluetooth-service-status the error messages about SAP can be avoided by starting bluetoothd with the "--noplugin=sap" option. Since SAP is probably of little use in Ubuntu and since it does not work anyway, how about disabling it by default? ** Bug watch added: Debian Bug tracker #803265 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803265 ** Also affects: bluez (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803265 Importance: Unknown Status: Unknown -- 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/1629632 Title: Sap driver initialization failed, sap-server: Operation not permitted Status in bluez package in Ubuntu: Confirmed Status in bluez package in Debian: Unknown Bug description: Hi, here are are messages from the bluetooth daemon: $ journalctl -b | grep bluetoothd Oct 01 17:24:35 xeelee bluetoothd[1104]: Bluetooth daemon 5.41 Oct 01 17:24:35 xeelee bluetoothd[1104]: Starting SDP server Oct 01 17:24:36 xeelee bluetoothd[1104]: Bluetooth management interface 1.13 initialized Oct 01 17:24:36 xeelee bluetoothd[1104]: Failed to obtain handles for "Service Changed" characteristic Oct 01 17:24:36 xeelee bluetoothd[1104]: Sap driver initialization failed. Oct 01 17:24:36 xeelee bluetoothd[1104]: sap-server: Operation not permitted (1) There are at least 2 errors concerning: - handles - Sap driver/server ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bluez 5.41-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 09:59:43 2016 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-19-lowlatency root=UUID=347d095b-3b19-412b-841e-acfd162e2c53 ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to yakkety on 2016-03-31 (184 days ago) dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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. hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:85:DE:57:27:6F ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:1974 acl:0 sco:0 events:132 errors:0 TX bytes:6033 acl:0 sco:0 commands:132 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632/+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 1668641] [NEW] Error message: pam_systemd(su:session): Cannot create session: Already running in a session
Public bug reported: Hi, here is how to reproduce this error: 1. log in to the root account with ssh 2. run "su - some_user_account" Here is what I see in the logs: Feb 28 15:21:45 xeelee su[9843]: Successful su for bonnaudl by root Feb 28 15:21:45 xeelee su[9843]: + /dev/pts/10 root:bonnaudl Feb 28 15:21:45 xeelee su[9843]: pam_unix(su:session): session opened for user bonnaudl by root(uid=0) Feb 28 15:21:45 xeelee su[9843]: pam_systemd(su:session): Cannot create session: Already running in a session Feb 28 15:21:48 xeelee su[9843]: pam_unix(su:session): session closed for user bonnaudl In another usage scenario of "su -" there is no error message and the creation of a new session: févr. 28 15:08:15 vougeot su[18962]: Successful su for bonnaudl by root févr. 28 15:08:15 vougeot su[18962]: + /dev/pts/0 root:bonnaudl févr. 28 15:08:15 vougeot su[18962]: pam_unix(su:session): session opened for user bonnaudl by bonnaudl(uid=0) févr. 28 15:08:15 vougeot systemd-logind[1162]: New session c9 of user bonnaudl. févr. 28 15:08:15 vougeot systemd[1]: Started Session c9 of user bonnaudl. févr. 28 15:08:17 vougeot su[18962]: pam_unix(su:session): session closed for user bonnaudl févr. 28 15:08:17 vougeot systemd-logind[1162]: Removed session c9. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-systemd 231-9ubuntu3 Uname: Linux 4.10.1-041001-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 28 15:21:09 2017 EcryptfsInUse: Yes SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug yakkety ** Bug watch added: Debian Bug tracker #825949 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825949 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825949 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668641 Title: Error message: pam_systemd(su:session): Cannot create session: Already running in a session Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: Hi, here is how to reproduce this error: 1. log in to the root account with ssh 2. run "su - some_user_account" Here is what I see in the logs: Feb 28 15:21:45 xeelee su[9843]: Successful su for bonnaudl by root Feb 28 15:21:45 xeelee su[9843]: + /dev/pts/10 root:bonnaudl Feb 28 15:21:45 xeelee su[9843]: pam_unix(su:session): session opened for user bonnaudl by root(uid=0) Feb 28 15:21:45 xeelee su[9843]: pam_systemd(su:session): Cannot create session: Already running in a session Feb 28 15:21:48 xeelee su[9843]: pam_unix(su:session): session closed for user bonnaudl In another usage scenario of "su -" there is no error message and the creation of a new session: févr. 28 15:08:15 vougeot su[18962]: Successful su for bonnaudl by root févr. 28 15:08:15 vougeot su[18962]: + /dev/pts/0 root:bonnaudl févr. 28 15:08:15 vougeot su[18962]: pam_unix(su:session): session opened for user bonnaudl by bonnaudl(uid=0) févr. 28 15:08:15 vougeot systemd-logind[1162]: New session c9 of user bonnaudl. févr. 28 15:08:15 vougeot systemd[1]: Started Session c9 of user bonnaudl. févr. 28 15:08:17 vougeot su[18962]: pam_unix(su:session): session closed for user bonnaudl févr. 28 15:08:17 vougeot systemd-logind[1162]: Removed session c9. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-systemd 231-9ubuntu3 Uname: Linux 4.10.1-041001-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 28 15:21:09 2017 EcryptfsInUse: Yes SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668641/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
I am still seeing this error with the 4.10.1-041001-generic mainline kernel. -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start
On Ubuntu 16.10 with this bluez package:
Package: bluez
Version: 5.41-0ubuntu3with
I no longer see the "Not enough handles to register service" messages.
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349
Title:
15:10 and 16.04: bluetoothd reports "Not enough handles to register
service" at start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1048430] Re: "dnsmasq not available on the bus"
This bug no longer exists in yakkety: # journalctl -b |grep dnsmasq Feb 26 20:12:47 xeelee audit[1052]: AVC apparmor="STATUS" operation="profile_load" name="/usr/sbin/dnsmasq" pid=1052 comm="apparmor_parser" Feb 26 20:12:47 xeelee audit[1052]: AVC apparmor="STATUS" operation="profile_load" name="/usr/sbin/dnsmasq//libvirt_leaseshelper" pid=1052 comm="apparmor_parser" Feb 26 20:12:47 xeelee NetworkManager[1088]: [1488136367.5567] dns-mgr[0x55d53a357a80]: init: dns=dnsmasq, rc-manager=resolvconf, plugin=dnsmasq Feb 26 20:12:50 xeelee NetworkManager[1088]: [1488136370.2108] dns-plugin[0x55d53a37b500]: starting dnsmasq... Feb 26 20:12:50 xeelee dnsmasq[1397]: started, version 2.76 cachesize 1000 Feb 26 20:12:50 xeelee dnsmasq[1397]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify Feb 26 20:12:50 xeelee dnsmasq[1397]: DBus support enabled: connected to system bus Feb 26 20:12:50 xeelee dnsmasq[1397]: using nameserver 8.8.4.4#53 Feb 26 20:12:50 xeelee dnsmasq[1397]: using nameserver 8.8.8.8#53 Feb 26 20:12:50 xeelee dnsmasq[1397]: cleared cache Feb 26 20:12:50 xeelee NetworkManager[1088]: [1488136370.2832] dnsmasq[0x55d53a37b500]: dnsmasq appeared as :1.13 Feb 26 20:12:50 xeelee dnsmasq[1397]: setting upstream servers from DBus [...] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: "dnsmasq not available on the bus" Status in network-manager package in Ubuntu: Confirmed Bug description: Dnsmasq seems to be having some issues. This occurs whenever I try to connect to my wireless network; sometimes it only happens once, but sometimes the error loops for a while. Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: starting dnsmasq... Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899067] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers. Sep 9 17:43:51 bkerensa NetworkManager[935]: [1347237831.899142] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Sep 9 17:43:51 bkerensa NetworkManager[935]: DNS: plugin dnsmasq update failed Sep 9 17:43:51 bkerensa NetworkManager[935]: ((null)): writing resolv.conf to /sbin/resolvconf ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dnsmasq (not installed) ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 17:47:22 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+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 1675892] Re: pulseaudio crashed with SIGABRT
I tried to reproduce the crash with a terminal bell and failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1675892 Title: pulseaudio crashed with SIGABRT Status in pulseaudio package in Ubuntu: Confirmed Bug description: A random pulseaudio crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 Uname: Linux 4.10.4-041004-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 1902 F pulseaudio CurrentDesktop: MATE Date: Thu Mar 23 07:51:00 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio Stacktrace: #0 No locals. #1 0x in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x0 StacktraceTop: ?? () Title: pulseaudio crashed with SIGABRT UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago) UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT 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.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT: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/pulseaudio/+bug/1675892/+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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml
I cannot reproduce the bug in Ubuntu 19.04. Thanks for the fix! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/289592 Title: Unknown media types in /usr/share/mime/packages/kde.xml Status in kdelibs: Won't Fix Status in shared-mime-info: Won't Fix Status in kde4libs package in Ubuntu: Confirmed Status in shared-mime-info package in Ubuntu: Triaged Status in shared-mime-info package in Debian: Confirmed Bug description: Here is the problem: # update-mime-database /usr/share/mime [...] Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' It seems to come from this file: /usr/share/mime/packages/kde.xml To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/289592/+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 1761858] Re: libx11-6-dbgsym should be in section "debug" instead of section "libs"
The bug is fixed in disco. The package now belongs to section debug: Package: libx11-6-dbgsym Section: debug Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1761858 Title: libx11-6-dbgsym should be in section "debug" instead of section "libs" Status in libx11 package in Ubuntu: New Bug description: Hi, the problem is that deborphan lists this package as removable, whereas I want to keep it: $ deborphan [...] libx11-6-dbgsym:amd64 It comes from the fact that libx11-6-dbgsym is in section "libs": $ dpkg -s libx11-6-dbgsym [...] Section: libs whereas it should be in section "devel". All other *-dbgsym packages on my system belong to this section. For instance: $ dpkg -s libqt5gui5-dbgsym [...] Section: debug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6-dbgsym 2:1.6.4-3 Uname: Linux 4.15.15-041515-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Apr 6 22:00:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1761858/+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 1761858] Re: libx11-6-dbgsym should be in section "debug" instead of section "libs"
The bug is fixed in disco. The package now belongs to section debug: Package: libx11-6-dbgsym Section: debug Thanks! ** Changed in: libx11 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1761858 Title: libx11-6-dbgsym should be in section "debug" instead of section "libs" Status in libx11 package in Ubuntu: Fix Released Bug description: Hi, the problem is that deborphan lists this package as removable, whereas I want to keep it: $ deborphan [...] libx11-6-dbgsym:amd64 It comes from the fact that libx11-6-dbgsym is in section "libs": $ dpkg -s libx11-6-dbgsym [...] Section: libs whereas it should be in section "devel". All other *-dbgsym packages on my system belong to this section. For instance: $ dpkg -s libqt5gui5-dbgsym [...] Section: debug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libx11-6-dbgsym 2:1.6.4-3 Uname: Linux 4.15.15-041515-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Apr 6 22:00:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.15-041515-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro vsyscall=none security=apparmor intel_iommu=on enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=1 SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1761858/+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 1668641] Re: Error message: pam_systemd(su:session): Cannot create session: Already running in a session
This bug no longer exists in Ubuntu 19.04/disco. Here is the log I get when I do ssh then "su -": Apr 10 14:08:42 xeelee systemd[1]: Started User Manager for UID 0. Apr 10 14:08:42 xeelee systemd[1]: Started Session 447 of user root. Apr 10 14:08:42 xeelee systemd[28391]: Reached target Default. Apr 10 14:08:42 xeelee systemd[28391]: Startup finished in 75ms. Apr 10 14:08:47 xeelee su[28502]: (to bonnaudl) root on pts/30 Apr 10 14:08:47 xeelee su[28502]: pam_unix(su-l:session): session opened for user bonnaudl by root(uid=0) Apr 10 14:09:08 xeelee su[28502]: pam_unix(su-l:session): session closed for user bonnaudl I still get this error: $ systemctl --user status Failed to connect to bus: No such file or directory but this is for another bug report... ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- 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/1668641 Title: Error message: pam_systemd(su:session): Cannot create session: Already running in a session Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Bug description: Hi, here is how to reproduce this error: 1. log in to the root account with ssh 2. run "su - some_user_account" Here is what I see in the logs: Feb 28 15:21:45 xeelee su[9843]: Successful su for bonnaudl by root Feb 28 15:21:45 xeelee su[9843]: + /dev/pts/10 root:bonnaudl Feb 28 15:21:45 xeelee su[9843]: pam_unix(su:session): session opened for user bonnaudl by root(uid=0) Feb 28 15:21:45 xeelee su[9843]: pam_systemd(su:session): Cannot create session: Already running in a session Feb 28 15:21:48 xeelee su[9843]: pam_unix(su:session): session closed for user bonnaudl In another usage scenario of "su -" there is no error message and the creation of a new session: févr. 28 15:08:15 vougeot su[18962]: Successful su for bonnaudl by root févr. 28 15:08:15 vougeot su[18962]: + /dev/pts/0 root:bonnaudl févr. 28 15:08:15 vougeot su[18962]: pam_unix(su:session): session opened for user bonnaudl by bonnaudl(uid=0) févr. 28 15:08:15 vougeot systemd-logind[1162]: New session c9 of user bonnaudl. févr. 28 15:08:15 vougeot systemd[1]: Started Session c9 of user bonnaudl. févr. 28 15:08:17 vougeot su[18962]: pam_unix(su:session): session closed for user bonnaudl févr. 28 15:08:17 vougeot systemd-logind[1162]: Removed session c9. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-systemd 231-9ubuntu3 Uname: Linux 4.10.1-041001-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 28 15:21:09 2017 EcryptfsInUse: Yes SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668641/+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 1761712] Re: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()
** Changed in: gconf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1761712 Title: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value() Status in gconf package in Ubuntu: Fix Released Bug description: This is caused by a missing setting in org.gnome.desktop.wm.preferences. This can be seen thanks to this error message that appears in the backtrace: Settings schema 'org.gnome.desktop.wm.preferences' does not contain a key named 'application-based'" ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gconf2 3.2.6-4ubuntu1 Uname: Linux 4.15.15-041515-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 6 10:48:45 2018 ExecutablePath: /usr/bin/gsettings-data-convert ExecutableTimestamp: 1496904803 ProcCmdline: gsettings-data-convert ProcCwd: /home/bonnaudl Signal: 5 SourcePackage: gconf StacktraceTop: g_settings_schema_get_value (schema=0x562a8ac5da30, key=0x562a8ac6b810 "application-based") at ../../../../gio/gsettingsschema.c:970 g_settings_schema_key_init (key=key@entry=0x7ffcbae8c490, schema=0x562a8ac5da30, name=name@entry=0x562a8ac6b810 "application-based") at ../../../../gio/gsettingsschema.c:1249 g_settings_set_value (settings=settings@entry=0x562a8ac5dc30 [GSettings], key=key@entry=0x562a8ac6b810 "application-based", value=0x562a8ac6f320) at ../../../../gio/gsettings.c:1563 g_settings_set (settings=0x562a8ac5dc30 [GSettings], key=0x562a8ac6b810 "application-based", format=) at ../../../../gio/gsettings.c:1670 handle_file (filename=) at gsettings-data-convert.c:295 Title: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value() UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1761712/+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 1447148] Re: broken apport hook
This bug no longer exists. ** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1447148 Title: broken apport hook Status in network-manager package in Ubuntu: Fix Released Bug description: Reporting a bug in network-manager with ubuntu-bug, leads to this error: nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. (as can be seen at the end of this bug report :>) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 Uname: Linux 4.0.0-04-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 22 14:31:54 2015 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 802-3-ethernet 1429705873 Wed 22 Apr 2015 02:31:13 PM CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 dbecefc9-ce36-429a-952e-5df76b594328 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1447148/+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 1568143] Re: apport-kde crashed with SIGSEGV
** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1568143/+attachment/4629626/+files/JournalErrors.txt -- 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/1568143 Title: apport-kde crashed with SIGSEGV Status in apport package in Ubuntu: Confirmed Bug description: Random crash ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-kde 2.20.1-0ubuntu1 Uname: Linux 4.5.0-040500-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:136:9666180:2016-04-08 20:43:09.867370128 +0200:2016-04-08 20:43:10.867370128 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash CurrentDesktop: KDE Date: Fri Apr 8 20:43:03 2016 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde systemd ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f666ccc6105:mov(%rax),%rax PC (0x7f666ccc6105) ok source "(%rax)" (0x7575757575757575) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-35m-x86_64-linux-gnu.so QObject::~QObject() (this=, __in_chrg=) at kernel/qobject.cpp:987 (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() (this=0x7f66691ccb40 <(anonymous namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, __in_chrg=) at accessible/qaccessiblecache_p.h:60 (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() (this=0x7f66691ccb40 <(anonymous namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, __in_chrg=) at accessible/qaccessiblecache.cpp:46 __run_exit_handlers (status=1, listp=0x7f6670b925f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 Title: apport-kde crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2016-03-31 (8 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare staff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1568143/+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 1826639] [NEW] wpasupplicant: unknown keys in no-mac-addr-change.conf
Public bug reported: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: New Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
I installed this package: Package: wpasupplicant Version: 2:2.9-1ubuntu4.1 from focal-proposed and now this command: journalctl | grep cloned-mac-address gives no output. Therefore, the error message is gone. And of course Wi-Fi still works on my WPA2-protected home network. Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa ships an invalid network-manager configuration that triggers warnings * Test case $ journalctl | grep no-mac-addr-change should not have errors listed * Regression potential the change removes configurations which are not needed (since they set the value to the same one as the default) and in the wrong section, it shouldn't have any visible impact Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1899749] [NEW] Please add DCCP to rarely used protocols
Public bug reported: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal groovy ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1899749 Title: Please add DCCP to rarely used protocols Status in kmod package in Ubuntu: New Bug description: Hi, according to this message: https://www.openwall.com/lists/oss-security/2020/10/13/7 the DCCP protocol may be used as an attack vector to the kernel. So could you please add it to /etc/modprobe.d/blacklist-rare- network.conf ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kmod 27-1ubuntu2 Uname: Linux 5.8.14-050814-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 14 10:21:37 2020 SourcePackage: kmod UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.blacklist-rare-network.conf: 2020-10-14T10:21:22.472169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1899749/+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 1870427] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
Here it is on my system: $ update-alternatives --display pager pager - auto mode link best version is /usr/bin/less link currently points to /usr/bin/less link pager is /usr/bin/pager slave pager.1.gz is /usr/share/man/man1/pager.1.gz /bin/more - priority 50 slave pager.1.gz: /usr/share/man/man1/more.1.gz /usr/bin/less - priority 77 slave pager.1.gz: /usr/share/man/man1/less.1.gz /usr/bin/w3m - priority 25 slave pager.1.gz: /usr/share/man/man1/w3m.1.gz However this output is for my system in its current state, that has been fixed by finishing the eoan -> focal upgrade. The alternative was probably transiently broken during the upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1870427 Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Incomplete Status in less package in Ubuntu: New Bug description: During an upgrade from eoan to focal I got the following error: package:smartmontools:7.1-1build1 Installing new version of config file /etc/init.d/smartmontools ... Configuration file '/etc/smartd.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** smartd.conf (Y/I/N/O/D/Z) [default=N] ? d sh: 1: pager: not found diff: standard output: Broken pipe dpkg: error processing package smartmontools (--configure): conffile difference visualizer subprocess returned error exit status 127 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Thu Apr 2 19:58:06 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: /usr/bin/python3.8, Python 3.8.2, python-is-python3, 3.8.2-3 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.1 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago) mtime.conffile..etc.smartd.conf: 2019-06-28T19:35:09.428956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1870427/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Confirmed Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument
The bug is fixed in Ubuntu 20.04/focal. -- 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/1837245 Title: Failed to bump fs.file-max, ignoring: Invalid argument Status in systemd package in Ubuntu: Triaged Bug description: $ journalctl -b [...] [3.786804] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 19 13:44:43 2019 InstallationDate: Installed on 2018-12-02 (228 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to eoan on 2018-12-02 (228 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837245/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Here is my (very simple) LVM setup: # pvdisplay --- Physical volume --- PV Name /dev/nvme0n1p2 VG Name MonVolume2 PV Size <850.00 GiB / not usable 3.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 217599 Free PE 89599 Allocated PE 128000 PV UUID oZhDcb-KQRJ-eFm9-sKDf-ZztS-1oiI-X3dV0V # vgdisplay --- Volume group --- VG Name MonVolume2 System ID Formatlvm2 Metadata Areas1 Metadata Sequence No 48 VG Access read/write VG Status resizable MAX LV0 Cur LV1 Open LV 1 Max PV0 Cur PV1 Act PV1 VG Size <850.00 GiB PE Size 4.00 MiB Total PE 217599 Alloc PE / Size 128000 / 500.00 GiB Free PE / Size 89599 / <350.00 GiB VG UUID R8BWf2-UExN-WPsG-0bxU-7Qzf-PtlT-fgf4hS # lvdisplay --- Logical volume --- LV Path/dev/MonVolume2/UbuntuRacine LV NameUbuntuRacine VG NameMonVolume2 LV UUIDnhjz7g-J0GH-uMqQ-3QQU-eoJH-tuc3-YTMtcd LV Write Accessread/write LV Creation host, time ubuntu, 2019-05-03 18:45:22 +0200 LV Status available # open 1 LV Size500.00 GiB Current LE 128000 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: New Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)
My system had the same LVM setup in Ubuntu 19.10 and no error message was displayed during boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: New Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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
