[Touch-packages] [Bug 1792579] Re: Network Disconnecting Intermittantly
[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/1792579 Title: Network Disconnecting Intermittantly Status in network-manager package in Ubuntu: Expired Bug description: On my machine (OPTIPLEX GX620, Xubuntu 18.04 LTS) my wired (Ethernet) connection disconnects randomly. Everything was fine before the upgrade from Xenial LTS. It's not yet reproducible (by me). There are no error messages associated with it, the indicator plugin doesn't turn grey, and I've noticed no pattern to when it occurs. The only way I know it is has occurred is when something that uses the (Samba) network times out or stops doing anything. If I click the indicator plugin and select "wired connection 1", it reconnects immediately, But at some later time the same thing may happen again; it could be after a few minutes or many hours. This happens on another, the AMD machine I use as a file server, too, so it looks like a bug in Bionic Beaver, not a software package. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 I suppose the bug could have something to do with the compatibility of Samba and 18.04 LTS, because after the upgrade, everything in /etc/fstab that used the credentials option stopped working, but that's part of another bug already reported by others but not yet solved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 559331] Re: Permanent "Printer-out-of-paper" message.
Same problem here. Ubuntu 19.04 and Canon MG5320 printer. ALways out of paper but wrong. A color ink is low but paper is ok and I print black & white. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/559331 Title: Permanent "Printer-out-of-paper" message. Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest on Karmic). I was printing a document when the printer was out of paper and got a message that "The printer is out of paper". I went to reload it and clicked resume on the printer and printing carried on normally. From this point on, the message "The printer is out of paper" is permanently stuck on the printer. - Every time i print, i get the message "The printer is out of paper", but the printing occurs without errors. - The configuration tool (system-config-printer 1.1.12) shows the printer with the red error sign. When viewing the properties of said printer, in the "Ink/Toner Levels" section, i have the "Status Message": "Printer HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS server error": "There was an error during the CUPS operation: 'client-error-document-format-not-supported'." (Not sure this is relevant). Removing and reinstalling the printer fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844902] [NEW] Pulseaudio broken after update
Public bug reported: after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get no sound and when killing the demon it restarts with the following error - [pulseaudio] main.c: pa_pid_file_create() failed. Reboot does not restore sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181 Uname: Linux 4.4.0-157-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 1745 F pulseaudio /dev/snd/controlC0: david 1745 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 22 11:05:48 2019 InstallationDate: Installed on 2017-01-03 (991 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503 dmi.board.name: DCP847SKE dmi.board.vendor: Intel Corporation dmi.board.version: G80890-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr: ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1844902 Title: Pulseaudio broken after update Status in pulseaudio package in Ubuntu: New Bug description: after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get no sound and when killing the demon it restarts with the following error - [pulseaudio] main.c: pa_pid_file_create() failed. Reboot does not restore sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181 Uname: Linux 4.4.0-157-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 1745 F pulseaudio /dev/snd/controlC0: david 1745 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 22 11:05:48 2019 InstallationDate: Installed on 2017-01-03 (991 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503 dmi.board.name: DCP847SKE dmi.board.vendor: Intel Corporation dmi.board.version: G80890-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1844902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
** Changed in: ibus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844897] [NEW] wifi icon has question mark in it even though network is fine
Public bug reported: After experiencing some "turbulence" in my wifi (I rebooted my primary wifi router, which caused my laptop to fallback onto a secondary access point which didn't have full connectivity until the primary router finished rebooting, then I rebooted the primary router a second time), the wifi icon in my top bar stayed as the question-mark icon (i.e., the icon that shows when Network Manager doesn't think you have full connectivity) even after everything was back up and in fact my connectivity was fine. Turning wifi off and back on did not cause the question mark to go away. Restarting Network Manager did not cause the question mark to go away. Switching to a different wifi network and then back to the previous one didn't cause the question mark to go away. I had to reboot my laptop to get the question mark to go away. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 18:35:48 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-12 (9 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1844897 Title: wifi icon has question mark in it even though network is fine Status in network-manager package in Ubuntu: New Bug description: After experiencing some "turbulence" in my wifi (I rebooted my primary wifi router, which caused my laptop to fallback onto a secondary access point which didn't have full connectivity until the primary router finished rebooting, then I rebooted the primary router a second time), the wifi icon in my top bar stayed as the question-mark icon (i.e., the icon that shows when Network Manager doesn't think you have full connectivity) even after everything was back up and in fact my connectivity was fine. Turning wifi off and back on did not cause the question mark to go away. Restarting Network Manager did not cause the question mark to go away. Switching to a different wifi network and then back to the previous one didn't cause the question mark to go away. I had to reboot my laptop to get the question mark to go away. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 21 18:35:48 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-12 (9 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.4
Adding a console log text from above because line wrapping made it unreadable in the body of my comment. ** Attachment added: "console-log-python3.6.log" https://bugs.launchpad.net/ubuntu/+source/python3.6/+bug/1835738/+attachment/5290266/+files/console-log-python3.6.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.4 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Bug description: Update Python interpreter to 3.6.9 and 3.7.4. As done with earlier subminor upstream releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.4
I am not sure if this is the place to report this, but I cannot think of a better one to attract Mathias' attention, sorry. Four python3.6 packages (and likely also python3.7 and python3.8) currently available in the ubuntu-toolchain-r PPA have an unmet version dependency on the 'python3' package. After adding the ppa, apt reports certain packages as upgradeable, but they cannot be upgraded: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic # uname -a Linux [redacted] 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # apt list --upgradable | grep python WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libpython3.6/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] libpython3.6-dev/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] libpython3.6-minimal/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] libpython3.6-stdlib/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3-distutils/bionic 3.6.9-1~18.04 all [upgradable from: 3.6.8-1~18.04] python3-gdbm/bionic 3.6.9-1~18.04 amd64 [upgradable from: 3.6.8-1~18.04] python3-lib2to3/bionic 3.6.9-1~18.04 all [upgradable from: 3.6.8-1~18.04] python3-tk/bionic 3.6.9-1~18.04 amd64 [upgradable from: 3.6.8-1~18.04] python3.6/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3.6-dev/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3.6-minimal/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] python3.6-venv/bionic 3.6.9-1~b1 amd64 [upgradable from: 3.6.8-1~18.04.2] # apt upgrade --dry-run libpython3.6 libpython3.6-dev libpython3.6-minimal libpython3.6-stdlib python3-distutils python3-gdbm python3-lib2to3 python3-tk python3.6-venv Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... 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: python3-distutils : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed python3-gdbm : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed python3-lib2to3 : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed python3-tk : Depends: python3 (>= 3.6.8-1~) but 3.6.7-1~18.04 is to be installed E: Broken packages 'apt show python3 -a' indicates the version 3.6.7-1~18.04 is from 'http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64', and there is also an original distro version 3.6.5-3 that hails from bionic/main. No other sources are available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.4 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Bug description: Update Python interpreter to 3.6.9 and 3.7.4. As done with earlier subminor upstream releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844887] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem
Trying ALSA driver compilation as stated in https://help.ubuntu.com/community/SoundTroubleshooting gives error and this output. for i in control postinst postrm ; do \ if [ -f debian/$i.orig ]; then \ mv -f debian/$i.orig debian/$i ; \ fi ; \ done rm -f control-munge make mrproper make[1]: Entering directory '/usr/src/modules/alsa-driver' rm -f .depend *.o snd.map* rm -f modules/*.o modules/*.ko make[2]: Entering directory '/usr/src/modules/alsa-driver/include' make[2]: Leaving directory '/usr/src/modules/alsa-driver/include' Makefile:288: recipe for target 'mrproper' failed make[1]: Leaving directory '/usr/src/modules/alsa-driver' debian/rules:154: recipe for target 'clean' failed rm -f configure-stamp rm -f build-stamp /usr/bin/make -f debian/rules binary-modules make[1]: Entering directory '/usr/src/modules/alsa-driver' CC="gcc" ./configure --prefix=/usr --with-kernel=/usr/src/linux --with-build=/usr/src/linux --with-moddir=/lib/modules/4.4.0-164-generic/updates/alsa --with-sequencer=yes --with-isapnp=yes --with-debug=detect --with-cards="hda-intel" checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for ranlib... ranlib checking for a BSD-compatible install... /usr/bin/install -c checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking whether time.h and sys/time.h may both be included... yes checking whether gcc needs -traditional... no checking for current directory... /usr/src/modules/alsa-driver checking cross compile... checking for directory with ALSA kernel sources... /usr/src/modules/alsa-driver/alsa-kernel checking for directory with kernel source... /usr/src/linux checking for directory with kernel build... /usr/src/linux checking for kernel linux/version.h ... no The file /usr/src/linux/include/INCLUDE_VERSION_H does not exist. Please install the package with full kernel sources for your distribution or use --with-kernel=dir option to specify another directory with kernel sources (default is /lib/modules/4.4.0-164-generic/build). debian/rules:119: recipe for target 'configure-stamp' failed make[1]: *** [configure-stamp] Error 1 make[1]: Leaving directory '/usr/src/modules/alsa-driver' debian/rules:197: recipe for target 'kdist_image' failed make: *** [kdist_image] Error 2 -- 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/1844887 Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Headphones not detected, low output volume(even when I put more then 100% volume), right speaker doesnt work. Here is output of some commands I was guided to post here, from troubleshoot instruction. https://help.ubuntu.com/community/SoundTroubleshooting XPS-15-9560:~$ sudo aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3266 Analog [ALC3266 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 find /lib/modules/`uname -r` | grep snd -This command gives a large list XPS-15-9560:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80) Subsystem: Dell Device 07be Flags: bus master, fast devsel, latency 32, IRQ 17 Memory at ed128000 (64-bit, non-prefetchable) [size=16K] Memory at ed10 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel *Additional information XPS-15-9560:~$ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 XPS-15-9560:~$ apt-cache policy pkgname alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-164.192-generic 4.4.186 Uname: Linux 4.4.0-164-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
** Bug watch added: github.com/ibus/ibus/issues #2137 https://github.com/ibus/ibus/issues/2137 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2137 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: Unknown Status in ibus package in Ubuntu: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844887] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem
** Description changed: Headphones not detected, low output volume(even when I put more then 100% volume), right speaker doesnt work. Here is output of some commands I was guided to post here, from troubleshoot instruction. https://help.ubuntu.com/community/SoundTroubleshooting XPS-15-9560:~$ sudo aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3266 Analog [ALC3266 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 find /lib/modules/`uname -r` | grep snd -This command gives a large list XPS-15-9560:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80) Subsystem: Dell Device 07be Flags: bus master, fast devsel, latency 32, IRQ 17 Memory at ed128000 (64-bit, non-prefetchable) [size=16K] Memory at ed10 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel - Information you required in the bug report:** + *Additional information + + XPS-15-9560:~$ lsb_release -rd + Description: Ubuntu 16.04.6 LTS + Release: 16.04 XPS-15-9560:~$ apt-cache policy pkgname alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-164.192-generic 4.4.186 Uname: Linux 4.4.0-164-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vasko 2204 F...m pulseaudio /dev/snd/controlC0: vasko 2204 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 21 22:05:15 2019 InstallationDate: Installed on 2018-10-15 (340 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/26/2019:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-06T23:26:58.909811 -- 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/1844887 Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Headphones not detected, low output volume(even when I put more then 100% volume), right speaker doesnt work. Here is output of some commands I was guided to post here, from troubleshoot instruction. https://help.ubuntu.com/community/SoundTroubleshooting XPS-15-9560:~$ sudo aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3266 Analog [ALC3266 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 find /lib/modules/`uname -r` | grep snd -This command gives a large list XPS-15-9560:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80) Subsystem: Dell Device 07be Flags: bus master, fast devsel, latency 32, IRQ 17 Memory at ed128000 (64-bit, non-prefetchable) [size=16K] Memory at ed10 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel *Additional information XPS-15-9560:~$ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 XPS-15-9560:~$ apt-cache policy pkgname alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500
[Touch-packages] [Bug 1680811] Re: Request to add wireguard interface to interface-order
I hace openresolv installed, do not have resolvconf installed, and I still see the above error. I see the error even after deleting /etc/resolv.conf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1680811 Title: Request to add wireguard interface to interface-order Status in resolvconf package in Ubuntu: Triaged Bug description: This started from https://github.com/jlund/streisand/issues/557. Basically wg* namespace is not in interface-order and acts last in * scope, and this makes resolv.conf to stay in the same state. I suggest the following change: :/etc/resolvconf/interface-order # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo +wg* tun* tap* hso* em+([0-9])?(_+([0-9]))* p+([0-9])p+([0-9])?(_+([0-9]))* @(br|eth)*([^.]).inet6 @(br|eth)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)*([^.]).inet @(br|eth)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(br|eth)* @(ath|wifi|wlan)*([^.]).inet6 @(ath|wifi|wlan)*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)*([^.]).inet @(ath|wifi|wlan)*([^.]).@(dhclient|dhcpcd|pump|udhcpc) @(ath|wifi|wlan)* ppp* * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844887] [NEW] [HDA-Intel - HDA Intel PCH, playback] Playback problem
Public bug reported: Headphones not detected, low output volume(even when I put more then 100% volume), right speaker doesnt work. Here is output of some commands I was guided to post here, from troubleshoot instruction. https://help.ubuntu.com/community/SoundTroubleshooting XPS-15-9560:~$ sudo aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3266 Analog [ALC3266 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 find /lib/modules/`uname -r` | grep snd -This command gives a large list XPS-15-9560:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80) Subsystem: Dell Device 07be Flags: bus master, fast devsel, latency 32, IRQ 17 Memory at ed128000 (64-bit, non-prefetchable) [size=16K] Memory at ed10 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Information you required in the bug report:** XPS-15-9560:~$ apt-cache policy pkgname alsa-base alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-164.192-generic 4.4.186 Uname: Linux 4.4.0-164-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vasko 2204 F...m pulseaudio /dev/snd/controlC0: vasko 2204 F pulseaudio CurrentDesktop: Unity Date: Sat Sep 21 22:05:15 2019 InstallationDate: Installed on 2018-10-15 (340 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0JHP5H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/26/2019:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-06T23:26:58.909811 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: Headphones not detected, low output volume(even when I put more then 100% volume), right speaker doesnt work. Here is output of some commands I was guided to post here, from troubleshoot instruction. https://help.ubuntu.com/community/SoundTroubleshooting XPS-15-9560:~$ sudo aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3266 Analog [ALC3266 Analog] - Subdevices: 0/1 - Subdevice #0: subdevice #0 + Subdevices: 0/1 + Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 find /lib/modules/`uname -r` | grep snd -This command gives a large list XPS-15-9560:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80) - Subsystem: Dell Device 07be - Flags: bus master, fast devsel, latency 32, IRQ 17 - Memory at ed128000 (64-bit, non-prefetchable) [size=16K] - Memory at ed10 (64-bit, non-prefetchable) [size=64K] - Capabilities: - Kernel driver in use: snd_hda_intel - Kernel modules: snd_hda_intel - + Subsystem: Dell Device 07be + Flags: bus master, fast devsel, latency 32, IRQ 17 + Memory at ed128000 (64-bit, non-prefetchable) [size=16K] + Memory at ed10 (64-bit, non-prefetchable) [size=64K] + Capabilities: + Kernel driver in use: snd_hda_intel + Kernel modules: snd_hda_intel Information you required in the bug report:** - XPS-15-9560:~$ lsb_release -rd - Description: Ubuntu 16.04.6 LTS - Release: 16.04 - XPS-15-9560:~$ apt-cache policy pkgname alsa-base alsa-base: - Installed: 1.0.25+dfsg-0ubuntu5 - Candidate: 1.0.25+dfsg-0ubuntu5 - Version table: - *** 1.0.25+dfsg-0ubuntu5 500
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
This bug was fixed in the package indicator-session - 17.3.20+19.10.20190921-0ubuntu1 --- indicator-session (17.3.20+19.10.20190921-0ubuntu1) eoan; urgency=medium [ Khurshid Alam ] * Port media keys to use com.canonical.unity.settings-daemon. LP: #1842324 (LP: #1842324) -- Sebastien Bacher Sat, 21 Sep 2019 10:59:04 + -- 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/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
This bug was fixed in the package unity-settings-daemon - 15.04.1+19.10.20190921-0ubuntu1 --- unity-settings-daemon (15.04.1+19.10.20190921-0ubuntu1) eoan; urgency=medium [ Khurshid Alam ] * Port media keys to use com.canonical.unity.settings-daemon (LP: #1842324) -- Sebastien Bacher Sat, 21 Sep 2019 10:59:14 + ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Fix Released ** Changed in: indicator-session (Ubuntu) Status: Confirmed => Fix Released -- 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/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
This bug was fixed in the package unity-greeter - 18.04.0+19.10.20190921-0ubuntu1 --- unity-greeter (18.04.0+19.10.20190921-0ubuntu1) eoan; urgency=medium [ Khurshid Alam ] * Port media keys to use com.canonical.unity.settings-daemon. LP: #1842324 (LP: #1842324) -- Sebastien Bacher Sat, 21 Sep 2019 10:59:35 + ** Changed in: unity-greeter (Ubuntu) Status: Confirmed => Fix Released -- 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/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844868] [NEW] cloud-images should not contain plymouth
Public bug reported: cloud-images should not contain plymouth ** Affects: cloud-images Importance: Undecided Status: New ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1844868 Title: cloud-images should not contain plymouth Status in cloud-images: New Status in ubuntu-meta package in Ubuntu: New Bug description: cloud-images should not contain plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1844868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
This bug was fixed in the package ubuntu-settings - 19.10.2 --- ubuntu-settings (19.10.2) eoan; urgency=medium [ Khurshid Alam ] * Remove screensaver override for unity Unity is now using it's own schema for media keys. See LP: #1842324 -- Sebastien Bacher Sat, 21 Sep 2019 13:19:29 +0200 ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Fix Released -- 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/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
Actually I confirm this on current ubuntu bionic. Would someone please reach the ubuntu security team and verify this is an intended choice? evilaliv3@evilaliv3:~$ hardening-check /usr/bin/python3 /usr/bin/python3: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: no, not found! hardening-check /usr/bin/python2 /usr/bin/python2: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in python2.7 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki /Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844860] [NEW] Freezing system
Public bug reported: The system getting frozen suddenly, no-longer peripheral material access (keyb, mouse etc..). Seems correlated with theFirefox navigator use. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Sep 21 13:08:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] [1025:0394] InstallationDate: Installed on 2019-08-03 (48 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: eMachines EL1358 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.name: EL1358 dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr: dmi.product.family: eMachines Desktop dmi.product.name: EL1358 dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: eMachines version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** 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/1844860 Title: Freezing system Status in xorg package in Ubuntu: New Bug description: The system getting frozen suddenly, no-longer peripheral material access (keyb, mouse etc..). Seems correlated with theFirefox navigator use. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Sep 21 13:08:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] [1025:0394] InstallationDate: Installed on 2019-08-03 (48 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: eMachines EL1358 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.name: EL1358 dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr: dmi.product.family: eMachines Desktop dmi.product.name: EL1358 dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: eMachines version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
@Tyler, @Jamie: When reviewing the proposal in comment #37, Sebastien pointed at a possible need to also change /etc/apparmor.d/abstractions/ibus. Can you please consider that? Also, in Ubuntu 17.10 - 19.04 the im-config change of the abstract socket path has not been effective in Ubuntu, since we have let GDM start ibus. Which implications, if any, has that had? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: In Progress Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor
[Touch-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
This happened to me while adding a google account to the online accounts service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server: Fix Released Status in evolution-data-server package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/evolution/issues/616 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f36355653ae) ok source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=32) at malloc.c:3051 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
** Tags added: regression-update ** Changed in: ibus (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus package in Ubuntu: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
This bug was fixed in the package xkeyboard-config - 2.26-2ubuntu2 --- xkeyboard-config (2.26-2ubuntu2) eoan; urgency=medium [ Viktor Kovács ] * debian/patches/git-update-old-hungarian.diff: - Upstream commit which addresses some issues with the Old Hungarian layout (LP: #1840699). -- Gunnar Hjalmarsson Tue, 20 Aug 2019 15:38:00 +0200 ** Changed in: xkeyboard-config (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 xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus package in Ubuntu: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
** Changed in: xkeyboard-config (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 xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843755] Re: [FFe] Please accept systemd 243 to Eoan
The 243 package is prepared in https://bileto.ubuntu.com/#/ticket/3801. According to Steve's out of band approval I'll upload that when every test passes. ** Summary changed: - [FFe] Please accept systemd 242 to Eoan + [FFe] Please accept systemd 243 to Eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1843755 Title: [FFe] Please accept systemd 243 to Eoan Status in systemd package in Ubuntu: Confirmed Bug description: Eoan currently has 241-7ubuntu1, Debian stable has 241 and Debian testing moved to 242 last week. While version 241 is the safer choice for Eoan (from v241 and v242) since it is widely tested updating to v242 will allow us to carry fewer patches in Eoan and makes moving to the next release easier. The proposed package is tested in Bileto and all tests are passing (except for a few unrelated failures): https://bileto.ubuntu.com/#/ticket/3797 The final version will be 242-6ubuntu1 and I'm tidying up the changelog, too. I plan merging 242-7, too, going forward but this will not need an FFe. CHANGES WITH 242: * In .link files, MACAddressPolicy=persistent (the default) is changed to cover more devices. For devices like bridges, tun, tap, bond, and similar interfaces that do not have other identifying information, the interface name is used as the basis for persistent seed for MAC and IPv4LL addresses. The way that devices that were handled previously is not changed, and this change is about covering more devices then previously by the "persistent" policy. MACAddressPolicy=random may be used to force randomized MACs and IPv4LL addresses for a device if desired. Hint: the log output from udev (at debug level) was enhanced to clarify what policy is followed and which attributes are used. `SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link /sys/class/net/` may be used to view this. Hint: if a bridge interface is created without any slaves, and gains a slave later, then now the bridge does not inherit slave's MAC. To inherit slave's MAC, for example, create the following file: ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ``` * The .device units generated by systemd-fstab-generator and other generators do not automatically pull in the corresponding .mount unit as a Wants= dependency. This means that simply plugging in the device will not cause the mount unit to be started automatically. But please note that the mount unit may be started for other reasons, in particular if it is part of local-fs.target, and any unit which (transitively) depends on local-fs.target is started. * networkctl list/status/lldp now accept globbing wildcards for network interface names to match against all existing interfaces. * The $PIDFILE environment variable is set to point the absolute path configured with PIDFile= for processes of that service. * The fallback DNS server list was augmented with Cloudflare public DNS servers. Use `-Ddns-servers=` to set a different fallback. * A new special target usb-gadget.target will be started automatically when a USB Device Controller is detected (which means that the system is a USB peripheral). * A new unit setting CPUQuotaPeriodSec= assigns the time period relatively to which the CPU time quota specified by CPUQuota= is measured. * A new unit setting ProtectHostname= may be used to prevent services from modifying hostname information (even if they otherwise would have privileges to do so). * A new unit setting NetworkNamespacePath= may be used to specify a namespace for service or socket units through a path referring to a Linux network namespace pseudo-file. * The PrivateNetwork= setting and JoinsNamespaceOf= dependencies now have an effect on .socket units: when used the listening socket is created within the configured network namespace instead of the host namespace. * ExecStart= command lines in unit files may now be prefixed with ':' in which case environment variable substitution is disabled. (Supported for the other ExecXYZ= settings, too.) * .timer units gained two new boolean settings OnClockChange= and OnTimezoneChange= which may be used to also trigger a unit when the
[Touch-packages] [Bug 1844853] [NEW] IBus no longer works in Qt applications after upgrade
Public bug reported: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus package in Ubuntu: New Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
