[Touch-packages] [Bug 1808275] Re: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all
Does rebooting successfully restore sound? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Summary changed: - [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all + [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped -- 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/1808275 Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped Status in pulseaudio package in Ubuntu: Incomplete Bug description: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808275/+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
I got an error when building the modules from @VanVan's github due to /sound/pci/hda_codec.h having been moved to /include/sound/hda_codec.h Fixing this let the compile finish without error (this is on Fedora 29). -- 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: Confirmed 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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
i also got errors when trying to follow that ubuntu guide for compiling your own kernel. -- 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: Confirmed 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 1808275] [NEW] [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all
Public bug reported: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1808275 Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808275/+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 1808264] Re: caldav free-busy query is broken
Whoops, misinterpreted the version numbering scheme and accidentally submitted a patch numbered for 18.04.2! ** Patch added: "Patch with correct version number" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+attachment/5221828/+files/2-3.28.5-0ubuntu1.18.04.1.debdiff -- 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/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+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 1808264] Re: caldav free-busy query is broken
** Patch added: "Patch for this issue" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+attachment/5221827/+files/1-3.28.5-0ubuntu0.18.04.2.debdiff -- 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/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+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 1808264] Re: caldav free-busy query is broken
I have added a patch which applies both upstream merge requests linked above. I was not above to successfully set up pbuilder, but built and tested it successfully with debuild in a bionic VM. Subscribing ubuntu- sru in accordance with http://packaging.ubuntu.com/html/security-and- stable-release-updates.html as I'm pretty sure the change I'm requesting would be a stable release update. Aiming justify that update: this is a significant regression because somewhere between Xenial and Bionic, this caldav freebusy code was rewritten and broken. Additionally somewhere in that timeframe the behavior changed from using the address book's FBURL to using this caldav-based technique (which, again, doesn't work :) -- 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/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+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 41159] Re: timezone data is duplicated over at least three packages in main
I wonder if we should change the packaging of tzdata to always build the stuff that icu needs/wants. Such that an update of tzdata ripples through to icu as well. Somehow. -- 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/41159 Title: timezone data is duplicated over at least three packages in main Status in evolution-data-server package in Ubuntu: Fix Released Status in gcj-4.1 package in Ubuntu: Fix Released Status in icu package in Ubuntu: Confirmed Status in postgresql-8.2 package in Ubuntu: Fix Released Status in python-tz package in Ubuntu: Fix Released Status in icu package in Debian: New Bug description: timezone data is duplicated over at least three packages in main, these are: - belocs-locales - icu - python-tz probably not something to solve before dapper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/41159/+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 1745866] Re: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on
See also bug 1707611. -- 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/1745866 Title: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.14.0-15-generic. AplayDevices: aplay: device_list:270: no soundcards found... ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 ArecordDevices: arecord: device_list:270: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-25 (36 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171222) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: bionic third-party-packages Uname: Linux 4.14.0-15-generic x86_64 UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H67M-GE/HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1711101, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1711101 Audio doesn't auto switch away from HDMI after unplugging HDMI -- 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/1802350 Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: On a fresh install of ubutu 18.04 all sound work (youtube and system sounds) I connected external hdmi monitor with speakers. I switched audio output to hdmi in settings Then all audio was channeled to external monitor speakers (youtube and system sounds) Then I disconnected external monitor and did not touch the audio output Now only system sounds are working. Youtube in chrome does not work. Audio settings says internal speakers. Firefox youtube has audio normally After reboot same issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 1412 F pulseaudio /dev/snd/controlC1: ed 1412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:28:37 2018 InstallationDate: Installed on 2018-11-01 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.family: 00 dmi.product.name: Inspiron 5547 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1808183] Re: server console output extremely slow after upgrade to 18.04
Please: 1. Clarify what is meant to be visible on your server console. Are you using Gnome Shell, just text mode, or something else? 2. Run 'lspci -k > lspcik.txt' on the machine and send us the 'lspcik.txt' file 3. Install package 'mesa-utils' and then run 'glxinfo > glxinfo.txt' on the machine and send us the file 'glxinfo.txt'. 4. Run 'dmesg > dmesg.txt' on the machine and send us the 'dmesg.txt' file. 5. Run 'journalctl > journal.txt' on the machine and send us the file 'journal.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: server console output extremely slow after upgrade to 18.04 Status in Ubuntu: Incomplete Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808183/+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 1808264] [NEW] caldav free-busy query is broken
Public bug reported: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-data-server (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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+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 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] - # cd /root + # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test - root-bind\x2dtest-abc.mount loaded inactive dead /root/bind-test/abc - root-bind\x2dtest.mount loaded active mounted /root/bind-test + tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc + tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : - # cd /root + # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test - root-bind\x2dtest.mount loaded active mounted /root/bind-test + tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. [Other Info] One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. It only affect systemd for Xenial, later release already has the fix: $ git describe --contains 65d36b495 v237~140 ==> systemd | 229-4ubuntu21.4 | xenial-updates systemd | 237-3ubuntu10.3 | bionic-updates systemd | 239-7ubuntu9 | cosmic [Original Description] From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 -- 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/1795764 Title: systemd: core: Fix edge case when processing /proc/self/mountinfo Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when
[Touch-packages] [Bug 1808251] Re: systemctl disable fails to clean up override
No applicable logs ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1808251 Title: systemctl disable fails to clean up override Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808251/+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 41159] Re: timezone data is duplicated over at least three packages in main
** Changed in: icu (Debian) Status: Unknown => New -- 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/41159 Title: timezone data is duplicated over at least three packages in main Status in evolution-data-server package in Ubuntu: Fix Released Status in gcj-4.1 package in Ubuntu: Fix Released Status in icu package in Ubuntu: Confirmed Status in postgresql-8.2 package in Ubuntu: Fix Released Status in python-tz package in Ubuntu: Fix Released Status in icu package in Debian: New Bug description: timezone data is duplicated over at least three packages in main, these are: - belocs-locales - icu - python-tz probably not something to solve before dapper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/41159/+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 1808251] [NEW] systemctl disable fails to clean up override
You have been subscribed to a public bug: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed -- systemctl disable fails to clean up override https://bugs.launchpad.net/bugs/1808251 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@z80-ben Yes, you are right, UX931UA is not part of the list, it could have worked :/ Be sure that you have no configuration error on /etc/modprobe.d/alsa-base.conf Tested on Asus UX333, UX433, UX533 with ALC294 Support for Asus G751, P5440FF, X430UN, D640SA, UX550GE, X705FD; X430UN, GL503VM, Q524UQK, X542UN with ALC256 and some others. A lot of Acer computers too and some other brands. @klintfr It depends on your Linux distribution -- 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: Confirmed 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 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed
This bug was fixed in the package software-properties - 0.96.29 --- software-properties (0.96.29) disco; urgency=medium * SoftwarePropertiesGtk.py: when checking a package's depends for DKMS also pass on an AttributeError (LP: #1807373) -- Brian Murray Tue, 11 Dec 2018 14:35:40 -0800 ** Changed in: software-properties (Ubuntu) Status: In Progress => 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/1807373 Title: /usr/bin/software-properties- gtk:AttributeError:on_driver_selection_changed Status in software-properties package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 1.92.36bodhi1, the problem page at https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1807373/+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 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
** Changed in: ufw Status: In Progress => Fix Committed -- 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/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: Fix Committed Status in ufw package in Ubuntu: Confirmed Status in ufw package in Debian: New Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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
I've compiled 4.20-rc6 from VanVan's github repository, and it has no effect on my UX391UA - still no sound. I notice the patch doesn't actually refer specifically to the UX931UA though, only other ASUS models. -- 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: Confirmed 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 1808060] Re: libmirclient causes multiarch SDL2 headers to conflict with each other
That's good to hear and would be very useful! :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1808060 Title: libmirclient causes multiarch SDL2 headers to conflict with each other Status in mir package in Ubuntu: Triaged Bug description: libmirclient-dev makes impossible to install both libsdl2-dev and libsdl2-dev:i386 which is essential for anyone building game related software. Seeing mir not being used at all in any of the official Ubuntu flavors, I find it strange that it was considered an acceptable solution to break a common and important workflow in favor of an experimental display server. It's probably a minor packaging bug anyway, multi-arch development headers usually don't conflict with each other. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libmirclient-dev 0.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 14:25:50 2018 SourcePackage: mir UpgradeStatus: Upgraded to cosmic on 2018-11-02 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1808060/+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
@VanVan (w-o) Thank you for your message. But I keep failing, trying to understand any "compile & build kernel" tutorials. I don't get it , how it works... I got your patched kernel and ran the sudo apt-get [...] Then, i really don't know what to do , what part of the tutorial I have to do ... :( I'm the rookiest rookie in the eternal rookiness -- 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: Confirmed 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 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
** Changed in: icu (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: New Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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 1808095] Re: uniq is not checking and handling all file types
** Description changed: Hi, The utility uniq allows all types of files as input. Allowing block devices or character devices as input can lead to unwanted behavior such as the utility executes indefinitely when device '/dev/urandom' is passed as an input. Please refer this for more information regarding this issue (https://github.com/pkmoore/rrapper/blob/master/anomalies/weird_filetypes.md). I've included a patch which checks and handles character devices and - block devices when passed as input. Please get back to me for more - information. + block devices when passed as input. I've tested the patched version and + it doesn't seem to break any tests but I'm always glad to further work + on it. Please get back to me with any feedback or for more information. Regards, Anoop Nadig ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 11 20:23:32 2018 ExecutablePath: /usr/bin/uniq InstallationDate: Installed on 2018-11-07 (35 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1808095 Title: uniq is not checking and handling all file types Status in coreutils package in Ubuntu: New Bug description: Hi, The utility uniq allows all types of files as input. Allowing block devices or character devices as input can lead to unwanted behavior such as the utility executes indefinitely when device '/dev/urandom' is passed as an input. Please refer this for more information regarding this issue (https://github.com/pkmoore/rrapper/blob/master/anomalies/weird_filetypes.md). I've included a patch which checks and handles character devices and block devices when passed as input. I've tested the patched version and it doesn't seem to break any tests but I'm always glad to further work on it. Please get back to me with any feedback or for more information. Regards, Anoop Nadig ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 11 20:23:32 2018 ExecutablePath: /usr/bin/uniq InstallationDate: Installed on 2018-11-07 (35 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1808095/+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 1808239] [NEW] package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: Está aparecendo mensagem de erro! ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python2.7 2.7.15~rc1-1ubuntu0.1 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 Date: Wed Dec 12 13:58:54 2018 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2018-12-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: python2.7 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (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 python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1808239 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in python2.7 package in Ubuntu: New Bug description: Está aparecendo mensagem de erro! ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python2.7 2.7.15~rc1-1ubuntu0.1 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 Date: Wed Dec 12 13:58:54 2018 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2018-12-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: python2.7 Title: package python2.7 2.7.15~rc1-1ubuntu0.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808239/+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 1589487] Re: libicu52 not present
libicu52 is and old version of the package and is not needed by any software that is in Ubuntu 16.04. Therefore it won't be added. ** Changed in: icu (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1589487 Title: libicu52 not present Status in icu package in Ubuntu: Invalid Bug description: Hi, libicu52 is not installable but some applications needs it. Command 1300 of 8 #apt-get install libicu52 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libicu52 Please can you add to Xenial standard repository the libicu52 library? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1589487/+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 41159] Re: timezone data is duplicated over at least three packages in main
** Bug watch added: Debian Bug tracker #863213 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863213 ** Also affects: icu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863213 Importance: Unknown Status: Unknown -- 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/41159 Title: timezone data is duplicated over at least three packages in main Status in evolution-data-server package in Ubuntu: Fix Released Status in gcj-4.1 package in Ubuntu: Fix Released Status in icu package in Ubuntu: Confirmed Status in postgresql-8.2 package in Ubuntu: Fix Released Status in python-tz package in Ubuntu: Fix Released Status in icu package in Debian: Unknown Bug description: timezone data is duplicated over at least three packages in main, these are: - belocs-locales - icu - python-tz probably not something to solve before dapper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/41159/+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 1795651] Re: ICU data package is grossly outdated
** Bug watch added: Debian Bug tracker #822631 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822631 ** Also affects: icu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822631 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Status in icu package in Debian: Unknown Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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 1641326] Re: package libicu-dev 55.1-7 failed to install/upgrade: libicu-dev:amd64 57.1-4 (Multi-Arch: no) is not co-installable with libicu-dev which has multiple installed inst
*** This bug is a duplicate of bug 1784135 *** https://bugs.launchpad.net/bugs/1784135 ** This bug has been marked a duplicate of bug 1784135 libicu-dev and libicu-dev:i386 conflict with each other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1641326 Title: package libicu-dev 55.1-7 failed to install/upgrade: libicu-dev:amd64 57.1-4 (Multi-Arch: no) is not co-installable with libicu-dev which has multiple installed instances Status in icu package in Ubuntu: New Bug description: I was update ubuntu and automatically don't install this library. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libicu-dev 55.1-7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 11 19:42:46 2016 DuplicateSignature: package:libicu-dev:55.1-7 Unpacking libxml2:i386 (2.9.4+dfsg1-2) over (2.9.3+dfsg1-1ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-sxBQc9/13-libicu-dev_57.1-4_amd64.deb (--unpack): libicu-dev:amd64 57.1-4 (Multi-Arch: no) is not co-installable with libicu-dev which has multiple installed instances ErrorMessage: libicu-dev:amd64 57.1-4 (Multi-Arch: no) is not co-installable with libicu-dev which has multiple installed instances InstallationDate: Installed on 2016-01-24 (292 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: icu Title: package libicu-dev 55.1-7 failed to install/upgrade: libicu-dev:amd64 57.1-4 (Multi-Arch: no) is not co-installable with libicu-dev which has multiple installed instances UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1641326/+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] [NEW] Update gtk to 3.24.2
Public bug reported: 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.2 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. 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. Other Info == One of the bigger changes in the git commit history were theming changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Status: Triaged ** Tags: cosmic ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Triaged -- 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.2 Status in gtk+3.0 package in Ubuntu: Triaged 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.2 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. 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. Other Info == One of the bigger changes in the git commit history were theming changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3. Ubuntu 18.10 uses the Yaru theme as default instead.). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. 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 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: icu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: Unknown Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
** Tags added: amd64 bionic i386 multiarch ** Bug watch added: Debian Bug tracker #898820 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898820 ** Also affects: icu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898820 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: Unknown Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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 1808216] Re: Cannot install amd64 and i386 versions of libicu-dev in parallel (on x86-64/bionic)
*** This bug is a duplicate of bug 1784135 *** https://bugs.launchpad.net/bugs/1784135 It seems that this is already reported, marking as duplicate. ** This bug has been marked a duplicate of bug 1784135 libicu-dev and libicu-dev:i386 conflict with each other -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1808216 Title: Cannot install amd64 and i386 versions of libicu-dev in parallel (on x86-64/bionic) Status in icu package in Ubuntu: New Bug description: On an x86-64 machine with Ubuntu 18.04, I've tried to install both 64 and 32 bit versions of libicu-dev (because I wanted to build both 32 and 64 bit versions of an app using that lib). Unfortunately, when I install the 64 bit version of the package then the 32 bit variant gets removed, and when I install the 32 bit variant then the 64 bit version gets removed. Some (slightly sanitized) console logs: $ cat /etc/issue.net Ubuntu 18.04.1 LTS $ uname -mrs Linux 4.15.0-38-generic x86_64 $ apt show libicu-dev Package: libicu-dev Version: 60.2-3ubuntu3 $ sudo apt install libicu-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libharfbuzz-dev:i386 libicu-le-hb-dev:i386 Suggested packages: icu-doc:i386 The following packages will be REMOVED: libharfbuzz-dev libicu-dev libicu-le-hb-dev The following NEW packages will be installed: libharfbuzz-dev:i386 libicu-dev:i386 libicu-le-hb-dev:i386 0 upgraded, 3 newly installed, 3 to remove and 0 not upgraded. Interestingly, on a Ubuntu 14.04.5 LTS (actually, on Travis CI), such a conflict does not happen. sudo apt-get install -y libicu-dev sudo apt-get install -y libicu-dev:i386 These two work just fine, the latter does not remove the former. The version there is libicu-dev 52.1-3ubuntu0.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1808216/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Thanx Colin. Anyway anyone knows why this bug is sooo hard to fix? It is old, and quite blocking someones workflow. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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
** Description changed: 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 - The fix for this was pushed to the stable gtk-3-24 branch. + 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. -- 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 Committed Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress 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. 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 1804568] Re: click position is flipped to cursor position when in tent mode
** Package changed: coreutils (Ubuntu) => x11-xserver-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: click position is flipped to cursor position when in tent mode Status in x11-xserver-utils package in Ubuntu: New Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1804568/+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
** Description changed: 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 - The fix for this was pushed to the stable gtk-3-24 branch. + 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://gitlab.gnome.org/GNOME/gtk/commit/dbbc7b3859f4b https://gitlab.gnome.org/GNOME/gtk/issues/1398 ** Description changed: 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. + 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 ** Description changed: 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 + 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 -- 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 Committed Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress 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 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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
The fix seems good to me! My verification steps: - I verified that I could still reproduce the issues in the first post here, in a stock Ubuntu 18.04.1 installation in a VM (all package at their "freshly installed" version, including Firefox). - In doing this, I tested both scenarios from the original comment here -- (1) the BitWarden extension and (2) "old" reddit ( https://old.reddit.com/r/firefox/ -- note that a slightly different URL is now needed to get the page that I was referencing in the original report here.) - Then, I installed these 2 packages: https://launchpad.net/ubuntu/+source/gnome-shell/3.28.3-0ubuntu0.18.04.4/+build/15764981/+files/gnome-shell-common_3.28.3-0ubuntu0.18.04.4_all.deb https://launchpad.net/ubuntu/+source/gnome-shell/3.28.3-0ubuntu0.18.04.4/+build/15764981/+files/gnome-shell_3.28.3-0ubuntu0.18.04.4_amd64.deb ...and ran "sudo apt --fix-broken install" to get a mutter update that gnome-shell required, and I rebooted, and retested BitWarden and "old reddit", and they were fixed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Hello Trent, or anyone else affected, Accepted cups into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.2.8-5ubuntu1.2 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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. ** Changed in: cups (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: cups (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1804576] Please test proposed package
Hello Trent, or anyone else affected, Accepted cups into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.7 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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. -- 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/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1804576] Please test proposed package
Hello Trent, or anyone else affected, Accepted cups into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.2.7-1ubuntu2.3 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. ** Changed in: cups (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
It has only been marked Won't Fix in Yakkety, because Yakkety is well past it's sell by date. It is still open on Xenial. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids
** Also affects: alsa-lib (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-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806660 Title: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids Status in Linux: Confirmed Status in alsa-lib package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Hello, The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids. In the upper part of gnome-shell it appears that they are with the headphones, and it is not like that. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2784 F pulseaudio /dev/snd/pcmC0D0p: caravena 2784 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 07:59:27 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806660/+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 1808216] [NEW] Cannot install amd64 and i386 versions of libicu-dev in parallel (on x86-64/bionic)
Public bug reported: On an x86-64 machine with Ubuntu 18.04, I've tried to install both 64 and 32 bit versions of libicu-dev (because I wanted to build both 32 and 64 bit versions of an app using that lib). Unfortunately, when I install the 64 bit version of the package then the 32 bit variant gets removed, and when I install the 32 bit variant then the 64 bit version gets removed. Some (slightly sanitized) console logs: $ cat /etc/issue.net Ubuntu 18.04.1 LTS $ uname -mrs Linux 4.15.0-38-generic x86_64 $ apt show libicu-dev Package: libicu-dev Version: 60.2-3ubuntu3 $ sudo apt install libicu-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libharfbuzz-dev:i386 libicu-le-hb-dev:i386 Suggested packages: icu-doc:i386 The following packages will be REMOVED: libharfbuzz-dev libicu-dev libicu-le-hb-dev The following NEW packages will be installed: libharfbuzz-dev:i386 libicu-dev:i386 libicu-le-hb-dev:i386 0 upgraded, 3 newly installed, 3 to remove and 0 not upgraded. Interestingly, on a Ubuntu 14.04.5 LTS (actually, on Travis CI), such a conflict does not happen. sudo apt-get install -y libicu-dev sudo apt-get install -y libicu-dev:i386 These two work just fine, the latter does not remove the former. The version there is libicu-dev 52.1-3ubuntu0.8. ** Affects: icu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1808216 Title: Cannot install amd64 and i386 versions of libicu-dev in parallel (on x86-64/bionic) Status in icu package in Ubuntu: New Bug description: On an x86-64 machine with Ubuntu 18.04, I've tried to install both 64 and 32 bit versions of libicu-dev (because I wanted to build both 32 and 64 bit versions of an app using that lib). Unfortunately, when I install the 64 bit version of the package then the 32 bit variant gets removed, and when I install the 32 bit variant then the 64 bit version gets removed. Some (slightly sanitized) console logs: $ cat /etc/issue.net Ubuntu 18.04.1 LTS $ uname -mrs Linux 4.15.0-38-generic x86_64 $ apt show libicu-dev Package: libicu-dev Version: 60.2-3ubuntu3 $ sudo apt install libicu-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libharfbuzz-dev:i386 libicu-le-hb-dev:i386 Suggested packages: icu-doc:i386 The following packages will be REMOVED: libharfbuzz-dev libicu-dev libicu-le-hb-dev The following NEW packages will be installed: libharfbuzz-dev:i386 libicu-dev:i386 libicu-le-hb-dev:i386 0 upgraded, 3 newly installed, 3 to remove and 0 not upgraded. Interestingly, on a Ubuntu 14.04.5 LTS (actually, on Travis CI), such a conflict does not happen. sudo apt-get install -y libicu-dev sudo apt-get install -y libicu-dev:i386 These two work just fine, the latter does not remove the former. The version there is libicu-dev 52.1-3ubuntu0.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1808216/+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
** Changed in: gtk+3.0 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1798861 Title: Tooltips flicker constantly in GTK3 applications Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 package in Debian: Confirmed 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 1808109] Re: Upgrade to 1.12
Looks like some additional patches have been added to the package in Ubuntu (https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/1.11.1-1ubuntu4), so this might need a merge. ** Tags added: needs-debian-merge upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808109 Title: Upgrade to 1.12 Status in gpgme1.0 package in Ubuntu: New Bug description: GPGme 1.12 was release with a new json help that allows browsers to use gpgme for encryption (see https://www.mailvelope.com/de/blog/mailvelope-3.0 for example). Debian (buster) already includes 1.12 and so should Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1808109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808092] Re: Checking and handling various filetypes in fmt
** Changed in: coreutils (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1808092 Title: Checking and handling various filetypes in fmt Status in coreutils package in Ubuntu: New Bug description: fmt doesn't check filetypes of the input arguments passed to it, it just opens the file and reads from it without checking its st_mode. It only throws an error if the file doesn't exist and can't handle the following filetypes - S_IFCHR, S_IFBLK and S_IFBLK. Passing a file from any of these types will possibly hang or crash the application. For more reference, please visit the below link- (https://github.com/pkmoore/rrapper/blob/master/anomalies/weird_filetypes.md) I have attached a patch that checks for the above mentioned filetypes and handles them accordingly. Please let me know if you have any questions or suggestions regarding this, will be happy to answer them. Thank you Snahil Singh ss11...@nyu.edu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 11 20:01:58 2018 ExecutablePath: /usr/bin/fmt InstallationDate: Installed on 2018-11-07 (35 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1808092/+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 1808095] Re: uniq is not checking and handling all file types
** Changed in: coreutils (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1808095 Title: uniq is not checking and handling all file types Status in coreutils package in Ubuntu: New Bug description: Hi, The utility uniq allows all types of files as input. Allowing block devices or character devices as input can lead to unwanted behavior such as the utility executes indefinitely when device '/dev/urandom' is passed as an input. Please refer this for more information regarding this issue (https://github.com/pkmoore/rrapper/blob/master/anomalies/weird_filetypes.md). I've included a patch which checks and handles character devices and block devices when passed as input. Please get back to me for more information. Regards, Anoop Nadig ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 11 20:23:32 2018 ExecutablePath: /usr/bin/uniq InstallationDate: Installed on 2018-11-07 (35 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1808095/+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 1807797] Re: Split doesn't check for filetype
** Patch added: "Patch for split r-chunk unit test" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+attachment/5221710/+files/split_r_chunk_test.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1807797 Title: Split doesn't check for filetype Status in coreutils package in Ubuntu: New Bug description: Hello! I noticed that Split doesn't check for filetypes before it starts splitting the file. As a result, it's possible to eat up CPU and Disk memory by passing in a character device as input. I wanted to make Split more robust by adding a patch to check for file type. This patch do break some of the tests for Split. The tests that are checking Split's ability to "elide empty files" by using /dev/null as input fail with this patch, since /dev/null is a character device. I would love to modify those tests to use a regular empty file, upon the approval of this patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+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 1807797] Re: Split doesn't check for filetype
** Patch added: "Patch for split b-chunk unit test" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+attachment/5221711/+files/split_b_chunk_test.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1807797 Title: Split doesn't check for filetype Status in coreutils package in Ubuntu: New Bug description: Hello! I noticed that Split doesn't check for filetypes before it starts splitting the file. As a result, it's possible to eat up CPU and Disk memory by passing in a character device as input. I wanted to make Split more robust by adding a patch to check for file type. This patch do break some of the tests for Split. The tests that are checking Split's ability to "elide empty files" by using /dev/null as input fail with this patch, since /dev/null is a character device. I would love to modify those tests to use a regular empty file, upon the approval of this patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+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 1807797] Re: Split doesn't check for filetype
Hello, Following up on the patch: I had a chance to fix the unit tests as well. I'm attaching the patches to the next four comments. Thanks, Maliat ** Patch added: "Patch for split filter unit test" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+attachment/5221708/+files/split_filter_test.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1807797 Title: Split doesn't check for filetype Status in coreutils package in Ubuntu: New Bug description: Hello! I noticed that Split doesn't check for filetypes before it starts splitting the file. As a result, it's possible to eat up CPU and Disk memory by passing in a character device as input. I wanted to make Split more robust by adding a patch to check for file type. This patch do break some of the tests for Split. The tests that are checking Split's ability to "elide empty files" by using /dev/null as input fail with this patch, since /dev/null is a character device. I would love to modify those tests to use a regular empty file, upon the approval of this patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+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 1807797] Re: Split doesn't check for filetype
** Patch added: "Patch for split l-chunk unit test" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+attachment/5221709/+files/split_l_chunk_test.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1807797 Title: Split doesn't check for filetype Status in coreutils package in Ubuntu: New Bug description: Hello! I noticed that Split doesn't check for filetypes before it starts splitting the file. As a result, it's possible to eat up CPU and Disk memory by passing in a character device as input. I wanted to make Split more robust by adding a patch to check for file type. This patch do break some of the tests for Split. The tests that are checking Split's ability to "elide empty files" by using /dev/null as input fail with this patch, since /dev/null is a character device. I would love to modify those tests to use a regular empty file, upon the approval of this patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1807797/+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 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I have no problem with pcscd on Ubuntu 16.04 LTS: $ sudo LANG=C apt install pcscd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libccid The following NEW packages will be installed: libccid pcscd 0 upgraded, 2 newly installed, 0 to remove and 8 not upgraded. Need to get 141 kB of archives. After this operation, 469 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 libccid amd64 1.4.22-1ubuntu0.1 [85.8 kB] Get:2 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 pcscd amd64 1.8.14-1ubuntu1.16.04.1 [55.7 kB] Fetched 141 kB in 0s (1006 kB/s) Selecting previously unselected package libccid. (Reading database ... 223096 files and directories currently installed.) Preparing to unpack .../libccid_1.4.22-1ubuntu0.1_amd64.deb ... Unpacking libccid (1.4.22-1ubuntu0.1) ... Selecting previously unselected package pcscd. Preparing to unpack .../pcscd_1.8.14-1ubuntu1.16.04.1_amd64.deb ... Unpacking pcscd (1.8.14-1ubuntu1.16.04.1) ... Processing triggers for systemd (229-4ubuntu21.10) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up libccid (1.4.22-1ubuntu0.1) ... Setting up pcscd (1.8.14-1ubuntu1.16.04.1) ... Processing triggers for systemd (229-4ubuntu21.10) ... Processing triggers for ureadahead (0.100.0-19) ... And also no problem on Ubuntu 18.04 LTS. $ sudo LANG=C apt install pcscd [sudo] Mot de passe de rousseau : Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: pcscd 0 upgraded, 1 newly installed, 0 to remove and 19 not upgraded. Need to get 57.9 kB of archives. After this operation, 176 kB of additional disk space will be used. Get:1 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 pcscd amd64 1.8.23-1 [57.9 kB] Fetched 57.9 kB in 0s (651 kB/s) Selecting previously unselected package pcscd. (Reading database ... 172785 files and directories currently installed.) Preparing to unpack .../pcscd_1.8.23-1_amd64.deb ... Unpacking pcscd (1.8.23-1) ... Setting up pcscd (1.8.23-1) ... Created symlink /etc/systemd/system/sockets.target.wants/pcscd.socket -> /lib/systemd/system/pcscd.socket. Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.9) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... I do not plan to fix a bug in Ubuntu 14.04 only. Ubuntu 14.04 should be UN-maintained after April 2019 (in 4 months). https://www.ubuntu.com/about/release-cycle The best solution may be to upgrade your system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1700104 Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pcsc-lite package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: pcscd 1.8.10-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.24 AptOrdering: pcscd: Install pcscd: Configure Architecture: amd64 Date: Fri Jun 23 12:21:31 2017 DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-28 (177 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: pcsc-lite Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+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 837557] Re: fraudulent DigiNotar certificate issuance
Nora Blob: those are blacklist entries. See details at https://security.stackexchange.com/questions/174474/why-is-diginotar-ca- still-in-my-mozilla-firefox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/837557 Title: fraudulent DigiNotar certificate issuance Status in ca-certificates package in Ubuntu: Fix Released Status in chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Fix Released Status in nss package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in seamonkey package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Released Status in xulrunner-1.9.2 package in Ubuntu: Invalid Status in ca-certificates source package in Lucid: Fix Released Status in chromium-browser source package in Lucid: Fix Released Status in firefox source package in Lucid: Fix Released Status in nss source package in Lucid: Fix Released Status in qt4-x11 source package in Lucid: Fix Released Status in seamonkey source package in Lucid: Won't Fix Status in thunderbird source package in Lucid: Fix Released Status in xulrunner-1.9.2 source package in Lucid: Fix Released Status in ca-certificates source package in Maverick: Fix Released Status in chromium-browser source package in Maverick: Fix Released Status in firefox source package in Maverick: Fix Released Status in nss source package in Maverick: Fix Released Status in qt4-x11 source package in Maverick: Fix Released Status in seamonkey source package in Maverick: Won't Fix Status in thunderbird source package in Maverick: Fix Released Status in xulrunner-1.9.2 source package in Maverick: Fix Released Status in ca-certificates source package in Natty: Fix Released Status in chromium-browser source package in Natty: Fix Released Status in firefox source package in Natty: Fix Released Status in nss source package in Natty: Fix Released Status in qt4-x11 source package in Natty: Fix Released Status in seamonkey source package in Natty: Won't Fix Status in thunderbird source package in Natty: Fix Released Status in xulrunner-1.9.2 source package in Natty: Fix Released Status in ca-certificates source package in Oneiric: Fix Released Status in chromium-browser source package in Oneiric: Fix Released Status in firefox source package in Oneiric: Fix Released Status in nss source package in Oneiric: Fix Released Status in qt4-x11 source package in Oneiric: Fix Released Status in seamonkey source package in Oneiric: Won't Fix Status in thunderbird source package in Oneiric: Fix Released Status in xulrunner-1.9.2 source package in Oneiric: Invalid Status in ca-certificates package in Debian: Fix Released Bug description: USN Information: This is being tracked in USN-1197-* NOTE: The Firefox update causes a regression for certain Dutch sites which is being tracked in Bug #838322. NOTE #2: The current update for Thunderbird still shows the DigiNotar Root CA as trusted in the certificate manager. This is due to Thunderbird using the system version of NSS. In this initial update, Thunderbird will actively distrust any certificate signed by the DigiNotar Root CA. Future updates will properly show the root CA as distrusted in the certificate manager. WORKAROUND (from blog post): http://support.mozilla.com/en-US/kb/deleting-diginotar-ca-cert - http://blog.mozilla.com/security/2011/08/29/fraudulent-google-com- certificate/ Qt 4.7 blog post: http://labs.qt.nokia.com/2011/09/07/what-the- diginotar-security-breach-means-for-qt-users-continued/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/837557/+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 1808183] [NEW] server console output extremely slow after upgrade to 18.04
Public bug reported: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance -- 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/1808183 Title: server console output extremely slow after upgrade to 18.04 Status in xorg package in Ubuntu: New Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1808183/+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 1332623] Re: Thunar behaves inconsistently with USB flash drive FAT32 partitions
This bug persists in Ubuntu 18.04 with Thunar 1.6.15
It is explained in more detail at: https://forum.xfce.org/viewtopic.php?id=12541
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1332623
Title:
Thunar behaves inconsistently with USB flash drive FAT32 partitions
Status in glib2.0 package in Ubuntu:
Confirmed
Status in thunar package in Ubuntu:
Fix Released
Bug description:
I installed Xubuntu 14.04 and performed no customizations or
reconfigurations.
Observation: Thunar 1.6.3 ("File Manager" from menu) on Xubuntu 14.04
handles write permission to inserted USB flash drives inconsistently:
* I am able to create a nil file on the flash drive with Thunar and edit it.
Clearly, the flash drive is not read-only.
* Using Thunar, I cannot copy an existing file (E.g. ~/.profile) and paste it
on the flash drive - "destination is read-only" (not true!).
* However, in a terminal window, `cp` with the flash drive as a destination
succeeds.
I tried this on drives by different manufacturers and with differing
capacities and on two different Xubuntu 14.04 installations.
There might be a configuration change for Thunar to allow paste to
flash drives. If so, this should be enabled when Thunar is installed
as this behaviour is what users expect.
Note: I created the FAT32 partition with `gparted` on Linux. I also
got the same results after creating a FAT32 partition using an MACOSX
system.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jun 20 11:30:40 2014
InstallationDate: Installed on 2014-06-19 (1 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
SourcePackage: thunar
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1332623/+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 1715854] Re: Adding local mail server to online accounts not possible
** Package changed: gnome-control-center (Ubuntu) => gnome-online- accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1715854 Title: Adding local mail server to online accounts not possible Status in gnome-online-accounts package in Ubuntu: New Bug description: In Settings / Online Accounts trying to connect a local SMTP/IMAP account fails. Trying to add the IMAP works (one has to ignore the warning about self signed certificate). SMTP does not get added (gnome-control-center-alt:6192): GoaBackend-WARNING **: g_socket_client_connect_to_host() failed: Could not connect to smtp.rsb.intern: Connection refused (g-io-error-quark, 39) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 12:57:37 2017 InstallationDate: Installed on 2017-09-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1715854/+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 1717277] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
** Package changed: gnome-control-center (Ubuntu) => gnome-online- accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1717277 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-control-center: Confirmed Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Hello, I'm working with GNOME settings Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Sep 14 11:49:22 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-05 (70 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f3817fd1e32 : mov(%rdi),%rbp PC (0x7f3817fd1e32) ok source "(%rdi)" (0x1) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 goa_object_peek_account () from /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1717277/+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 discussed this issue briefly on #xubuntu-devel today. This issue does not affect the default Xubuntu session which has set a cursor size for a long time. It only affects Ubuntu 18.10 users using the plain Xfce session. (In fact, I had to create a new user to see this bug for myself in an Xubuntu 18.10 live ISO. Simply choosing "Xfce" after already logging in with "Xubuntu" was not sufficient.) This bug will be fixed for Ubuntu 19.04 and never affected Ubuntu 18.04 LTS. ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: rls-cc-notfixing -- 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 Committed Status in gtk+3.0 package in Debian: Unknown 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 1717277] [NEW] gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
You have been subscribed to a public bug: Hello, I'm working with GNOME settings Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Sep 14 11:49:22 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-05 (70 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f3817fd1e32 : mov (%rdi),%rbp PC (0x7f3817fd1e32) ok source "(%rdi)" (0x1) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 goa_object_peek_account () from /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo ** Affects: gnome-control-center Importance: Medium Status: Confirmed ** Affects: gnome-online-accounts (Ubuntu) Importance: Medium Status: Triaged ** Tags: amd64 apport-crash artful -- gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() https://bugs.launchpad.net/bugs/1717277 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Description changed: [Test Case] rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 - rbalint@yogi:~$ lxc shell bb-lp-1806076 + rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: - libfreetype6 + libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: - language-pack-ru + language-pack-ru The following NEW packages will be installed: - language-pack-ru language-pack-ru-base + language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... - ru_RU.UTF-8... done - ru_UA.UTF-8... done + ru_RU.UTF-8... done + ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1983, in - (options, args) = parser.parse_args() # type: ignore - File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args - stop = self._process_args(largs, rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args - self._process_long_opt(rargs, values) - File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt - option.process(opt, value, values, self) - File "/usr/lib/python3.6/optparse.py", line 785, in process - self.action, self.dest, opt, value, values, parser) - File "/usr/lib/python3.6/optparse.py", line 807, in take_action - parser.print_help() - File "/usr/lib/python3.6/optparse.py", line 1647, in print_help - file.write(self.format_help()) + File "/usr/bin/unattended-upgrade", line 1983, in + (options, args) = parser.parse_args() # type: ignore + File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args + stop = self._process_args(largs, rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args + self._process_long_opt(rargs, values) + File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt + option.process(opt, value, values, self) + File "/usr/lib/python3.6/optparse.py", line 785, in process + self.action, self.dest, opt, value, values, parser) + File "/usr/lib/python3.6/optparse.py", line 807, in take_action + parser.print_help() + File "/usr/lib/python3.6/optparse.py", line 1647, in print_help + file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat Usage: unattended-upgrade [options] Options: - -h, --helpshow this help message and exit - -d, --debug print debug messages - --apt-debug make apt/libapt print verbose debug messages - -v, --verbose print info messages - --dry-run Simulation, download but do not install - --download-only Only download, do not even try to install. - --minimal-upgrade-steps - Upgrade in minimal steps (and allow interrupting with - SIGTERM - + -h, --helpshow this help message and exit + -d, --debug print debug messages + --apt-debug make apt/libapt print verbose debug messages + -v, --verbose print info messages + --dry-run Simulation, download but do not install + --download-only Only download, do not even try to install. + --minimal-upgrade-steps + Upgrade in minimal steps (and allow interrupting with + SIGTERM [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If
[Touch-packages] [Bug 1715854] [NEW] Adding local mail server to online accounts not possible
You have been subscribed to a public bug: In Settings / Online Accounts trying to connect a local SMTP/IMAP account fails. Trying to add the IMAP works (one has to ignore the warning about self signed certificate). SMTP does not get added (gnome-control-center-alt:6192): GoaBackend-WARNING **: g_socket_client_connect_to_host() failed: Could not connect to smtp.rsb.intern: Connection refused (g-io-error-quark, 39) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.25.92.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 12:57:37 2017 InstallationDate: Installed on 2017-09-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug artful -- Adding local mail server to online accounts not possible https://bugs.launchpad.net/bugs/1715854 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1808060] Re: libmirclient causes multiarch SDL2 headers to conflict with each other
As you can see in https://packages.ubuntu.com/disco/libmirclient-dev they are actually not co-installable so it's not as minor a problem as you state, but it's certainly fixable. ** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1808060 Title: libmirclient causes multiarch SDL2 headers to conflict with each other Status in mir package in Ubuntu: Triaged Bug description: libmirclient-dev makes impossible to install both libsdl2-dev and libsdl2-dev:i386 which is essential for anyone building game related software. Seeing mir not being used at all in any of the official Ubuntu flavors, I find it strange that it was considered an acceptable solution to break a common and important workflow in favor of an experimental display server. It's probably a minor packaging bug anyway, multi-arch development headers usually don't conflict with each other. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libmirclient-dev 0.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 11 14:25:50 2018 SourcePackage: mir UpgradeStatus: Upgraded to cosmic on 2018-11-02 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1808060/+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 1098441] Re: indicator-datetime is used in GNOME classic but the panel is only listed for Unity
that's deprecated by the move to GNOME in newer Ubuntu versions ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Invalid -- 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/1098441 Title: indicator-datetime is used in GNOME classic but the panel is only listed for Unity Status in Indicator Date and Time: Triaged Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Triaged Bug description: Hello! 1) I have installed on VirbualBox, Edubuntu amd64 (10a0abbefa754b36869be07fb2460bf1 *raring-dvd-amd64.iso 20130111). 2) On the session "gnome fallback", on the high panel, I have clicked on the time. 3) On the "setting Date & Time" this link is false because is launched "gnome-control-center (view screencast). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Fri Jan 11 08:19:26 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-01-11 (0 days ago) InstallationMedia: Edubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130111) MarkForUpload: True ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (gnome-settings-daemon:1972): color-plugin-WARNING **: failed to get edid: unable to get EDID for output (gnome-settings-daemon:1972): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output (gnome-settings-daemon:1972): color-plugin-WARNING **: failed to reset xrandr-default gamma tables: gamma size is zero (gnome-panel:2024): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed (gnome-panel:2024): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.3-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.0-0ubuntu1 indicator-datetime 12.10.3daily12.11.23-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1098441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
I installed gnome-shell 3.28.3-0ubuntu0.18.04.4 from bionic-proposed in a fully up-to-date bionic VM (amd64) and verified that after restarting the shell (Alt+F2, r), the problem with password fields in firefox is gone. I used the instructions in duplicate bug #1795169 for testing, as they don't involve installing an extension, and test case #2 in this bug report (which involves reddit login page) doesn't exhibit the problem any longer. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-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/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1744719] Re: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface()
That's still an issue https://errors.ubuntu.com/problem/f31496b5c1b8747327b33133de1fb483c0abce0b ** Package changed: gnome-control-center (Ubuntu) => gnome-online- accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1744719 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() Status in gnome-control-center: Confirmed Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: Hello, I'm trying to delete an "Online Account" from Google Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:53:35 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (100 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center online-accounts SegvAnalysis: Segfault happened at: 0x7fd2c3e16fbf : mov(%rbx),%rdi PC (0x7fd2c3e16fbf) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_dbus_object_get_interface () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 goa_object_peek_account () at /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 () () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1744719/+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
** Also affects: gtk+3.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148 Importance: Unknown Status: Unknown ** Project changed: hash-it => acorn (Ubuntu) ** No longer affects: acorn (Ubuntu) -- 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: Confirmed Status in gtk+3.0 package in Debian: Unknown 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 1768754] Re: Applications are muted (silent) but system sounds work
Has I say in my report : "Graphically, applications react normally, we can see their connections with pulse audio in the applications tab of the sound settings. But no sound comes out of the speakers." At UI level, everything seem to work, application volume is not mutted. The stranger thing is that gnome feedback sound work where application sound (mpv, firefox, ...) don't. -- 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/1768754 Title: Applications are muted (silent) but system sounds work Status in pulseaudio package in Ubuntu: Incomplete Bug description: How to reproduce this bug: * Connect a laptop to a dock, which is connected to a screen with an HDMI / DisplayPort cable. * Then configure the sound to exit through the cable connecting the screen. * Turn off the computer * Take it out of the dock * Turn on the computer Then, the sound automatically switches to the audio output of the laptop. System sounds work well, such as the bell of output volume slider or the test speaker buttons “front left” or “front right”. Unfortunately, no more applications can produce a sound. Graphically, applications react normally, we can see their connections with pulse audio in the applications tab of the sound settings. But no sound comes out of the speakers. Workaround : * Connect an alternative audio output, such as a Bluetooth headset * Select it in the “Choose a device for sound output:” option * Switch back to the internal audio speakers * Et voilà ! If it help, my laptop is a “HP Zbook G2” sometime connected to a “HP 2012 230W Docking Station” Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 3 09:21:01 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-04-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768754/+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 1744719] [NEW] gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface()
You have been subscribed to a public bug: Hello, I'm trying to delete an "Online Account" from Google Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 22 10:53:35 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (100 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: gnome-control-center online-accounts SegvAnalysis: Segfault happened at: 0x7fd2c3e16fbf : mov (%rbx),%rdi PC (0x7fd2c3e16fbf) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_dbus_object_get_interface () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 goa_object_peek_account () at /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 () () () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo ** Affects: gnome-control-center Importance: Medium Status: Confirmed ** Affects: gnome-online-accounts (Ubuntu) Importance: Medium Status: Triaged ** Tags: amd64 apport-crash bionic -- gnome-control-center crashed with SIGSEGV in g_dbus_object_get_interface() https://bugs.launchpad.net/bugs/1744719 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1089855] Re: Online accounts keeps asking authorization
I think this is what's happening still today with up to date 10.40: Accounts are expired, but when I do the sign-in process successfully, they still are reported expired. Tested with Google and Facebook accounts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1089855 Title: Online accounts keeps asking authorization Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Online accounts regularly asks for account authorization to access my online accounts, these are google accounts, but also IRC and plain jabber. Sometimes, I need to reboot to get back into my accounts. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-online-accounts 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 13 11:40:45 2012 InstallationDate: Installed on 2012-07-19 (146 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to quantal on 2012-10-01 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1089855/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
I'm back to having to re-pair a handful of times each boot. It seems every once in a while the pairing "sticks" and works until I have to reconnect it again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1768754] Re: Applications are muted (silent) but system sounds work
gnome-control-center is only involved in applying configuration changes, it's not a service and not active/playing a part in what is happening after rebooting on disconnecting devices, reassigning to pulseaudio When you play sound in an application, do you see that one added to the 'applications' tab from the sound settings? is the volume muted/low there? ** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1768754 Title: Applications are muted (silent) but system sounds work Status in pulseaudio package in Ubuntu: Incomplete Bug description: How to reproduce this bug: * Connect a laptop to a dock, which is connected to a screen with an HDMI / DisplayPort cable. * Then configure the sound to exit through the cable connecting the screen. * Turn off the computer * Take it out of the dock * Turn on the computer Then, the sound automatically switches to the audio output of the laptop. System sounds work well, such as the bell of output volume slider or the test speaker buttons “front left” or “front right”. Unfortunately, no more applications can produce a sound. Graphically, applications react normally, we can see their connections with pulse audio in the applications tab of the sound settings. But no sound comes out of the speakers. Workaround : * Connect an alternative audio output, such as a Bluetooth headset * Select it in the “Choose a device for sound output:” option * Switch back to the internal audio speakers * Et voilà ! If it help, my laptop is a “HP Zbook G2” sometime connected to a “HP 2012 230W Docking Station” Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 3 09:21:01 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-04-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768754/+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 1774901] Re: Ubuntu 16.04 atualized, then wifi no more
Thank you for your bug report. Could you give details on your wifi. Do you see it but fail to connect? What error do you get? Could you also add your journalctl log after getting the issue? ** Package changed: gnome-control-center (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1774901 Title: Ubuntu 16.04 atualized, then wifi no more Status in network-manager package in Ubuntu: Incomplete Bug description: I use Ubuntu 18.04 LTS release 18.04, since its delivery, in dual boot with Windows 8.1, and its all ok. In may 28 I made a normal atualization so reboot, then wifi device not connected no more. I don´t have wired connection, only wifi, so I don´t know what to do.(I´m posting this by Windows, and wifi is connected.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1774901/+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 1774904] Re: No defualt sound. Test speakers not working.
Thank you for your bug report. Is that specific to your user/could you try with a test user? Could you also start gnome-control-center from a command line and see if any warning is displayed, and see if there is a slider for the sound effect in the applications tab when you play the test sound, maybe it's low/muted? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1774904 Title: No defualt sound. Test speakers not working. Status in gnome-control-center package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Default sound is silent, choosing another sound (ie. Sonar) plays the sound until the control panel is closed. Test speakers does not produce any sounds. Sounds and music work in FF and Rhythm Box. Description: Ubuntu 18.04 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1766 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Jun 3 21:10:36 2018 InstallationDate: Installed on 2018-03-26 (69 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: CO96510J.86A.6100.2009.1004.2331 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DQ965GF dmi.board.vendor: Intel Corporation dmi.board.version: AAD41676-402 dmi.chassis.type: 3 dmi.chassis.vendor: IN WIN dmi.chassis.version: IW-Z583 dmi.modalias: dmi:bvnIntelCorp.:bvrCO96510J.86A.6100.2009.1004.2331:bd10/04/2009:svnPrimeSystems:pnCF2007-965:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-402:cvnINWIN:ct3:cvrIW-Z583: dmi.product.name: CF2007-965 dmi.sys.vendor: Prime Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774904/+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 1768754] [NEW] Applications are muted (silent) but system sounds work
You have been subscribed to a public bug: How to reproduce this bug: * Connect a laptop to a dock, which is connected to a screen with an HDMI / DisplayPort cable. * Then configure the sound to exit through the cable connecting the screen. * Turn off the computer * Take it out of the dock * Turn on the computer Then, the sound automatically switches to the audio output of the laptop. System sounds work well, such as the bell of output volume slider or the test speaker buttons “front left” or “front right”. Unfortunately, no more applications can produce a sound. Graphically, applications react normally, we can see their connections with pulse audio in the applications tab of the sound settings. But no sound comes out of the speakers. Workaround : * Connect an alternative audio output, such as a Bluetooth headset * Select it in the “Choose a device for sound output:” option * Switch back to the internal audio speakers * Et voilà ! If it help, my laptop is a “HP Zbook G2” sometime connected to a “HP 2012 230W Docking Station” Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 3 09:21:01 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-04-24 (8 days ago) ** Affects: pulseaudio (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug bionic -- Applications are muted (silent) but system sounds work https://bugs.launchpad.net/bugs/1768754 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1774901] [NEW] Ubuntu 16.04 atualized, then wifi no more
You have been subscribed to a public bug: I use Ubuntu 18.04 LTS release 18.04, since its delivery, in dual boot with Windows 8.1, and its all ok. In may 28 I made a normal atualization so reboot, then wifi device not connected no more. I don´t have wired connection, only wifi, so I don´t know what to do.(I´m posting this by Windows, and wifi is connected.) ** Affects: network-manager (Ubuntu) Importance: Low Status: Incomplete -- Ubuntu 16.04 atualized, then wifi no more https://bugs.launchpad.net/bugs/1774901 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
It's already done like mohamed badaoui said: http://mailman.alsa- project.org/pipermail/alsa-devel/2018-December/142572.html Linux kernel is a big project, it can takes months to accept it. We use mailing list rather than PR request. If you don't want to wait, you can compile it by yourself following my previous message. -- 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: Confirmed 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 1465814] Re: Apt did the opposite of what I told it to do when it asked me a yes or no question
Reporter no longer uses Launchpad so cannot establish if still an issue Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016 Issue never confirmed by another user Closing by changing status to "Invalid" ** Changed in: ubuntu-gnome Status: New => Invalid -- 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/1465814 Title: Apt did the opposite of what I told it to do when it asked me a yes or no question Status in Ubuntu GNOME: Invalid Status in apt package in Ubuntu: Invalid Bug description: Today I executed the command: sudo apt-get dist-upgrade And this was the output: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: aptdaemon aptdaemon-data python-aptdaemon python-aptdaemon.gtk3widgets python3-aptdaemon python3-aptdaemon.gtk3widgets python3-aptdaemon.pkcompat wpasupplicant 8 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 1,146 kB of archives. After this operation, 3,072 B of additional disk space will be used. Do you want to continue? [Y/n] So I answered 'y' (without the quotes), and this was the output: Abort. And it seemingly aborted instead of doing what I said, although when I ran the command again, it installed the upgrades instead of aborting, but I just thought that I should report this as it seemed buggy as this is not what it is meant to do. --- OS Information: Description: Ubuntu 15.04 Release: 15.04 Package Information (I got this information after upgrading those packages, and the error occurred before the upgrade, so the version it occurred on might have been the previous to this): apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1465814/+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 1806458] Re: Intel I219-V ethernet connection lost
** Tags added: manager network x11 ** Tags removed: manager network ** Tags added: network-manager -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By
[Touch-packages] [Bug 1553260] Re: Pressing the little "X" instead of "Cancel" makes Apport unresponsive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1553260 Title: Pressing the little "X" instead of "Cancel" makes Apport unresponsive Status in apport package in Ubuntu: Confirmed Bug description: I have recently noticed that when running Apport, if one presses the little "X" to close Apport during the time when it is collecting or sending the bug information, instead of it behaving as though you have pressed "Cancel" and closing, it becomes unresponsive and I am asked if I would prefer to "Wait" or "Force Quit" and I am forced to "Force Quit" because it is completely unresponsive, there's nothing else I can do. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportLog: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CrashReports: 640:1000:115:252353:2016-03-04 13:54:37.958497524 +:2016-03-04 13:54:38.958497524 +:/var/crash/_usr_share_oneconf_oneconf-service.1000.crash 664:1000:115:0:2016-03-04 13:54:40.334540276 +:2016-03-04 13:54:40.334540276 +:/var/crash/_usr_share_oneconf_oneconf-service.1000.upload 600:108:115:0:2016-03-04 13:54:42.614611375 +:2016-03-04 13:54:42.614611375 +:/var/crash/_usr_share_oneconf_oneconf-service.1000.uploaded CurrentDesktop: GNOME Date: Fri Mar 4 16:14:38 2016 InstallationDate: Installed on 2015-12-10 (85 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1553260/+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 1553260] Re: Pressing the little "X" instead of "Cancel" makes Apport unresponsive
** Tags removed: wily ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1553260 Title: Pressing the little "X" instead of "Cancel" makes Apport unresponsive Status in apport package in Ubuntu: Confirmed Bug description: I have recently noticed that when running Apport, if one presses the little "X" to close Apport during the time when it is collecting or sending the bug information, instead of it behaving as though you have pressed "Cancel" and closing, it becomes unresponsive and I am asked if I would prefer to "Wait" or "Force Quit" and I am forced to "Force Quit" because it is completely unresponsive, there's nothing else I can do. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportLog: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CrashReports: 640:1000:115:252353:2016-03-04 13:54:37.958497524 +:2016-03-04 13:54:38.958497524 +:/var/crash/_usr_share_oneconf_oneconf-service.1000.crash 664:1000:115:0:2016-03-04 13:54:40.334540276 +:2016-03-04 13:54:40.334540276 +:/var/crash/_usr_share_oneconf_oneconf-service.1000.upload 600:108:115:0:2016-03-04 13:54:42.614611375 +:2016-03-04 13:54:42.614611375 +:/var/crash/_usr_share_oneconf_oneconf-service.1000.uploaded CurrentDesktop: GNOME Date: Fri Mar 4 16:14:38 2016 InstallationDate: Installed on 2015-12-10 (85 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1553260/+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 1450558] Re: Stops uploading half way and crashes
Reporter no longer uses Launchpad so unable to establish if still an issue
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Problem never confirmed by another user
No activity on bug report for over three years
Closing by marking "Invalid"
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1450558
Title:
Stops uploading half way and crashes
Status in apport package in Ubuntu:
Invalid
Bug description:
I find that when executing "apport-bug " (""
replaced by the name of the package which you are reporting the bug against)
that after getting half way through uploading the information, it crashes, and
I am forced to force quit the process, and upon exit I am given this Python
error message:
"
^CException ignored in:
Traceback (most recent call last):
File "/usr/lib/python3.4/threading.py", line 1294, in _shutdown
t.join()
File "/usr/lib/python3.4/threading.py", line 1060, in join
self._wait_for_tstate_lock()
File "/usr/lib/python3.4/threading.py", line 1076, in _wait_for_tstate_lock
elif lock.acquire(block, timeout):
KeyboardInterrupt
"
So this is disabling me from being able to upload any bug information
through Apport.
---
OS Information:
Description: Ubuntu 15.04
Release: 15.04
Package Information:
apport:
Installed: 2.17.2-0ubuntu1
Candidate: 2.17.2-0ubuntu1
Version table:
*** 2.17.2-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1450558/+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 1786532] Re: Microphones don't work after rebooting
The settings is not a service and not involved in restoring configs after boot, it's just an interface to change the options. Removing g-c-c since the problem is not here ** No longer affects: gnome-control-center (Ubuntu) -- 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/1786532 Title: Microphones don't work after rebooting Status in pulseaudio package in Ubuntu: New Bug description: Connect both rear microphone and front microphone to the PC. In Gnome Sound settings select Rear Microphone input. Reboot the computer. Now both microphones don't work. Workaround: Modify (and then modify back) the input device in Gnome Sound settings. Gigabyte H67A-UD3H motherboard. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 10 21:34:19 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-06-23 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1786532/+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 1763584] Re: ureadahead service fails with error Error while tracing: No such file or directory
My system (Ubuntu 18.04) on a Thinkpad X1 Extreme is affected as well. I operate the laptop with closed lid using a Thinkpad TB3 docking station. Here is the relevant output: $ systemctl status ureadahead.service ● ureadahead.service - Read required files in advance Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-12-12 11:29:53 CET; 7min ago Process: 498 ExecStart=/sbin/ureadahead (code=exited, status=5) Main PID: 498 (code=exited, status=5) Dec 12 11:29:53 ubuntu ureadahead[498]: ureadahead: Error while tracing: No such file or directory Dec 12 11:29:53 ubuntu ureadahead[498]: Counted 12 CPUs Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1763584 Title: ureadahead service fails with error Error while tracing: No such file or directory Status in ureadahead package in Ubuntu: Confirmed Bug description: I'm reporting this as duplicate of #1176536 to provide more info. dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service ● ureadahead.service - Read required files in advance Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 10min ago Main PID: 379 (code=exited, status=5) Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while tracing: No such file or directory Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ureadahead 0.100.0-20 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 13:13:26 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1763584/+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 1685878] Re: Gedit bottom scroll bar goes on top of final line
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1685878 Title: Gedit bottom scroll bar goes on top of final line Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1685878/+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 1685878] Re: Gedit bottom scroll bar goes on top of final line
Upstream issue now being tracked at https://gitlab.gnome.org/GNOME/gtk/issues/809 -- 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/1685878 Title: Gedit bottom scroll bar goes on top of final line Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I am on Ubuntu GNOME 17.04 with GNOME 3.24, though obviously still Gedit 3.22, and I have found something slightly annoying with it, and that is that when mousing over the last line to try to copy and paste it for instance, the bottom scroll bar goes on top of it and obscures it. I have attached two screenshots of what I mean. This also affects me on Arch so I have filled an upstream report on this. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1685878/+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 1700104] Re: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Nice catch Martin! The best would be to ask systemd what directory to use. So the same code can be used on Ubuntu and Debian. I was not able to find a way to ask systemd where the unit files should be installed :-( Any idea? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1700104 Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pcsc-lite package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: pcscd 1.8.10-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.24 AptOrdering: pcscd: Install pcscd: Configure Architecture: amd64 Date: Fri Jun 23 12:21:31 2017 DuplicateSignature: package:pcscd:1.8.10-1ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-28 (177 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: pcsc-lite Title: package pcscd 1.8.10-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1700104/+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 1808133] [NEW] python3-apport emits a deprecation warning
Public bug reported:
python3-apport uses the deprecated module imp. This causes to emitting a
deprecation warning when run python3 with the -Walways option, and even
to changing a traceback when run python3 with the -Werror option.
Example:
```
$ python3 -Walways -c '1/0'
/usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp
module is deprecated in favour of importlib; see the module's documentation for
alternative uses
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
```
```
$ python3 -Werror -c '1/0'
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 13, in
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
File "/usr/lib/python3.6/imp.py", line 33, in
DeprecationWarning, stacklevel=2)
DeprecationWarning: the imp module is deprecated in favour of importlib; see
the module's documentation for alternative uses
Original exception was:
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
```
The -Werror option can be used for catching possible issues, and
additional output from apport spoils the result.
```
$ python3 -b -Werror -c 'str(b"")'
Traceback (most recent call last):
File "", line 1, in
BytesWarning: str() on a bytes instance
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 13, in
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
File "/usr/lib/python3.6/imp.py", line 33, in
DeprecationWarning, stacklevel=2)
DeprecationWarning: the imp module is deprecated in favour of importlib; see
the module's documentation for alternative uses
Original exception was:
Traceback (most recent call last):
File "", line 1, in
BytesWarning: str() on a bytes instance
```
The solution is to silence DeprecationWarning for `import imp`:
import warnings
with warnings.catch_warnings():
warnings.simplefilter('ignore', DeprecationWarning)
import imp
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1808133
Title:
python3-apport emits a deprecation warning
Status in apport package in Ubuntu:
New
Bug description:
python3-apport uses the deprecated module imp. This causes to emitting
a deprecation warning when run python3 with the -Walways option, and
even to changing a traceback when run python3 with the -Werror option.
Example:
```
$ python3 -Walways -c '1/0'
/usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the
imp module is deprecated in favour of importlib; see the module's documentation
for alternative uses
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp
Traceback (most recent call last):
File "", line 1, in
ZeroDivisionError: division by zero
```
```
$ python3 -Werror -c '1/0'
Traceback (most recent call last):
File "", line 1, in
[Touch-packages] [Bug 1801744] Re: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
This is caused by insufficient disk space on /boot partition where kernels are stored, excerpts from the attachments: update-initramfs: Generating /boot/initrd.img-4.4.0-139-generic cat: write error: No space left on device Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 241965241595 0 100% /boot Sometimes, running "sudo apt-get autoremove" will clean up old kernels and allow subsequent upgrade attempts to succeed. In some situations manual intervention is needed, see more about that at https://help.ubuntu.com/community/RemoveOldKernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801744 Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-139-generic 4.4.0-139.165 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jaideep1604 F pulseaudio /dev/snd/controlC0: jaideep1604 F pulseaudio Date: Fri Nov 2 23:55:21 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=0dfe2ba1-25bb-463c-b5f0-85897090f1d1 InstallationDate: Installed on 2016-04-19 (930 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO INVALID ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-139-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN36WW(V2.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 3192 PRO dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrA2CN36WW(V2.04):bd04/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3192PRO:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801744/+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 1799259] Re: Online Accounts imap does not support plain
Did you configure the email account in the online account? What email client do you use? The online accounts are supposed to handle plain, are you sure you issue is not that you need a security option instead of plain (like it's described in https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/27) ** Package changed: gnome-control-center (Ubuntu) => gnome-online- accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1799259 Title: Online Accounts imap does not support plain Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: When I try to log in with IMAP It does not go and alerts that it does not support plain. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 09:21:51 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-18 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1799259/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Thank you for the new debdiffs. I have uploaded all these packages now. -- 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/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Released Status in cups package in Debian: Fix Released Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1799259] [NEW] Online Accounts imap does not support plain
You have been subscribed to a public bug: When I try to log in with IMAP It does not go and alerts that it does not support plain. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 09:21:51 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-18 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug bionic -- Online Accounts imap does not support plain https://bugs.launchpad.net/bugs/1799259 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
gnome-control-center is only the configuration interface, what you describe is that it doesn't automatically switch back when disconnecting the screen, that is on the backend side and not the user UI, reassigning to pulseaudio then ** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu) -- 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/1802350 Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: On a fresh install of ubutu 18.04 all sound work (youtube and system sounds) I connected external hdmi monitor with speakers. I switched audio output to hdmi in settings Then all audio was channeled to external monitor speakers (youtube and system sounds) Then I disconnected external monitor and did not touch the audio output Now only system sounds are working. Youtube in chrome does not work. Audio settings says internal speakers. Firefox youtube has audio normally After reboot same issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 1412 F pulseaudio /dev/snd/controlC1: ed 1412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:28:37 2018 InstallationDate: Installed on 2018-11-01 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.family: 00 dmi.product.name: Inspiron 5547 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
> Disabling the key "/org/gnome/desktop/lockdown/disable-lock-screen" in dconf-editor solved the problem. Also, solved for mee too (Ubuntu 18.10 with all updates installed, per 12 Dec 2018) -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 366470] Re: Ekiga destroys Evolution address book
Upstream tested with a recent version and said it seems to be fixed there ** Changed in: evolution-data-server (Ubuntu) Status: Triaged => Fix Released -- 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/366470 Title: Ekiga destroys Evolution address book Status in Ekiga: Expired Status in evolution-data-server: Expired Status in evolution-data-server package in Ubuntu: Fix Released Bug description: Binary package hint: ekiga Jaunty, Ekiga 3.2.0. I decided to import contacts from Thunderbird to Evolution because Ekiga can use supposedly use these addresses. So I spent some time getting things organized, no problem. Then I configure Ekiga and take a look at the addressbook. Didn't change anything using Ekiga, just took a look. Then I closed Ekiga, did some other stuff and then I needed an Evolution contacts. Nothing there. Ekiga messed them up. addressbook.db and addressbook.db.summary are still there, but Evolution can't read them properly. Yes, it's reproducible. I stupidly went through the process of importing my contacts twice before realizing that Ekiga was the problem. Wow. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/ekiga Package: ekiga 3.2.0-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ekiga Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ekiga/+bug/366470/+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
Jeremy, you might want to consider distro patching that one as well if you are still doing gtk changes? ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- 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 Hash-it: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed 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/hash-it/+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 1808092] Re: Checking and handling various filetypes in fmt
The attachment "fmt.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1808092 Title: Checking and handling various filetypes in fmt Status in coreutils package in Ubuntu: New Bug description: fmt doesn't check filetypes of the input arguments passed to it, it just opens the file and reads from it without checking its st_mode. It only throws an error if the file doesn't exist and can't handle the following filetypes - S_IFCHR, S_IFBLK and S_IFBLK. Passing a file from any of these types will possibly hang or crash the application. For more reference, please visit the below link- (https://github.com/pkmoore/rrapper/blob/master/anomalies/weird_filetypes.md) I have attached a patch that checks for the above mentioned filetypes and handles them accordingly. Please let me know if you have any questions or suggestions regarding this, will be happy to answer them. Thank you Snahil Singh ss11...@nyu.edu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 11 20:01:58 2018 ExecutablePath: /usr/bin/fmt InstallationDate: Installed on 2018-11-07 (35 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1808092/+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 1808095] Re: uniq is not checking and handling all file types
The attachment "Patch for detecting and handling character and block device as input" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1808095 Title: uniq is not checking and handling all file types Status in coreutils package in Ubuntu: New Bug description: Hi, The utility uniq allows all types of files as input. Allowing block devices or character devices as input can lead to unwanted behavior such as the utility executes indefinitely when device '/dev/urandom' is passed as an input. Please refer this for more information regarding this issue (https://github.com/pkmoore/rrapper/blob/master/anomalies/weird_filetypes.md). I've included a patch which checks and handles character devices and block devices when passed as input. Please get back to me for more information. Regards, Anoop Nadig ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Dec 11 20:23:32 2018 ExecutablePath: /usr/bin/uniq InstallationDate: Installed on 2018-11-07 (35 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1808095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808109] [NEW] Upgrade to 1.12
Public bug reported: GPGme 1.12 was release with a new json help that allows browsers to use gpgme for encryption (see https://www.mailvelope.com/de/blog/mailvelope-3.0 for example). Debian (buster) already includes 1.12 and so should Ubuntu. ** Affects: gpgme1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808109 Title: Upgrade to 1.12 Status in gpgme1.0 package in Ubuntu: New Bug description: GPGme 1.12 was release with a new json help that allows browsers to use gpgme for encryption (see https://www.mailvelope.com/de/blog/mailvelope-3.0 for example). Debian (buster) already includes 1.12 and so should Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1808109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
