[Touch-packages] [Bug 1817662] Re: Need to support WWAN module DW5820e
** Description changed: * Impact - New WWAN modeule like DW5820e is not supported. + New WWAN module like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. * Regression potential - As far as know (and we've been in communication with Aleksandr), MM 1.10 + As far as know (and we've been in communication with Aleksandr), MM 1.10 should be fully backwards compatible with NM 1.2x. ** Description changed: * Impact New WWAN module like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. + 3. Test a few exsting WWAN module and make sure they works. * Regression potential As far as know (and we've been in communication with Aleksandr), MM 1.10 should be fully backwards compatible with NM 1.2x. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1817662 Title: Need to support WWAN module DW5820e Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: * Impact New WWAN module like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. 3. Test a few exsting WWAN module and make sure they works. * Regression potential As far as know (and we've been in communication with Aleksandr), MM 1.10 should be fully backwards compatible with NM 1.2x. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817666] [NEW] system hangs
Public bug reported: i dont know ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-79.100~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 26 12:19:26 2019 DistUpgraded: 2016-11-14 14:16:19,712 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-11-12 (835 days ago) InstallationMedia: Edubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803.1) MachineType: LENOVO 20157 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic root=UUID=3006e45f-5f40-45c8-a376-3b9473cb4f8b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2016-11-14 (833 days ago) dmi.bios.date: 02/01/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN44WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr62CN44WW:bd02/01/2013:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 20157 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Feb 26 09:04:52 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16978 vendor SEC xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1817666 Title: system hangs Status in xorg package in Ubuntu: New Bug description: i dont know ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-79.100~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 26 12:19:26 2019 DistUpgraded: 2016-11-14 14:16:19,712 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-11-12 (835 days ago) InstallationMedia: Edubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803.1) MachineType: LENOVO 20157 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-79-generic root=UUID=3006e45f-5f40-45c8-a376-3b9473cb4f8b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2016-11-14 (833 days ago) dmi.bios.date: 02/01/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 62CN44WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake 2 dmi.board.vendo
[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Until the fix gets pushed to bionic and cosmic, you should able to get
stereo playback using the headphone jack adapter for the headsets that
should be included with them. Cable's a bit short, but it works.
--
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/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
In Progress
Status in pulseaudio source package in Cosmic:
In Progress
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817662] [NEW] Need to support WWAN module DW5820e
Public bug reported: * Impact New WWAN modeule like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. * Regression potential As far as know (and we've been in communication with Aleksandr), MM 1.10 should be fully backwards compatible with NM 1.2x. ** Affects: oem-priority Importance: Critical Assignee: Yuan-Chen Cheng (ycheng-twn) Status: Confirmed ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: somerville ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Description changed: * Impact New WWAN modeule like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. * Regression potential - TODO + As far as know (and we've been in communication with Aleksandr), MM 1.10 + should be fully backwards compatible with NM 1.2x. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1817662 Title: Need to support WWAN module DW5820e Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: * Impact New WWAN modeule like DW5820e is not supported. * Test case 1. Install the new Modem manager on the target machine that have DW5820e installed. 2. Plugged sim card, create a connection and make sure the internet connection is working. * Regression potential As far as know (and we've been in communication with Aleksandr), MM 1.10 should be fully backwards compatible with NM 1.2x. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal
I think it stuck in firmware/hardware instead of userspace process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 996848] Re: Ubuntu 12.04. "Time in other locations" - City "Kemerovo" has a wrong time zone assigned.
[Expired for tzdata (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tzdata (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/996848 Title: Ubuntu 12.04. "Time in other locations" - City "Kemerovo" has a wrong time zone assigned. Status in Indicator Date and Time: Incomplete Status in tzdata package in Ubuntu: Expired Bug description: Ubuntu 12.04 64 bits. Unfortunately, I don't know the name of the package which shows Time and Date on the top menu. I added city "Kemerovo" in All Settings -> Time & Date -> "Time in other locations" After I click on Date and Clock (top menu) and noticed that Kemerovo has a wrong time zone. Russia has merged some time zones and moved several cities to other time zones. Now, Kemerovo is in the same time zone as Novosibirsk. Currently, the difference is +1 hour. Please fix. Screenshot is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/996848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1026299] Re: wireless password corrupted?
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1026299 Title: wireless password corrupted? Status in network-manager package in Ubuntu: Expired Bug description: I have been using 12.04 for about a month. I have two primary locations for wireless connection, work and home. Both have worked perfectly until Wednesday of last week. My work connection is the issue. It works in Windows 7(dual boot), but no more in ubuntu. When it ques me for the password to access the wireless, I type in the password, but it takes three more "characters"(keystrokes) for the connect button to go from greyed out to black, but by then the password is wrong. I have deleted the connection, tried to reestablish the connection, re-booted all to no avail. I'm scratch'n my head on this one. Any help would be appreciated. The connect button also goes from greyed out to black with 5 digits in case this is important. The password is 10 digits. I have a Toshiba Laptop P205d-s7438 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1026299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session
** Changed in: pam (Ubuntu Xenial) Importance: Undecided => High ** Changed in: pam (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam source package in Xenial: Confirmed Status in pam source package in Bionic: Confirmed Status in pam package in Debian: Fix Released Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
This bug was fixed in the package xfce4-session - 4.12.1-6ubuntu1 --- xfce4-session (4.12.1-6ubuntu1) disco; urgency=medium * Merge from debian unstable. - Recommends no longer include xscreensaver (LP: #1754872) * Remaining changes: - debian/patches: + xubuntu_git_Make_verbose_logging_conditional.patch: Backport a commit to turn off verbose logging by default. + xubuntu_ignore-gdm-lang.patch: do not set $LANG to $GDM_LANG, there's already an xsession script to do that, and $GDM_LANG might not contain a valid locale code. + 0001-Update-locker-list-in-xflock4.patch: Use locker list from debian git to add support for xfce4-screensaver + 0001-Add-DesktopNames-to-.desktop-file.patch, 0001-Export-XDG_CURRENT_DESKTOP-Bug-11239.patch, 02_add-light-locker-to-xflock4.patch, 03_add-light-locker-to-xflock4.patch, 03_runtime-logind-support.patch, 03_xflock4-update-lockers-list.patch: dropped, included upstream - debian/systemd/*, debian/xfce4-session.install: + Add systemd user session. Note that this is not active for the XFCE session right now, it will just be used for xubuntu-default-setting's Xubuntu session. - d/rules, d/startxfce4.user-session.upstart, d/xfce4-session.install: + Add Xfce upstart user session -- Sean Davis Mon, 25 Feb 2019 20:46:14 -0500 ** Changed in: xfce4-session (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
confirmed my sound problem was solved using -Linux Kernel 4.19.10 on my -aus zenbook ux533fd -dual boot windows 10 and ubuntu 16.04 by following the next steps: 1. install Ukuu sudo add-apt-repository ppa:teejee2008/ppa sudo apt-get update sudo apt-get install ukuu 2. install kernel 4.19.10 sudo ukuu --install v4.19.10 3.restart(reboot)->select "advanced options" -> select kernel version 4.19.10 for more questions, simply: xing@gmail.com thanks the commends upon, especially #78 #96 thanks all ! -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817637] [NEW] a52 DigitalAC-3Pulseaudio not working on 19.04
Public bug reported: So I upgraded to 19.04 and now I no longer can get the a52 working. It worked fine on 18.10. this is the description I follow https://help.ubuntu.com/community /DigitalAC-3Pulseaudio also the package libasound2-plugins-extra that is supposed to do this for you is not working. I use the same kernel version so it's only userspace that has changed. There looks to only be small changes in the driver and I'm not sure if the driver code is even called before you actually try to use it but I never get so far I can not select the a52 device as it do not show up anywhere so I think its the configuraton that no longer works. or something, the configuration format is impossible to understand. https://git.alsa-project.org/?p=alsa- plugins.git;a=history;f=a52/pcm_a52.c;h=b005bc2040c0113f69ca081e6f7f75d69616f64c;hb=HEAD ** Affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1817637 Title: a52 DigitalAC-3Pulseaudio not working on 19.04 Status in alsa-plugins package in Ubuntu: New Bug description: So I upgraded to 19.04 and now I no longer can get the a52 working. It worked fine on 18.10. this is the description I follow https://help.ubuntu.com/community /DigitalAC-3Pulseaudio also the package libasound2-plugins-extra that is supposed to do this for you is not working. I use the same kernel version so it's only userspace that has changed. There looks to only be small changes in the driver and I'm not sure if the driver code is even called before you actually try to use it but I never get so far I can not select the a52 device as it do not show up anywhere so I think its the configuraton that no longer works. or something, the configuration format is impossible to understand. https://git.alsa-project.org/?p=alsa- plugins.git;a=history;f=a52/pcm_a52.c;h=b005bc2040c0113f69ca081e6f7f75d69616f64c;hb=HEAD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1817637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607696] Re: Version string missing in libjpeg.pc
This bug was fixed in the package libjpeg-turbo - 2.0.1-0ubuntu2 --- libjpeg-turbo (2.0.1-0ubuntu2) disco; urgency=medium * debian/libjpeg.pc.in, debian/rules: - remove the distro .pc copy, upstream provides one nowadays which includes a valid Version entry (lp: #1607696) -- Sebastien Bacher Mon, 25 Feb 2019 21:31:59 +0100 ** Changed in: libjpeg-turbo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1607696 Title: Version string missing in libjpeg.pc Status in libjpeg-turbo package in Ubuntu: Fix Released Bug description: Proper pkg-config files are installed if I build libjpeg-turbo myself. The description in the pkg-config file shipped by Ubuntu is also different from what is in upstream so I assume this is caused by Ubuntu (/Debian?) patching in a custom pkg-config file before they were included upstream in https://github.com/libjpeg-turbo/libjpeg- turbo/pull/53 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1607696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817531] Re: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat
** Package changed: ubuntu-settings (Ubuntu) => hplip (Ubuntu) -- 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/1817531 Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat Status in hplip package in Ubuntu: New Bug description: I can not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_43_46_generic_47 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Feb 25 12:30:11 2019 ErrorMessage: probleme de dependențe - se lasă neconfigurat InstallationDate: Installed on 2018-07-20 (220 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1817531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807721] Re: Fix variant selection in emoji chooser
I was able to successfully insert people variant emojis with libgtk-3-0 3.24.4-0ubuntu1 on Ubuntu 18.10 and with 3.22.30-1ubuntu2 on Ubuntu 18.04 LTS. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- 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/1807721 Title: Fix variant selection in emoji chooser Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Fix Committed Bug description: Impact == The variant selector in the emoji chooser was broken and will crash the app if used. Test Case = In an app like gedit, right click in the text area and select Insert Emoji Look for one of the "people" emoji. Right-click (or long-click) on the emoji and select one of the skin tones instead of the default yellow. The emoji with the skin tone you selected should be added to the text area. Regression Potential This fix was included in the gtk 3.24.2 release. There is a standing microrelease exception for GNOME point releases. GTK 3.24 was a big enough release (with some bumped dependencies) that it's not very practical to push to Ubuntu 18.04 LTS so we selectively cherry-pick fixes there. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b https://gitlab.gnome.org/GNOME/gtk/issues/1398 Other Info == This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: #1808233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications
I am marking this fixed since we have a proposed fix in progress tracked at https://launchpad.net/bugs/1808233 ** Changed in: gtk+3.0 (Ubuntu Cosmic) Status: In Progress => 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/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Cosmic: Fix Released Status in gtk+3.0 package in Debian: Fix Released Bug description: Tooltips are flicker constantly (i.e. repeatedly shown and the hidden again) in GTK3 applications under XFCE. It is a regression in the recent GTK 3.24. This is the upstream report and fix: https://gitlab.gnome.org/GNOME/gtk/issues/1371 https://gitlab.gnome.org/GNOME/gtk/commit/9b7d886b723132eade2e76f3fd179cf81b7601f2 A workaround for XFCE is as follows: Open Settings Editor. Set xsettings -> Gtk -> CursorThemeSize to 16. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.24.1-1ubuntu2 Uname: Linux 4.19.0-041900rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 12:23:53 2018 InstallationDate: Installed on 2017-02-01 (624 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1798861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
pygobject built successfully on Ubuntu 18.04 LTS and the autopkgtests confirm that it still works. https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#pygobject https://autopkgtest.ubuntu.com/packages/p/pygobject ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: Fix Committed Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807719] Re: Some emoji in emoji chooser are black & white
I confirmed that all emoji in the emoji chooser appear to be in full color with libgtk-3-0 3.24.4-0ubuntu1 on Ubuntu 18.10 and with 3.22.30-1ubuntu2 on Ubuntu 18.04 LTS. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- 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/1807719 Title: Some emoji in emoji chooser are black & white Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Fix Committed Bug description: Impact == Some emoji in the emoji chooser show as black & white. This is because these emoji default to "text presentation" instead of "emoji presentation". More information and a screenshot can be found in the pango issue linked below. Test Case = In an app like gedit, right click in the text area and select Insert Emoji Browse through the emoji list. All should be in full color. Regression Potential This fix was included in the gtk 3.24.2 release. There is a standing microrelease exception for GNOME point releases. GTK 3.24 was a big enough release (with some bumped dependencies) that it's not very practical to push to Ubuntu 18.04 LTS so we selectively cherry-pick fixes there. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/pango/issues/334 https://gitlab.gnome.org/GNOME/gtk/commit/aac38198a3f5 https://gitlab.gnome.org/GNOME/gtk/commit/b74e3209a5af0 Other Info == This adds an extra variation selector byte to each emoji added via the emoji chooser. (Many emoji are made up of multiple bytes.) This will not affect emoji added to GTK apps in other ways, such as copying and pasting from an app where the emoji doesn't have that variation selector added to it. This bug is fixed in gtk 3.24.2. Its SRU for cosmic is being tracked in LP: #1808233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1807719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4
I verified the Xfce bug by installing the xfce4 metapackage on top of Ubuntu 18.10. I could see the cursor flickering (and missing tooltip) by hovering over the text for one of the links in Archive Manager's Help. After installing libgtk-3-0 (and related packages) 3.24.4-0ubuntu1, the tooltip displayed correctly without flickering. I also ran several gtk3 apps in Ubuntu 18.10 and verified that they worked fine. I confirmed that switches looked ok with the Yaru and Adwaita themes. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1808233 Title: Update gtk to 3.24.4 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Cosmic: Fix Committed Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. Make sure that GTK switches look OK. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few regressions in the 3.24.2 and 3.24.3 releases.) This update changes the ON/OFF switches for GNOME's default Adwaita theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a font you have installed: currently, that's fonts-symbola which we no longer install by default). Previously, it was ❙/○ for most languages but ON/OFF for English (because English has short words that could fit on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which doesn't use labels on its switches. This is technically a UI change, but it is useful for compatibility with Flatpak apps that are being built with the new GTK. This change is small enough that it could be reverted for Ubuntu 18.10 if necessary. Other Info == The commit history shows themeing changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. The next scheduled gtk3 release (3.24.5 ? in March?) will include those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in- gtk-3/ for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1808233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817527] Re: ufw status problem
** Project changed: gui-ufw => ufw (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1817527 Title: ufw status problem Status in ufw package in Ubuntu: New Bug description: I recently have a spontaneous problem when running the command "service ufw status" and below picture is a result that shows me "active (exited)" status how can fix it ??? thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1817527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607696] Re: Version string missing in libjpeg.pc
** Changed in: libjpeg-turbo (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1607696 Title: Version string missing in libjpeg.pc Status in libjpeg-turbo package in Ubuntu: Fix Committed Bug description: Proper pkg-config files are installed if I build libjpeg-turbo myself. The description in the pkg-config file shipped by Ubuntu is also different from what is in upstream so I assume this is caused by Ubuntu (/Debian?) patching in a custom pkg-config file before they were included upstream in https://github.com/libjpeg-turbo/libjpeg- turbo/pull/53 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1607696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756516] Re: update libvorbis to 1.3.6
libvorbis 1.3.6 is in cosmic and the CVEs were already fixed in bionic (and earlier through security updates, I believe) ** Changed in: libvorbis (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libvorbis in Ubuntu. https://bugs.launchpad.net/bugs/1756516 Title: update libvorbis to 1.3.6 Status in libvorbis package in Ubuntu: Fix Released Bug description: libvorbis 1.3.6 (2018-03-16) -- "Xiph.Org libVorbis I 20180316 (Now 100% fewer shells)" * Fix CVE-2018-5146 - out-of-bounds write on codebook decoding. * Fix CVE-2017-14632 - free() on unitialized data * Fix CVE-2017-14633 - out-of-bounds read * Fix bitrate metadata parsing. * Fix out-of-bounds read in codebook parsing. * Fix residue vector size in Vorbis I spec. * Appveyor support * Travis CI support * Add secondary CMake build system. * Build system fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvorbis/+bug/1756516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817527] [NEW] ufw status problem
You have been subscribed to a public bug: I recently have a spontaneous problem when running the command "service ufw status" and below picture is a result that shows me "active (exited)" status how can fix it ??? thanks a lot ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- ufw status problem https://bugs.launchpad.net/bugs/1817527 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817617] [NEW] Video driver
Public bug reported: ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Mon Feb 25 17:05:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-02-22 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3442 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0P8H6J dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817617 Title: Video driver Status in xorg package in Ubuntu: New Bug description: ~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Mon Feb 25 17:05:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-02-22 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3442 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh ins
[Touch-packages] [Bug 1732522] Re: [2.3] Ephemeral boot environment does not renew DHCP leases
Is this still an issue that needs cloud-init work? ** Changed in: cloud-init Status: New => Incomplete -- 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/1732522 Title: [2.3] Ephemeral boot environment does not renew DHCP leases Status in cloud-init: Incomplete Status in MAAS: Fix Released Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I started commissioning+hardware testing on a machine, and while the machine was testing (for 2hrs+) i noticed that the IP address had disappeared. The machine has the MAC of 00:25:90:4c:e7:9e and IP of 192.168.0.211 from the dynamic range. Checking the MAAS server, I noticed that the IP/MAC was in the ARP table: andreserl@maas:/var/lib/maas/dhcp$ arp -a | grep 211 192-168-9-211.maas (192.168.9.211) at 00:25:90:4c:e7:9e [ether] on bond-lan Checking the leases file has the following: http://pastebin.ubuntu.com/25969442/ Then I checked a couple areas of MAAS: - Device discovery, the machine wasn't there. - Subnet details page, the machine wasn't there (e.g. as observed) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1732522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817557] Re: python3-software-properties broken
resolved by reinstalling packages.
** Changed in: software-properties (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1817557
Title:
python3-software-properties broken
Status in software-properties package in Ubuntu:
Invalid
Bug description:
I'm getting the following error when I try add an ppa.
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
mmattox@a1ubthorp01:~$ sudo add-apt-repository ppa:nilarimogard/webupd8
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 11, in
from softwareproperties.SoftwareProperties import SoftwareProperties,
shortcut_handler
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
64, in
from . import shortcuts
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
23, in
_DEF_CODENAME = aptsources.distro.get_distro().codename
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 576, in
get_distro
os_release = _OSRelease()
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 525, in
__init__
self.parse()
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 547, in
parse
self.parse_entry(*line.split('=', 1))
TypeError: parse_entry() missing 1 required positional argument: 'value'
mmattox@a1ubthorp01:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817557/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04
Hi guys I just upgraded to an informed version and the problem still continues. See attachment * Hi Pessoal Acabei de atualizar para versão informada e o problema ainda continua. Vide anexo ** Attachment added: "Captura de tela de 2019-02-25 15-02-39.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+attachment/5241610/+files/Captura%20de%20tela%20de%202019-02-25%2015-02-39.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817352 Title: Livepatch is not available for this system Ubuntu Disco 19.04 Status in software-properties package in Ubuntu: Fix Released Bug description: Hi guys There is an option for livepacth, but there is information that is not yet available for Ubuntu Disk 19.04. Will the livepatch be available for Ubuntu Disk 19.04? "Livepacth is not available for this system" See attached Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.6 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 22 14:08:04 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04
This bug was fixed in the package software-properties - 0.97.7 --- software-properties (0.97.7) disco; urgency=medium [ Andrea Azzarone ] * LivepatchPage: Make sure the scrolled window of the error message view is always visible (lp: #1817352) -- Sebastien Bacher Mon, 25 Feb 2019 15:47:00 +0100 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817352 Title: Livepatch is not available for this system Ubuntu Disco 19.04 Status in software-properties package in Ubuntu: Fix Released Bug description: Hi guys There is an option for livepacth, but there is information that is not yet available for Ubuntu Disk 19.04. Will the livepatch be available for Ubuntu Disk 19.04? "Livepacth is not available for this system" See attached Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.6 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 22 14:08:04 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 330972] Re: evince alpha blur rendering errors
Verified with newest evince: 3.31.90-1 and the bug doesn't exit any more. ** Changed in: poppler (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/330972 Title: evince alpha blur rendering errors Status in Poppler: Fix Released Status in poppler package in Ubuntu: Fix Released Bug description: Binary package hint: evince Description: Ubuntu 8.10 Release: 8.10 evince: Installed: 2.24.1-0ubuntu1 Evince is having problems rendering layered pictures with alpha blurs. Here's the link to the sample pdf: http://www.whiteestate.org/vez/oct08/VeZ_Sports-web.pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/330972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic
@Brian - it was already meant to be marked verification-failed per comment #33 , so IMHO there is no hope anymore to get this verified. Further there is work incoming for ua-tools in Xenial (and Trusty), for that I'd really appreciate if this could be removed from proposed even sooner than after 15 days - to have some clarity on the versions we will work with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1735160 Title: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic Status in httmock package in Ubuntu: Fix Released Status in protobuf package in Ubuntu: Fix Released Status in py-macaroon-bakery package in Ubuntu: Fix Released Status in pymacaroons package in Ubuntu: Fix Released Status in httmock source package in Xenial: In Progress Status in protobuf source package in Xenial: Fix Committed Status in py-macaroon-bakery source package in Xenial: In Progress Status in pymacaroons source package in Xenial: Fix Committed Status in httmock source package in Artful: Invalid Status in protobuf source package in Artful: Invalid Status in py-macaroon-bakery source package in Artful: In Progress Status in pymacaroons source package in Artful: Fix Committed Bug description: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - for protobuf: $ python3 -c "import google.protobuf" - for protobuf: $ python2 -c "import google.protobuf" - for python3-macaroonbakery: make sure all the tests pass - make sure "snapcraft login" works properly [Regression Potential] - httmock, none has it's not in xenial - protobuf, reduced considering that the code has been backported from master (small changes to make it compatabile py3 compatabile) - pymacaroons, none has 0.12 is backward compatible with 0.9.2 - py-macaroon-bakery, none has it's not in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal
Tested with multiple OSs, all stuck: Ubuntu 14, Fedora 29, Arch Linux current 2019.02.01. We received a detailed note from the next level of support with HPE and decided to test with Ubuntu 16 (our production one) and set "ps -ef >> /shutdown-log.txt" in to the debug.sh script. Maybe we can see something that is not closed/terminated and prevent the server to reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817557] Re: python3-software-properties broken
** Package changed: ubuntu => software-properties (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1817557
Title:
python3-software-properties broken
Status in software-properties package in Ubuntu:
New
Bug description:
I'm getting the following error when I try add an ppa.
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
mmattox@a1ubthorp01:~$ sudo add-apt-repository ppa:nilarimogard/webupd8
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 11, in
from softwareproperties.SoftwareProperties import SoftwareProperties,
shortcut_handler
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
64, in
from . import shortcuts
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
23, in
_DEF_CODENAME = aptsources.distro.get_distro().codename
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 576, in
get_distro
os_release = _OSRelease()
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 525, in
__init__
self.parse()
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 547, in
parse
self.parse_entry(*line.split('=', 1))
TypeError: parse_entry() missing 1 required positional argument: 'value'
mmattox@a1ubthorp01:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817557/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817557] [NEW] python3-software-properties broken
You have been subscribed to a public bug:
I'm getting the following error when I try add an ppa.
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
mmattox@a1ubthorp01:~$ sudo add-apt-repository ppa:nilarimogard/webupd8
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 11, in
from softwareproperties.SoftwareProperties import SoftwareProperties,
shortcut_handler
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
64, in
from . import shortcuts
File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line
23, in
_DEF_CODENAME = aptsources.distro.get_distro().codename
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 576, in
get_distro
os_release = _OSRelease()
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 525, in
__init__
self.parse()
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 547, in parse
self.parse_entry(*line.split('=', 1))
TypeError: parse_entry() missing 1 required positional argument: 'value'
mmattox@a1ubthorp01:~$
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
python3-software-properties broken
https://bugs.launchpad.net/bugs/1817557
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to software-properties in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817537] Re: libsoup should support ntlmv2
The issue is fixed in the current Ubuntu version, closing for the current serie. The commit looks like it's not too complex and could probably be backported to 18.04 https://gitlab.gnome.org/GNOME/libsoup/commit/0e7b2c14 (and https://gitlab.gnome.org/GNOME/libsoup/commit/7e4b94cd) ** Changed in: libsoup2.4 (Ubuntu) Importance: Undecided => High ** Changed in: libsoup2.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Bug description: Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04
** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817352 Title: Livepatch is not available for this system Ubuntu Disco 19.04 Status in software-properties package in Ubuntu: Fix Committed Bug description: Hi guys There is an option for livepacth, but there is information that is not yet available for Ubuntu Disk 19.04. Will the livepatch be available for Ubuntu Disk 19.04? "Livepacth is not available for this system" See attached Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.6 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 22 14:08:04 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583255] Re: Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist
It seems that the correct config file location is /etc/xrdp/pulse/default.pa, because of the xrdpd usage. :) -- 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/1583255 Title: Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist Status in pulseaudio package in Ubuntu: New Bug description: System is Ubuntu 16.04 According to Ubuntu Pulseaudio MAN page: http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html it says... The PulseAudio sound server interprets a configuration script on startup, which is mainly used to define the set of modules to load. When PulseAudio runs in the per-usermodeand ~/.config/pulse/default.pa exists, that file is used. When PulseAudio runs in the per-user mode and that file doesn't exist, /etc/pulse/default.pa is used. On my system I have put the following into - /etc/pulse/default.pa load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 The contents of my ~/.config/pulse/ directory contains NO default.pa file only the cookie file: $ ls ~/.config/pulse cookie After a reload I issue the command patcl list modules and the "module- native-protocol-tcp" is NOT listed ? $ pactl list modules Module #0 Name: module-augment-properties Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Augment the property sets of streams with additional static information" module.version = "8.0" Module #1 Name: module-always-sink Argument: Usage counter: n/a Properties: module.author = "Colin Guthrie" module.description = "Always keeps at least one sink loaded even if it's a null one" module.version = "8.0" Module #3 Name: module-xrdp-sink Argument: Usage counter: 0 Properties: module.author = "Jay Sorg" module.description = "xrdp sink" module.version = "8.0" Module #4 Name: module-xrdp-source Argument: Usage counter: n/a Properties: module.author = "Laxmikant Rashinkar" module.description = "xrdp source" module.version = "8.0" Module #5 Name: module-native-protocol-unix Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Native protocol (UNIX sockets)" module.version = "8.0" Module #6 Name: module-cli-protocol-unix Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Command line interface protocol (UNIX sockets)" module.version = "8.0" I am filing this bug because according to the MAN page (see above)... since I do NOT have a ~/.config/pulse/default.pa Ubuntu/Pulseaudio should be executing the /etc/pulse/default.pa configuration instead... which should be loading: load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 but it not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Hello Agustin, or anyone else affected, Accepted gnome-shell into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.28.3+git20190124-0ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Incomplete Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.prod
[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04
** Branch linked: lp:~azzar1/software-properties/fix-1817352 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817352 Title: Livepatch is not available for this system Ubuntu Disco 19.04 Status in software-properties package in Ubuntu: In Progress Bug description: Hi guys There is an option for livepacth, but there is information that is not yet available for Ubuntu Disk 19.04. Will the livepatch be available for Ubuntu Disk 19.04? "Livepacth is not available for this system" See attached Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.6 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 22 14:08:04 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04
I'm attaching a screenshot of how it was supposed to be. There is a small bug in software-properties-gtk that is preventing the error to appear. I've already proposed a fix for this. Thanks for the report. ** Attachment added: "Screenshot from 2019-02-25 13-01-15.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+attachment/5241551/+files/Screenshot%20from%202019-02-25%2013-01-15.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817352 Title: Livepatch is not available for this system Ubuntu Disco 19.04 Status in software-properties package in Ubuntu: In Progress Bug description: Hi guys There is an option for livepacth, but there is information that is not yet available for Ubuntu Disk 19.04. Will the livepatch be available for Ubuntu Disk 19.04? "Livepacth is not available for this system" See attached Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.6 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 22 14:08:04 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: software-properties (Ubuntu) Importance: Low => Medium ** Changed in: software-properties (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817352 Title: Livepatch is not available for this system Ubuntu Disco 19.04 Status in software-properties package in Ubuntu: In Progress Bug description: Hi guys There is an option for livepacth, but there is information that is not yet available for Ubuntu Disk 19.04. Will the livepatch be available for Ubuntu Disk 19.04? "Livepacth is not available for this system" See attached Thank you ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.6 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 22 14:08:04 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-02-11 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793120] Re: Ubuntu 18.04.1 Desktop install fails to show try or install choice
Tried with ubuntu-18.04.2-desktop-amd64. Same error. -- 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/1793120 Title: Ubuntu 18.04.1 Desktop install fails to show try or install choice Status in systemd package in Ubuntu: New Bug description: When I try to install Ubuntu 18.04 (replacing rather than updating 16.04) on my HP Pavilion dv7 6080eo laptop, which currently runs Windows in dual boot with Ubuntu 16.04 LTS for amd64, I never get the screen with the Try Ubuntu or Install Ubuntu choice. Instead the GUI drops into "terminal mode" showing some errors, and after some time I can log into "Try Ubuntu" mode. I have verified the DVD with two methods: Compared the MD5 sum of the ubuntu-18.04.1-desktop-amd64.iso file using md5sum with the value on the web, f430da8fa59d2f5f4262518e3c177246, and checked the DVD using the command: dd if=/dev/sr0 | head -c $(wc -c .../ubuntu-18.04.1-desktop- amd64.iso) | md5sum | cut -d' ' -f1 which also returned f430da8fa59d2f5f4262518e3c177246. Verified the DVD integrity, booting the HP with ubuntu-18.04.1 -desktop-amd64 DVD and used the Check CD for defects menu option, which was successful. The "terminal output" I get before the "installation" on the HP drops into try mode includes (at least) one suspicious line in the beginning (I have attached a picture): [ OK ] Created slice system-lvm2\x2dpvscan.slice Starting LVM2 PV scan on device 8:6... [ OK ] Started Snappy daemon. Starting Wait until snapd is fully seeded.. Starting Holds Snappy daemon refresh... [ FAILED ] Failed to start Dispatcher daemon for systemd-networkd. : : When I boot on an old Asus laptop (K70IO) from that DVD, everything behaves normally. When I boot the HP laptop with a DVD with ubuntu-16.04.1-amd.iso, everything behaves normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: quassel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1814302 Title: Quasselcore apparmor profile issue in lxd container. Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in quassel package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 container. Everything up todate via apt. Install quassel-core. Service will not start. Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start. I then added "/usr/bin/quasselcore rm," to "/etc/apparmor.d/usr.bin.quasselcore". Set "aa-enforce /usr/bin/quasselcore". Restarted main host. Quasselcore service now starts and I can connect to it. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1814302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1814302 Title: Quasselcore apparmor profile issue in lxd container. Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in quassel package in Ubuntu: Confirmed Bug description: Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 container. Everything up todate via apt. Install quassel-core. Service will not start. Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start. I then added "/usr/bin/quasselcore rm," to "/etc/apparmor.d/usr.bin.quasselcore". Set "aa-enforce /usr/bin/quasselcore". Restarted main host. Quasselcore service now starts and I can connect to it. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1814302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Proposed package upload rejected
An upload of libunistring to bionic-proposed has been rejected from the upload queue for the following reason: "This upload has only an FTBFS bug attached to it even though it's a new upstream release SRU (from 0.9.9 tp 0.9.10). That does not seem like the 'fix' to a FTBFS issue. Please re-upload with just the FTBFS fix or fill in additional SRU bugs for all the other changes.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: Won't Fix Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file
This bug was fixed in the package apt - 1.0.1ubuntu2.20 --- apt (1.0.1ubuntu2.20) trusty; urgency=medium [ Julian Andres Klode ] * Fix crashes in apt search, cache file (LP: #1815187) * Clean up some build artifacts and regenerate the po files [ Heitor R. Alves de Siqueira ] * backport "do not segfault in cache generation on mmap failure" (Closes: 803417) (LP: #1815129) -- Julian Andres Klode Fri, 08 Feb 2019 13:12:26 +0100 ** Changed in: apt (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, ... apt | 1.0.1ubuntu2.19 | trusty-security | source, ... apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... apt | 1.2.10ubuntu1 | xenial | source, ... apt | 1.6.1 | bionic | source, ... apt | 1.7.0 | cosmic | source, ... apt | 1.8.0~rc2 | disco| source, ... [Test Case] 1) Deploy a Trusty (14.04 LTS) vm w/ 128M 2) Fetch latest stress-ng src code 2.1) git clone git://kernel.ubuntu.com/cking/stress-ng 2.2) cd stress-ng 2.3) make clean 2.4) make 3) Stress the mmap() with stress-ng 3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90% 4) Disable swap (if any) 4.1) swapoff -a 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done ... vsftpd: Installed: (none) Candidate: 3.0.2-1ubuntu2.14.04.1 Version table: 3.0.2-1ubuntu2.14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.0.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) ... [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815187] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815187 Title: Fix crash when opening DepCache before Cache Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Bug description: [Impact] apt search and probably other code crashes some time, as GetDepCache() in trusty does not call BuildCaches() first. [Test case] Run apt search -o RootDir=/dev/null foobar, make sure it does not crash. [Regression potential] There may be some locking implications, as we build caches when opening depcache first, without locks. That said, the same code is in use in all post-trusty releases, and they work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815129] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815129 Title: apt segfaults when generating cache file Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] apt crashes (core dump) during cache creation [Description] When executing apt-cache several times on a memory constrained system, apt-cache can sometimes crash with a core dump file. This is related to mmap() failing allocations during cache generation, according to an upstream bug report (803417). There is an upstream patch for this bug (6789e01e do not segfault in cache generation on mmap failure) and it's included in the apt package for other series (see below), so we only need to backport it to Trusty. Upstream commit: https://salsa.debian.org/apt- team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1 $ git describe --contains 6789e01e9370 1.1_exp16~5 $ rmadison apt apt | 1.0.1ubuntu2| trusty | source, ... apt | 1.0.1ubuntu2.19 | trusty-security | source, ... apt | 1.0.1ubuntu2.19 | trusty-updates | source, ... apt | 1.2.10ubuntu1 | xenial | source, ... apt | 1.6.1 | bionic | source, ... apt | 1.7.0 | cosmic | source, ... apt | 1.8.0~rc2 | disco| source, ... [Test Case] 1) Deploy a Trusty (14.04 LTS) vm w/ 128M 2) Fetch latest stress-ng src code 2.1) git clone git://kernel.ubuntu.com/cking/stress-ng 2.2) cd stress-ng 2.3) make clean 2.4) make 3) Stress the mmap() with stress-ng 3.1) ./stress-ng --brk 2 --mmap 5 --vm 1 --mmap-bytes 90% 4) Disable swap (if any) 4.1) swapoff -a 5) for i in `seq 1 1`;do apt-cache policy vsftpd;done ... vsftpd: Installed: (none) Candidate: 3.0.2-1ubuntu2.14.04.1 Version table: 3.0.2-1ubuntu2.14.04.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 3.0.2-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) ... [Regression Potential] The regression potential for this should be low, as it's a change in the failure path for memory allocations. This shouldn't be triggered during normal usage, and we'll thoroughly test the patched package with autopkgtests and perform scripted runs in memory-constrained systems with stress-ng. We also have a confirmation from an impacted user that the upstream patch fixes their issue without further problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815187] Re: Fix crash when opening DepCache before Cache
This bug was fixed in the package apt - 1.0.1ubuntu2.20 --- apt (1.0.1ubuntu2.20) trusty; urgency=medium [ Julian Andres Klode ] * Fix crashes in apt search, cache file (LP: #1815187) * Clean up some build artifacts and regenerate the po files [ Heitor R. Alves de Siqueira ] * backport "do not segfault in cache generation on mmap failure" (Closes: 803417) (LP: #1815129) -- Julian Andres Klode Fri, 08 Feb 2019 13:12:26 +0100 ** Changed in: apt (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815187 Title: Fix crash when opening DepCache before Cache Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Bug description: [Impact] apt search and probably other code crashes some time, as GetDepCache() in trusty does not call BuildCaches() first. [Test case] Run apt search -o RootDir=/dev/null foobar, make sure it does not crash. [Regression potential] There may be some locking implications, as we build caches when opening depcache first, without locks. That said, the same code is in use in all post-trusty releases, and they work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813584] Re: libidn ftbfs in 18.04 LTS
All reported 4 systemd autopkgtests are failing since a while now, unrelated to the current FTBFS SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Released Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. It is important that packages in stable series are buildable at all times in case security updates need to be prepared. [Test Case] Make sure the package builds successfully. [Regression Potential] Should be relatively minimal. The same change was present in Ubuntu since cosmic, so we would already get mentions of regressions previously. [Original Description] = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815125] Re: constant video freezes in firefox with x-x-v-amdgpu 18.1.0
This bug was fixed in the package libx11 - 2:1.6.4-3ubuntu0.2 --- libx11 (2:1.6.4-3ubuntu0.2) bionic; urgency=medium * call-poll-for-event-again.diff: Fix constant video freezes on firefox with amdgpu. (LP: #1815125) -- Timo Aaltonen Thu, 07 Feb 2019 22:04:25 +0200 ** Changed in: libx11 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1815125 Title: constant video freezes in firefox with x-x-v-amdgpu 18.1.0 Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Released Bug description: [Impact] There are constant video freezes in firefox (e.g. on youtube) with xf86-video-amdgpu-18.1.0, which is included in the HWE stack in 18.04.2 https://bugs.freedesktop.org/show_bug.cgi?id=107992 [Test case] test firefox with youtube on radeon [Regression potential] it's a single commit from upstream 1.6.7, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1815125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815125] Update Released
The verification of the Stable Release Update for libx11 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1815125 Title: constant video freezes in firefox with x-x-v-amdgpu 18.1.0 Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Released Bug description: [Impact] There are constant video freezes in firefox (e.g. on youtube) with xf86-video-amdgpu-18.1.0, which is included in the HWE stack in 18.04.2 https://bugs.freedesktop.org/show_bug.cgi?id=107992 [Test case] test firefox with youtube on radeon [Regression potential] it's a single commit from upstream 1.6.7, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1815125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817537] [NEW] libsoup should support ntlmv2
Public bug reported: Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) ** Affects: libsoup2.4 (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 libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: New Bug description: Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817531] Re: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat
** Tags removed: need-duplicate-check -- 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/1817531 Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat Status in ubuntu-settings package in Ubuntu: New Bug description: I can not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_43_46_generic_47 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Feb 25 12:30:11 2019 ErrorMessage: probleme de dependențe - se lasă neconfigurat InstallationDate: Installed on 2018-07-20 (220 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1817531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817531] [NEW] package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat
Public bug reported: I can not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_43_46_generic_47 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Feb 25 12:30:11 2019 ErrorMessage: probleme de dependențe - se lasă neconfigurat InstallationDate: Installed on 2018-07-20 (220 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (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 ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1817531 Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat Status in ubuntu-settings package in Ubuntu: New Bug description: I can not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_43_46_generic_47 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Feb 25 12:30:11 2019 ErrorMessage: probleme de dependențe - se lasă neconfigurat InstallationDate: Installed on 2018-07-20 (220 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: probleme de dependențe - se lasă neconfigurat UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1817531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: visualvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in visualvm package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [
[Touch-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
** Changed in: sddm Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Unknown Status in SDDM: Fix Released Status in accountsservice package in Ubuntu: Triaged Status in ceph package in Ubuntu: Triaged Status in ifmail package in Ubuntu: Triaged Status in libvirt package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in netqmail package in Ubuntu: Triaged Status in sddm package in Ubuntu: Fix Released Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
